Hi,
I agree that it's most useful on plasma.
>On systems that do not use X11 (Windows, macOS, Android) it
>is most likely not useful at all.
There exists code for mac and windows but I don't know either if it's working
or just a dummy so it compiles.
Also for everyone interested in the topic,
On Tue, Apr 6, 2021 at 5:30 PM Nicolas Fella wrote:
>
> Hi,
>
> we received a few reports [1] [2] from people using non-Plasma systems
> that the kglobalaccel5 process was started, leading to clashes with the
> native global shortcut system.
>
> This seems to happen when apps call some API of KGlo
That will continue to work. The window manager doesn't really matter
here, at least on X11.
On 06.04.21 20:31, Konstantin Kharlamov wrote:
Just to clarify a bit: by "only running on Plasma system" do you mean running
when $XDG_CURRENT_DESKTOP = KDE? Or something else?
The reason I'm asking is b
We are pleased to announce that CMake 3.19.8 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
Changes made since CMake 3.19.7:
Just to clarify a bit: by "only running on Plasma system" do you mean running
when $XDG_CURRENT_DESKTOP = KDE? Or something else?
The reason I'm asking is because I'm a user of Plasma + i3wm, and having various
shortcuts automatically set up by Plasma (specifically: screen brightness,
various mult
Hi,
we received a few reports [1] [2] from people using non-Plasma systems
that the kglobalaccel5 process was started, leading to clashes with the
native global shortcut system.
This seems to happen when apps call some API of KGlobalAccel which
results in the kglobalaccel5 process to be DBus-act
