Created attachment 67883 [details]
Version: 4.7.4 (using KDE 4.7.4)
I have a dual head configuration (2 separate X screens). No Xinerama, no Nvidia TwinView. I am using the main X screen (1920x1200) on my TFT display for working and the second X screen (800x600) on the TV for watching TV and videos. KDE is only being used on the main X screen.
When I press ALT-TAB, most of the time the switcher does not show on the main X screen and so I cannot switch to the next application. Instead, the switcher shows (partly in the lower right) on the second X screen. Looks like it centers like if it ran on 1920x1200, but shows on the 800x600 screen. Sometimes it works however and shows on the main X screen.
Even though I would want KDE to not use the other X screen, it displays the desktop background there.
Adding "disableMultihead=true" in ~.kde4/share/config/kcmdisplayrc prevents KDE from showing the desktop background on the other X screen, but the ALT-TAB behavior is the same.
I think this problem started with KDE 4.6 or 4.7.
There is also a thread in the Gentoo forums about this:
ALT-F2 also does not work most of the time. But I can't say, if this one opens on the other X screen, too (I don't see it there).
Steps to Reproduce:
Configure 2 X screens in xorg.conf (dual head, no Xinerama or TwinView, but totally separate X screens).
Try to switch between applications with ALT-TAB.
The switcher most of the time opens on the other X screen. Holding ALT and pressing TAB multiple times does not switch between the applications on the current X screen.
Always show switcher on current desktop.
Not a matter of the window manager but kglobalaccel (needs to be screen aware, there's only one instance passing the action to its known, ie. 1/2 of all cases the "wrong" WM)
cross check bug #256242
This behavior btw. didn't like "start" with 4.6 or 4.7 but before you simply wouldn't have a kwin instance on each screen at all.
While the other bug is a dumpster, i'll still dupe this one since a fix to either will fix both and the kglobalaccel maintainer is already attached to the other bug.
*** This bug has been marked as a duplicate of bug 256242 ***