After configuring a second monitor in the display settings dialog, the plasma desktop that shows up in the LVDS monitor (primary output) is the one that was in VGA1 in the previous session. The one that should have been on the LVDS monitor is gone. And the VGA1 monitor is all black. You can move the mouse cursor there, but right-clicking on it doesn't show the usual menu that one would expect. Reproducible: Always Steps to Reproduce: 1. Plug-in secondary (VGA) monitor. Configure it (for example) to be on the left of the primary monitor (LVDS). 2. Customize the desktop of each monitor differently so that you can recognize which is which. E.g., use different wallpapers and add different widgets to each of them. 3. Disconnect the secondary monitor. 4. Logout. 5. Log back in. 6. Repeat step 1. Actual Results: The result is as I described above: the desktop that was in VGA1 before is now in LVDS. The LVDS desktop is gone. And the plugged-in monitor is blank, with no desktop at all (no right-click menu). Expected Results: The desktop that was originally in VGA1 should be in the plugged-in monitor, the desktop that was originally in LVDS should be in the laptop screen (i.e., LVDS monitor). If the secondary monitor is plugged in before logging in (therefore being in X's default clone mode when the session starts), and then you configure the monitor as in step 1, then things work as expected. So what triggers the bug is having no monitor at all when the session starts and then plugging it in. If it is already present in the beginning then it works.
Hello, Here is a similar problem: There are two monitors that form one extendend dekstop, two virtual desktops aligned vertically, let's call the lower one Desktop2, and two activities, Activity 1 and Activity 2. If you pause Activity 1 and return to it, then Desktop 2 of Activity 1 = Desktop 2 of Activity 2.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham