Version: 4.7 (using KDE 4.7.2)
Hi there. I have a dual-head environment, with separately configured screens (X.Org manually configured, config attached). In this case global shortcuts (like audio player or volume controls) does not work, if mouse pointer (or input focus) placed on Screen1, if I move pointer to Screen0, and click there - global hotkeys works fine.
May be any workarrounds for it?
Steps to Reproduce:
1. configure X.Org to use separate screens (ZaphodHeads for radeon)
2. start KDE
3. try o use global shortcuts on secondary screen
System does not react on pressing global shortcut keys
Global shortcuts should work on every screen
If any needed - I can provide any log, output, debug info, or debug it by self.
Michael, what can I do to help fix it? I'm really don't know, what is start point to debug this really annoying issue?
Currently? Whatever you want. I am without internet (landline) for 2 month now and no end to be seen. so do not expect anything from me for the foreseeable future.
I can confirm this bug with one addition. KWin shortcuts when pressed on the second screen have no effect but when pressed on the first screen the action is initiated on each screens (for example Show Desktop Grid, Switch One Desktop to the Left, etc). An exception to this behavior that I noticed is Walk Through Windows which on the second screen does nothing, but if you press it on the first screen sometimes works correctly but some other times a box saying "*** No Windows ***" appears on the second screen. (By the way this makes Alt+Tab completely unusable, I've replaced it with some ugly hacks using xbindkeys+xdotool+wmctrl but they can never function as good as the window manager)
I can confirm that this broken behaviour is still present in KDE 4.9.1.
This is *not* a bug in KWin, but nevertheless see bug #256242 for a vast discussion on the matter (also briefly covering kglobalaccel)
The basic problem here is that kglobalaccel operates on head-unaware dbus and only runs on one head.
Thank you for the bug report.
As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.
If this bug is no longer persisting or relevant please change the status to resolved.