❯ sudo pacman -S khotkeys
warning: khotkeys-5.24.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) khotkeys-5.24.3-1
Back here to say I’ve not been able to fix any of the issues. Copying all config files I could find into a new user’s dir doesn’t introduce problems in that new user. Not sure what else is left to try.
@linux-aarhus thanks, deleted files, but no luck. In fact, any change made in System Settings updates those two files you mentioned, but the error is after saving: Unable to contact khotkeys. Your changes are saved, but they could not be activated.
When saving any khotkeys settings, after clicking on “Apply”, the window (and only that window) freezes for ~1-2 mins. And then errors with the message above.
journalctl -f has this line in red after the 1-2 mins (nothing interesting before this):
systemsettings[128978]: Unable to start server org.kde.khotkeys (kded module) [ "org.freedesktop.DBus.Error.NoReply" ]: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Dunno why I hadn’t tried this before. But just renamed .config to something else and rebooted. All problems (not just custom shortcuts) are gone!
Now comes the task of finding out what exactly in .config is causing this (by moving it back file by file). There are just too many things so might take a while before I’m back with the result.
Okay good news: I’ve narrowed it down to konquerorrc and kwinrc, both in ~/.config/.
Not gonna bother figuring out which of them and which part of the file is causing issues, it’s just easier to set up kwin again.
Thanks again @Mirdarthos for sticking through it!
For anyone else facing the same issues:
Rename .config to something else like .config.backup
Reboot
Check if Cookies opens normally (or any of your other issues don’t exist)
If everything works, move a few files from .config.backup back to .config
If something break, now you know which file/dir is the cause