KDE Plasma loves to nuke any and all keybinds to any application that gets updated on my system. Every single time firefox or discord or any other application outside the plasma stack gets updated my keybind that I set to launch it is completely wiped, like it never ever even existed. This has been happening for 2 months now and it's starting to get really annoying
Are the affected applications by any chance customized with their own .desktop files in ~/.local/share/applications? Ar there any other kind of application customization on the system?
This is 100% stock, pacman managed files
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Still happening even after the last update round to hit the Arch KDE-unstable repos
Have you by any chance run `systemsettings` as root and accidentally saved your shortcut settings at the root level, instead of the user level? That would explain system updates overwriting your changes at least.
(In reply to Nate Graham from comment #5) > Have you by any chance run `systemsettings` as root and accidentally saved > your shortcut settings at the root level, instead of the user level? That > would explain system updates overwriting your changes at least. Nope, this is not user error, this is the default stock nature of Plasma on Arch as it rolls from the kde-unstable repo. It also suffered the libxml2.so.2 issue, where Arch no longer ships such an outdated library, and plasma refused to even launch until I symlinked libxml2.so.16.0.2 to libxml2.so.2
For what it's worth, I can't reproduce this on my Fedora KDE 42 device. I'm not an Arch Linux user, but is there a reason why the KDE-Unstable repositories only have kglobalacceld, while the Extra repositories have both that and kglobalaccel? On the face of it, that seems like a possible source of issues? When that issue occurs, is ~/.config/kglobalshortcutsrc getting updated by the package updates?
I don't know, but all these updates and no bug fixes are getting really annoying. KDE/Plasma team states they're no longer working on features and trying to fix bugs in the code only to introduce 30 new bugs, 20 regressions, and 10 new features. There's still Plasma 3 source code in the latest Plasma versions. This project is an absolute mess. They spend more time changing the default settings of applications than they do patching the broken lines of code, and it shows heavily the last few years
KDE Plasma team yet again ignoring yet another reported bug by a user, trying to push it out of the queue because this dev team hates fixing bugs. They'd rather introduce features nobody asked for, insert more bugs into the code base, and then wonder why nobody donates to them when they don't listen to their community
The requested information is to check if the file ~/.config/kglobalshortcutsrc is being edited, appended, replaced, etc. during the update process when this issue is observed. Please reference https://community.kde.org/Get_Involved/Issue_Reporting#Issue_tracker_etiquette
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.