search

flathub / net.cozic.joplin_desktop

https://flathub.org/apps/details/net.cozic.joplin_desktop
22 stars 10 forks source link

Wayland works, so enable Wayland permission #216

Closed issacdowling closed 3 months ago

issacdowling commented 3 months ago

If Wayland doesn't work for you, let me know, but it works completely fine on AMD, Intel, and NVIDIA for me. The only thing stopping it by default is the lack of permissions.

This would be useful for me and (I presume) many others since it would allow nicer scaling and remove another app that requires Xwayland.

flathubbot commented 3 months ago

Started test build 143297

flathubbot commented 3 months ago

Build 143297 failed

flathubbot commented 3 months ago

Started test build 143298

flathubbot commented 3 months ago

Build 143298 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/126353/net.cozic.joplin_desktop.flatpakref
flathubbot commented 3 months ago

Started test build 143309

flathubbot commented 3 months ago

Build 143309 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/126364/net.cozic.joplin_desktop.flatpakref
catsout commented 3 months ago

Please report to electron.
https://github.com/electron/electron/issues/41551

issacdowling commented 3 months ago

I'm sorry, but I'm not sure I understand. If there's something actually stopping Wayland from working, fair enough, but regardless of what's going on with Electron, Joplin works for me just by enabling socket=wayland. I don't need to set launch arguments or change anything else, I just launch the app with that permission and it happens. What's blocking this from being enabled for Joplin?

catsout commented 3 months ago

We keep same behavior with the electron.
It's default x11, so we default x11.
It requires user to manually switch to wayland, so we also need user to add wayland permission themself.