Summary: | Global shortcuts can be held for programs that are not installed | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kglobalaccel | Reporter: | Nix <nix> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | minor | CC: | devguy.ca, kde, nate |
Priority: | NOR | ||
Version First Reported In: | 5.74.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nix
2020-11-24 13:37:16 UTC
You say that you have /usr/share/kglobalaccel/org.kde.plasma.emojier.desktop on your system but not emojier? How should the daemon then know that it is not installed? Further you have plasma installed but apparently no shortcuts kcm? That somehow also seems wrong. I would close this as a downstream bug but I think in general the concern is valid. If we have a component in the globalshortcutsrc but no matching desktop file, then don't grab the shortcuts of that. Of course this doesn't work with the non desktop file way of registering shortcuts... Ugh you're right, that Debian install has got into a mess due to an ancient historical installation and subsequent removal of plasma-desktop: I've managed to end up with plasma-desktop-data (which contains /usr/share/kglobalaccel/org.kde.plasma.emojier.desktop) installed, but not plasma-desktop itself. (In KDE, plasma-desktop depends on plasma-desktop-data, but not the other way around since that would be a circular dependency: so it's quite possible to end up with one installed and not the other.) I raised this against kglobalaccel rather than plasma because I was fairly sure that something like this had probably happened, but that even if it did kglobalaccel shouldn't be grabbing keybindings on behalf of programs that aren't there, no matter how they ended up not being there :) Perhaps kglobalaccel could do a check to make sure that the app for each global shortcut is actually installed. However this seems like it's getting a bit far in the realm of bending over backwards to handle errors in configuration or packaging. :) Not saying we shouldn't do it, of course. *** Bug 442056 has been marked as a duplicate of this bug. *** |