https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #20 from Nicolas Fella ---
As I have mentioned before kglobalaccel is not autostarted via the usual
autostart mechanism. The process is launched via DBus activation the first time
something makes an API call to it
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #19 from prash ---
(In reply to Nate Graham from comment #18)
> The change was reverted as it broke legitimate users of KGlobalAccel outside
> of Plasma. Re-opening this.
Could you please make the autostart of kactivitymanagerd and
https://bugs.kde.org/show_bug.cgi?id=435420
Nate Graham changed:
What|Removed |Added
Version Fixed In|5.82|
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #17 from Nate Graham ---
Git commit 9a48818abf50340e31d718cc675501dec6c51429 by Nate Graham.
Committed on 26/05/2021 at 19:14.
Pushed by ngraham into branch 'master'.
Revert "Prevent kglobalaccel5 getting activated on non-Plasma systems"
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #16 from prash ---
I'm not sure if if you still need me to list out the clashing hotkeys. There
are quite a lot of them (if I add openbox+lxqt vs KDE).
A more general solution I would prefer is if you could make all these services
https://bugs.kde.org/show_bug.cgi?id=435420
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=435420
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.82
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #15 from Nicolas Fella ---
> Amarok has some useful global shortcuts using KGlobalAccel [1], e.g. for
> skipping tracks, that you would like to work even if the current environment
> is not plasma. Currently, these shortcuts will stop
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #14 from Roman Kapl ---
(In reply to Nate Graham from comment #13)
> So you don't want kglobalaccel to run when Plasma is also installed but not
> active,
Well that is what @prash wanted, not me. I understand where he is coming from
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #13 from Nate Graham ---
So you don't want kglobalaccel to run when Plasma is also installed but not
active, and you do want it to run when using KWin as the window manager in
LXQt?
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=435420
Roman Kapl changed:
What|Removed |Added
CC||ro...@rkapl.cz
--- Comment #12 from Roman Kapl
https://bugs.kde.org/show_bug.cgi?id=435420
Nicolas Fella changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/fram
https://bugs.kde.org/show_bug.cgi?id=435420
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #9 from prash ---
(In reply to prash from comment #8)
After a bit of triangulating, it appears that merely opening a KDE app will not
autostart kglobalaccel5. On a fresh session, when I opened Okular, there were
no processes that were out
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #8 from prash ---
(In reply to prash from comment #7)
Sorry, I wrote to soon. The change to kaccess.desktop only partially fixes the
problem. kglobalaccel5 no longer autostarts on login, but it starts the moment
I start dolphin.
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #7 from prash ---
(In reply to Nicolas Fella from comment #6)
Thank you! I made this change in my own /etc/xdg/autostart/kaccess.desktop, and
it fixed the problem.
Should I mark the bug as resolved or will that be done by the dev team?
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #6 from Nicolas Fella ---
Git commit f701c66dc37343bfb01062aa09dc4a2040ea7d4c by Nicolas Fella.
Committed on 08/04/2021 at 12:52.
Pushed by nicolasfella into branch 'master'.
Only start kaccess in Plasma
kaccess is an implementation
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #5 from Nicolas Fella ---
What probably happens is that kaccess is autostarted (since it is in
/etc/xdg/autostart) and that triggers kglobalaccel.
I guess kaccess should be changed to only autostart in Plasma then
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #4 from prash ---
(In reply to Nicolas Fella from comment #2)
> Preventing that from happening is easy enough, but before I make a patch
> doing so I want to check that I'm not missing a legitimate use case.
The first thing I do on each
https://bugs.kde.org/show_bug.cgi?id=435420
--- Comment #3 from prash ---
(In reply to Nate Graham from comment #1)
> Are you saying that it gets autostarted when you're in an LXQt session too?
Yes, it gets autostarted in LXQt too.
> Do any other KDE processes get autostarted, or just
https://bugs.kde.org/show_bug.cgi?id=435420
Nicolas Fella changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
CC|
https://bugs.kde.org/show_bug.cgi?id=435420
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
22 matches
Mail list logo
