[arch-general] WIN+anything key not working at startup
Hi Every time I start my computer, plasma does not properly detect/respond to global hotkeys, in particular, WIN+anything combination. After I open a terminal from inside plasma, kill the kglobalaccel5 program and launch it again, all the WIN+ hotkeys work again. During the time that it is not working and whilst the cursor is stood in a shell window, pressing the hotkey WIN+r generates the keypresses sr Has anyone seen this behaviour before and know of a durable fix short of scripting plasma startup with a delayed kill+restart of kglobalaccel5? Thank you Andy
On 07/23/2018 10:02 AM, Andy Pieters wrote:
Has anyone seen this behaviour before and know of a durable fix short of scripting plasma startup with a delayed kill+restart of kglobalaccel5?
Andy, It is unclear what exactly is happening. It almost sounds like there is something in your profile that is preventing loading your kglobalaccel5 at start-up, and the kill/reload does finally manage to load it correctly. Before looking further into profile problems, after you kill/restart kglobalaccel5 and have things working, rebuild the kde system config cache passing the --noincremental option to force a complete rebuild, e.g. $ kbuildsycoca5 --noincremental then restart plasma and see if that resolved the issue. If not, the next test would be to create a new user and logout/login with that account and see if the problem persists. If it does -- file a bug, if not, you know you have a problem in your profile. Check: https://forum.kde.org/viewtopic.php?f=67&t=150900 https://www.pclinuxos.com/forum/index.php?topic=144060.0 or any of the other sites returned searching "kde5/plasma delete profile" Good luck. -- David C. Rankin, J.D.,P.E.
Thank you David
8:35AM David C. Rankin
Before looking further into profile problems, after you kill/restart kglobalaccel5 and have things working, rebuild the kde system config cache passing the --noincremental option to force a complete rebuild, e.g.
$ kbuildsycoca5 --noincremental
then restart plasma and see if that resolved the issue.
It did appear to, although this was a sign out/sign in situation, not a "real" boot.
if not, you know you have a problem in your profile. Check: https://forum.kde.org/viewtopic.php?f=67&t=150900 https://www.pclinuxos.com/forum/index.php?topic=144060.0 or any of the other sites returned searching "kde5/plasma delete profile"
Deleting a profile is not something I would recommend in any
situation, nor would I do it myself. I appreciate the help but this
entails *soooooo* much work having to recreate everything from scratch
Something I haven't mentioned before is that I have autologin going at
boot up so it could be related to that.
I will do some more testing when I need to reboot again and follow up here then.
Thank you
On Tue, Jul 24, 2018 at 8:36 AM, David C. Rankin
On 07/23/2018 10:02 AM, Andy Pieters wrote:
Has anyone seen this behaviour before and know of a durable fix short of scripting plasma startup with a delayed kill+restart of kglobalaccel5?
Andy,
It is unclear what exactly is happening. It almost sounds like there is something in your profile that is preventing loading your kglobalaccel5 at start-up, and the kill/reload does finally manage to load it correctly.
Before looking further into profile problems, after you kill/restart kglobalaccel5 and have things working, rebuild the kde system config cache passing the --noincremental option to force a complete rebuild, e.g.
$ kbuildsycoca5 --noincremental
then restart plasma and see if that resolved the issue. If not, the next test would be to create a new user and logout/login with that account and see if the problem persists. If it does -- file a bug, if not, you know you have a problem in your profile. Check:
https://forum.kde.org/viewtopic.php?f=67&t=150900 https://www.pclinuxos.com/forum/index.php?topic=144060.0
or any of the other sites returned searching "kde5/plasma delete profile"
Good luck.
-- David C. Rankin, J.D.,P.E.
participants (2)
-
Andy Pieters
-
David C. Rankin