Gnome merges Global Shortcuts
-
Gnome Extensions run in the Gnome shell, so they have special privileges.
Wayland’s security focus prevents apps from listening in on all user key presses, which means they can’t know you used a keyboard shortcut unless the app is focused.
The Global Shortcut Portal was made to address this. An app registers for a global shortcut, and when the user activates the shortcut, the portal tells the app that it’s been activated.
Thanks for the context!
-
This post did not contain any content.wrote on last edited by [email protected]
.
-
This post did not contain any content.
it's still up to individual apps to implement the portal I think
-
it's still up to individual apps to implement the portal I think
True, but the apps that cause the most complaints about features that Wayland lacks (Discord for this one) are usually among the fastest to enable the portals once they're available.
-
The traditional insecure global shortcuts system works in Xorg.
-
True, but the apps that cause the most complaints about features that Wayland lacks (Discord for this one) are usually among the fastest to enable the portals once they're available.
Not sure if Discord is the best example here, as it didn't support the screen capture portal for a very long time.
-
It wasn't clear for me what the hell is a "Global Shortcut" I heard the term first time in my life, I found the answer in the upstream PR:
It's designed so that applications can register actions that can be triggered globally (i.e. regarless of the system's state, like focus).
It's strange, it wasn't possible until now, or the main thing it's now DE independent?
On Gnome I use Run or raise extension, and with this I can run or switch to running apps with** global shortcuts**, so this was definitely working from Gnome extensions.
It's because this feature was implemented as a pseudo-keylogger on X11. All X clients could listen to the compositor state at all times (including input), even if input was focussed on another (potentially sensitive) application.
In Wayland, clients have almost zero knowledge of the compositor's state. This was an explicit design choice to enhance security and enable modular features via wayland protocols. Of course, this also killed every implementation of app-specific global shortcuts.
Wayland protocols take a lot of time to get agreed on - They need multiple implementations across different compositors (usually means KDE and GNOME need to implement the protocol spec and agree to it) and the specs can take a long time to design and reach production.
Obviously this does hurt uptake for Wayland since issues can take years to resolve, but the core team are very aware of the pitfalls of X11's development and have long preferred this slow and methodical approach in the hopes it's sustainable and maintainable into the future.
-
Not sure if Discord is the best example here, as it didn't support the screen capture portal for a very long time.
Discord didn't take very long to add it at all, what took a long time was fixing audio streaming.
-
The traditional insecure global shortcuts system works in Xorg.
wrote on last edited by [email protected].
-
Xorg global shortcuts will work for anything using Xwayland, but not in anything thats wayland native
For example, in a game (using wine, which uses Xorg by default currently) your global shortcut will work. But in a wayland native window like Firefox, it will not if its the active window
-
Xorg global shortcuts will work for anything using Xwayland, but not in anything thats wayland native
For example, in a game (using wine, which uses Xorg by default currently) your global shortcut will work. But in a wayland native window like Firefox, it will not if its the active window
wrote on last edited by [email protected].
-
This post did not contain any content.
Does anyone know what the status on KDE implementing this is?
-
Does anyone know what the status on KDE implementing this is?
Already merged there some time ago.
-
Already merged there some time ago.
I can't find any documentation on how to set it up, do you happen to know where that would be?
I can't figure out how to setup discord push to talk on kde wayland, specifically
-
I can't find any documentation on how to set it up, do you happen to know where that would be?
I can't figure out how to setup discord push to talk on kde wayland, specifically
Apps need to add support for the new portal system. Chromium is adding (or added?) support, so Discord may implement it once they use an Electron version with support.
If you’re using KDE, you can tell Discord to use X11 and use KDE’s feature to let X11 apps snoop on key presses.
-
Xorg global shortcuts will work for anything using Xwayland, but not in anything thats wayland native
For example, in a game (using wine, which uses Xorg by default currently) your global shortcut will work. But in a wayland native window like Firefox, it will not if its the active window
Are you sure about that? KDE has a feature that lets Xwayland apps snoop if certain keys are pressed, but Gnome does not.
-
Are you sure about that? KDE has a feature that lets Xwayland apps snoop if certain keys are pressed, but Gnome does not.
Yeah. The behavior i stated was how it works in Gnome. In KDE since Xorg passthrough is a formal thing, the behavior is different based on those options
-
Does anyone know what the status on KDE implementing this is?
It was implemented over two years ago.
-
Discord didn't take very long to add it at all, what took a long time was fixing audio streaming.
Umm yes, they did take ages to support it. It took like 7 years...
-
It was implemented over two years ago.
I can't find a way to manually add entries in the settings, is there no way to do that?
How would I manually enable push to talk in discord, for example?
