Version: unspecified (using Devel) OS: Linux I wanted to have diff wallpapers / workspace so I activated this option. This let me do what I wanted but then, trying to add items from amarok's collection to the playlist resulted in those items ending up as "plasmoids" on workspaces 2 and 3 if I was happening to use workspace 1. I thought maybe I needed to restart my session so I logged off and on again. This time, the plasmoids showing my /home folder did not start up. Or so I thought. I went and deactivated the option and poof, I had a functional desktop again. Plamoids showing my home folder back where they were supposed to be, adding items from collections to the playlist in amarok worked again. Reproducible: Didn't try Steps to Reproduce: Activate the option "different widgets for each desktop" in the pager options panel. Actual Results: Results in broken desktop. Expected Results: Changes made on one workspace should affect only that workspace.
Yes, I'm with KDE 7.4.7 and my widgets dissapear when I enable this option, but it doesn't brake the desktop - I can place new ones and everything works
Ok. now please try the things I mention with amarok (for me it happened with version 2.5 of the player). See if you find your songs scattered one any of the workspaces after trying to drag them from the collection to your play list.
4.7.4* typo (In reply to comment #1) > Yes, I'm with KDE 7.4.7 and my widgets dissapear when I enable this option, but > it doesn't brake the desktop - I can place new ones and everything works
*** Bug 283653 has been marked as a duplicate of this bug. ***
*** Bug 289705 has been marked as a duplicate of this bug. ***
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 is already 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