Bug 370143 - Desktop Settings doesn't save changes after logout
Summary: Desktop Settings doesn't save changes after logout
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (show other bugs)
Version: 5.8.0
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-05 18:23 UTC by cdnr
Modified: 2017-04-23 07:39 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cdnr 2016-10-05 18:23:12 UTC
see summary

Reproducible: Always

Steps to Reproduce:
1.open Desktop Settings
2.change layout to Folder View
3.or change Wallpaper Positioning to smth different
4.logout

Actual Results:  
Desktop Settings is on it's defaults


Fresh neon-useredition-20161004-1607-amd64 installation
Comment 1 Aaron Wolf 2016-10-08 17:26:18 UTC
confirmed as having the issue here
Comment 2 mensched 2016-10-26 10:52:59 UTC
confirmed on Debian Testing. 

For me also desktop widgets are not displayed any more after logout, login.
Comment 3 mensched 2016-10-26 22:40:21 UTC
It works for me now as it should with Plasma 5.8.2. Thanks!
Comment 4 Adrian Piotrowicz 2016-10-27 06:23:13 UTC
I have 3 monitor setup and one of my monitors is constantly being reset to default settings.
Also I need to reboot plasma via "kquitapp5 plasmashell && kstart5 plasmashell" after login to make it correctly setup primary display - my primary display is always the one on the left rather the one I want - center.


Bug is not fixed on Plasma 5.8.2
Comment 5 tromzy 2016-11-07 10:36:35 UTC
I can confirl this bug on Plasma 5.8.3 on the radeon free driver (Arch Linux).
Comment 6 Adrian Piotrowicz 2016-11-22 08:09:11 UTC
So... I've done some testing/observations on ".config/plasma-org.kde.plasma.desktop-appletsrc" file.
I've created a simple reader for that file which creates JSON data from it's contents and I've noticed that after each reboot plasma adds a new 'Containment' to that config. Situation changes after calling "kquitapp5 plasmashell && kstart5 plasmashell" which I'm using to sanitize plasma.
After first call after reboot Plasma adds another Containment in that config.
After second call Plasma removes two Containments from that config. 
And here is what is odd - Plasma removes not those two newly created Containments but rather two previous (leaving newest one).

Numbers will be easier:
I've got few Containments and highest number is 61
FULL REBOOT
Plasma adds Containment 62
"kquitapp5 plasmashell && kstart5 plasmashell"
Plasma adds Containment 63
"kquitapp5 plasmashell && kstart5 plasmashell"
Plasma removes Containment 61 & 62
"kquitapp5 plasmashell && kstart5 plasmashell" * N
Situation is stable - no changes to configuration file
FULL REBOOT
Plasma adds Containment 64
"kquitapp5 plasmashell && kstart5 plasmashell"
Plasma adds Containment 65
"kquitapp5 plasmashell && kstart5 plasmashell"
Plasma removes Containment 63 & 64
"kquitapp5 plasmashell && kstart5 plasmashell" * N
Situation is stable - no changes to configuration file

This situation is under 3 monitor setup.
Comment 7 Adrian Piotrowicz 2016-11-22 08:24:52 UTC
When I'm not docked (no external monitors attached) nothing happens to config file after full reboot or plasmashell restart.

However:
When i docked plasma created new Containment - 66
Desktop was a mess so "kquitapp5 plasmashell && kstart5 plasmashell"
Plasma removed Containment 65
"kquitapp5 plasmashell && kstart5 plasmashell" * N
Situation is stable - no changes to configuration file
Comment 8 Jetchko Jekov 2016-11-23 10:01:26 UTC
I can confirm that weird behavior on Fedora 25 / Plasma 5.8.3 / Intel IGC
Dual monitor setup.
Comment 9 Jetchko Jekov 2016-11-30 09:32:20 UTC
For me this problem got fixed with upgrading to plasma 5.8.4
Comment 10 tromzy 2016-11-30 09:34:48 UTC
Plasma 5.8.4 fixed it for me too.
Comment 11 Adrian Piotrowicz 2016-11-30 12:08:09 UTC
Same here - 5.8.4 fixes the problem.
Comment 12 Marcos Paulino Roriz Junior 2017-04-23 07:39:48 UTC
I'm still having this issue on KDE 5.8.5 in Kubuntu 16.04.
Any idea on how to fix it?