First I want to say it has improved from user edition, it remember panels position on a single setup, but still there exist some problems with unplugging/plugging monitors, behavior is inconsistent, I will try to explain it telling my experience... :) 1. I booted after the install, updated the system, all fine, disabled a weird "VGA display" that shows here but did not exist, move external monitor orientation to the left of my notebook, add 2 panels (the left monitor I put the panel on left, the wright I put the second panel on wright) and reboot. 2. After rebooting, all fine (YAY! User edition did not remember the panels position still). So I unplugged the monitor. 3. When I unplug the monitors, I see no panel "ok, different settings per display setup maybe, great, it is more flexible!" I thought. So I add a panel to my "single monitor setup" at left side of screen. 4. Then I plug monitor again and, well... It remembers my "single monitor setup" panel... Here start the inconsistency, now I have 3 panels with 2 overlapping , on the left side of the left display. 5. Plug, unplug, and well, fine it appears to remember, so I reboot, and the 3th panel goes to the wright of the second monitor. Reproducible: Always Actual Results: Inconsistent behavior, It remember or not settings, they are disconnected? At the moment it is a mix. Expected Results: I liked when I thought that plugging or unplugging a monitor plasma get a completely different set of settings (panels, their positions, widgets, display monitor settings, position, what is enabled and not), but it need to be well defined, when plugging, forget panels form "single monitor setup", when unplugging, forget "dual monitor setup" and restore "single monitor setup". This is my Opinion, but I will be pretty much happy if plasma stay consistent any way (remember display characteristic... if it has only one panel, in any setup this monitor stay the same) It can be useful to know my external monitor is 2560x1080 and the notebook one is 1920x1080.
Isn't this duplicate of the famous bug 356225 (now at 272 comments)?
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!