Bug 359612 - All plasmoids lost from the desktop after setting monitor positions
Summary: All plasmoids lost from the desktop after setting monitor positions
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.5.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-20 18:57 UTC by LukasT
Modified: 2020-12-19 04:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LukasT 2016-02-20 18:57:41 UTC
I logged into Plasma5 session and saw duplicated output in my two monitors.
After correcting the ,monitor settings, I lost all the configuration of the plasmoids I had on one of my monitors. I did not have any plasmoids on the other monitor.

Reproducible: Sometimes

Steps to Reproduce:
1. Plasma5 session started weirdly: in my two monitor setup, one is on the left of the other. They both shared the same output (duplicated output)
2. In Display Configuration correct the monitors (set one as left to the other), click Apply
3. All the plasmoids and their settings are lost from the two monitor setup.

Hard to reproduce, it happened for the second time in last 6 weeks.

Actual Results:  
Duplicated output, lost plasmoid settings

Expected Results:  
Everything works flawlessly.

NVidia driver:
version 358.16 (buildmeister@swio-display-x64-rhel04-12) 
Mon Nov 16 19:58:01 PST 2015  The NVIDIA X Server Settings tool
Comment 1 Marco Martin 2016-03-02 11:05:02 UTC
what's probably happening is that the containment for the screen gets swapped for a new, empty one
Comment 2 Justin Zobel 2020-11-19 03:56:25 UTC
Thanks for the report.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 Bug Janitor Service 2020-12-04 04:34:05 UTC
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!
Comment 4 Bug Janitor Service 2020-12-19 04:35:37 UTC
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!