Bug 381270

Summary: Plasma lost all my configuration when connected to another screen while using activities
Product: [Plasma] plasmashell Reporter: humufr
Component: generic-multiscreenAssignee: Aleix Pol <aleixpol>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bhush94, jaap.geurts, nate, plasma-bugs
Priority: NOR    
Version: 5.10.2   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description humufr 2017-06-16 08:02:23 UTC
I just lost nearly all my configuration I made on my activities:

- wallpaper
- layout
- plasmoid folder view associate with specific activities to separate my work as it is advised.
- notes (not very fun that part since I lost information that was short lived but important and not saved anywhere else which is obviously my mistake but that means also that plasmoid are totally not reliable and dangerous to use)

It happen when I was on an external screen in "unify mode". I shifted to another activites and 

Thankfully I still have late dock properly configured but nearly all the other plasma configuration are lost so I do not have to configure everything from scratch.


One funny thing is one of the activities kept its own configuration when all the other went back to the new layout and default wallpaper without any plasmoid on it.

By the way I notice also that if you are changing the layout you cannot change the wallpaper at the same time you have to restart the "configure desktop" to be able to do it.

I am using the last plasma and last plasma-framework provided by archlinux:

- plasma-desktop 5.10.2-1
- plasma-framework 5.35.0-1
Comment 1 humufr 2018-06-12 10:35:13 UTC
It happen again but I am giving up on activities. Hoping that will solve my problems by using only one activities and desktops.
Comment 2 Nate Graham 2021-08-17 01:52:18 UTC

*** This bug has been marked as a duplicate of bug 391531 ***
Comment 3 Nate Graham 2021-10-06 18:35:37 UTC

*** This bug has been marked as a duplicate of bug 371717 ***
Comment 4 Nate Graham 2022-01-24 19:42:06 UTC

*** This bug has been marked as a duplicate of bug 353975 ***