Bug 395599 - Component name for window management's global shortcuts switches between "KWin" and "System Settings"
Summary: Component name for window management's global shortcuts switches between "KWi...
Status: RESOLVED DUPLICATE of bug 400248
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (show other bugs)
Version: 5.13.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
: 358120 389819 396187 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-06-19 08:01 UTC by Christian Muehlhaeuser
Modified: 2018-10-30 21:18 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Muehlhaeuser 2018-06-19 08:01:51 UTC
I have been trying to change KWin's global shortcuts, e.g. for switching virtual desktops or the 'present windows' effect.

I'm not sure if my memory plays a trick on me, but I believe there used to be a separate component "KWin" in the sidebar. Since at least 5.13.0 KWin's shortcuts can now be found in the "System Settings" component.

I'm not sure if that's a bug or intended, but fwiw I didn't expect KWin's shortcuts in this group... I rather expected it to only contain shortcuts for, well, the app called "System Settings" (the very app I'm using to change these settings).

Since this component only contains a tree of settings for window management functions (which again is also called "System Settings" - a bit redundant maybe?), maybe it should be renamed? I understand that "KWin" might have been not ideal either, since it might not mean much to the average user, how about renaming it to "Window Management" (a term used throughout the settings experience)?
Comment 1 Nate Graham 2018-06-19 21:32:45 UTC
I've seen the same thing. This seems to switch around every release: one release it's under KWin, the next it's under System Settings. I suspect it's a bug rather than a design decision.
Comment 2 Christoph Feck 2018-06-27 16:31:15 UTC
*** Bug 358120 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2018-07-05 14:50:45 UTC
*** Bug 396187 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2018-10-27 15:36:01 UTC
*** Bug 389819 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2018-10-30 21:18:35 UTC
Just fixed with the commit that fixed Bug 400248!

*** This bug has been marked as a duplicate of bug 400248 ***