Hello, I have a laptop that I connect it to an external monitor and use a multi screen setup. In this case, I always want to have the plasmoids to be put on the primary output which I usually set it to be the laptop screen. The problem is that when I put the laptop on the right side of my desk and the external monitor on the left side of it, my plasmoids are moved towards the right edge of the screen and if the external screen's horizontal resolution is larger that this of the laptop, then they are pushed as much to disappear. If I put the laptop on the left side everything looks fine. Now if I choose the external monitor which is on the left to be my primary output, the plasmoids are shown properly on this monitor, so my conclusion is that I can only have my plasmoids on the left monitor no matter what. Reproducible: Always Expected Results: Plasmoids should be placed properly in the primary output no matter if it is left, right, above, below or anywhere else it could be.
Same thing happens to me. I use Linux Mint 14 KDE version. Always when connecting the HDMI and selecting laptop display as the main display and setting something else than clone for HDMI (ex.above), then background and widgets disappear as if I was on a brand new activity with nothing set up.
Created attachment 88349 [details] Snapshot of the 2 screen setup showing the activity using only the right side of the main screen.
I have a similar problem with KDE 4.13.3 on Ubuntu. It affects the Search and Launch and Homerun activities most as the widgets are displayed as if the left of the main screen is not there. It is displayed, but not used by the activity. A workaround which Earl Ruby posted for Bug 312190 worked for me on system startup, but unfortunately, stopping the activity and restarting it redisplays the problem until I reboot.
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