Wayland compatibility #1353
friday
announced in
Troubleshooting
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ulauncher was created as an application using GTK3 and X11, relying on a lot of X11 features that most regular desktop applications don't need, but launchers like Ulauncher does. With the arrival of Wayland, the maintainers of Wayland, GTK and Gnome Desktop decided that applications shouldn't have access to these features, and that use cases like Ulauncher are no longer a valid for their SDKs and protocols. However, many (if not most) Desktop Environments actually want to support these use cases in applications, and opts in to support additional protocols added by wlroots.
This table represent the current state in the v6 branch. All of my tests were with Gnome X11, XWayland and pure Wayland. Tests for KDE and other environments (with all these modes) are needed, but in general Gnome has the worst compatibility.
✔️ Supported
❌ Unsupported
🛠️ Unsupported, but can be worked around
In addition to this, Ulauncher's hotkey handling is platform specific, but you can always work around this should it be a problem for you. See #1347
Note that Ulauncher version 5.x.x and older uses XWayland by default when you launch Ulauncher with the Desktop files (including using XDG Autostart) or the systemd service. You can get around this by opting into using the Ulauncher version 6 beta, launching Ulauncher via a custom command or overriding the desktop entry or systemd service and removing GDK_BACKEND=x11.
Beta Was this translation helpful? Give feedback.
All reactions