Bug 379110 - Plasma is not saving desktop setting (folder view) after logout
Summary: Plasma is not saving desktop setting (folder view) after logout
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (show other bugs)
Version: 5.8.5
Platform: Ubuntu Linux
: NOR major
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-23 07:48 UTC by Marcos Paulino Roriz Junior
Modified: 2020-01-22 18:49 UTC (History)
3 users (show)

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

Attachments
plasma config (4.70 KB, text/plain)
2017-04-23 07:48 UTC, Marcos Paulino Roriz Junior 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos Paulino Roriz Junior 2017-04-23 07:48:54 UTC 
Created attachment 105155 [details]
plasma config

Hello everyone, I'm having a major issue when trying to change my plasma shell view to folder view (showing desktop). Precisely, when I reboot or logout it restores the plasma view to its default view. I'm running KDE 5.8.5 on Kubuntu 16.04.

This bug seems to be a follow up of https://bugs.kde.org/show_bug.cgi?id=370143, which tried to fix this issue in 5.8.4. However, it still appears in KDE 5.8.5 on Kubuntu 16.04.
Comment 1 Adrian Piotrowicz 2017-06-29 06:55:59 UTC 
I was having same issue while back on <=5.8.3 it was fixed for me on 5.8.4, and now it returned in >=5.10.0
However for me it happens when I'm switch from/to docking station. Settings are saved between sessions.
Number of [Containments] in .config/plasma-org.kde.plasma.desktop-appletsrc is raising.
Because of this issue I've given up on customizing desktop... The only thing that gives me PIA is icons on desktop - which I truly hate ;)
Comment 2 Alexander Mentyu 2017-12-07 13:26:07 UTC 
Can't reproduce in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Type: 64-bit
Comment 3 Nate Graham 2020-01-22 18:49:11 UTC 
Yeah, this was fixed a while ago.