Version: (using KDE 4.2.4) OS: Linux Installed from: Gentoo Packages This bug is since 4.2.1. Setup: two monitors, configured w/twinview - kde puts the main panel on the 'right' display - login is on the 'left' display case 1: Physically remove the 'left' display from the system before starting kdm. Login, and the main panel is nowhere to be seen. case 2: - Login, then go to System Settings -> Display - in the size drop down, change it from '2560x1024' to '1280x1024' The display on the 'left' goes blank, all of the windows get moved to the 'right' display, but the panel does not get moved with it, leaving it totally inaccessible. Because the panel still exists, but is beyond reach, it can't be moved or removed. Also, since notifications go to the existing taskbar in the panel, they can't be seen or controlled. Furthermore, creating a new panel on the remaining visible desktop and adding a second taskbar to it doesn't result in a taskbar populated with all the items from the already-existing-yet-invisible taskbar--thus limiting some of the overall desktop functionality. For starters, it would be really nice if someone who knows could tell me what config file to edit to move the location of the existing panel to the remaining screen, since this whole exercise was discovered by trying to remove the extra CRT from my desk. I've played around with several config rc files w/no luck so far.
More info: Trying something else: I set up the single display in xorg.conf, with all twinview disabled. The panel is still hidden. And more: I set up the single display with a virtual size of 2560x1280: - the kdm login has the full size (you can pan it to the right--thus the login is on the 'left' half - after login, it went away - opening up the System Settings -> Display window and setting the display size to 2560x1280 restores the ability to pan to the right, but: - now on the 'right' half there is no wallpaper, one konsole window was put there, but the panel still does not shows up on either half.
s/2560x1280/2560x1024/
*** This bug has been marked as a duplicate of bug 183280 ***