Bug 254884 - Plasma desktop settings lost after every system crash
Summary: Plasma desktop settings lost after every system crash
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: 4.8.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
Depends on:
Reported: 2010-10-21 17:35 UTC by karl.r.ernst
Modified: 2018-06-08 18:34 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description karl.r.ernst 2010-10-21 17:35:15 UTC
Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

I know it shouldn't crash in the first place, but sometimes it is just inevitable.

This happens every time when the system is forcefully shut down, including but not limited to:
- restart with reset button
- power outage
- kernel panic/freeze

If this happens, all plasma desktop settings get reset to their default, e.g. background image, all widgets get removed and the single default folder view is added. Other settings like k-menu or taskbar appearance are unaffected.

Reproducible: Always

Steps to Reproduce:
1. set your desktop to somethign non-default
2. restart, just to make sure changes are properly written to disk
3. note how your settings are still there
4. cut power / remove battery / push reset button ...

Actual Results:  
Desktop settings set back to default

Expected Results:  
Desktop settings should be the same as after the restart

NOT a filesystem / caching issue, tested on 2 different PCs, same behaviour
Comment 1 Beat Wolf 2010-10-21 21:06:42 UTC
this should not happen. plasma saves it's config periodicaly. At most you should lose something like 2 minutes of configuration.
Comment 2 andre.cbarros 2010-11-26 10:42:00 UTC
I have experienced this bug a couple of times. When plasma crashes and restart it creates a new activityID and, since there are no settings saved with the new identifier, it creates default activities for every virtual desktop.

I have restored my desktop many times after playing with plasma-desktop-appletsrc and plasma-desktoprc (~/.kde4/share/config). All is needed is to replace the old activityId with the new one on plasma-desktop-appletsrc and replace on [viewIds] the numbers of the new activities with the old ones.

Besides, I think that the source of the many problems people have reported is to use a "random" generated identifier on a configuration file! It should never be there and, frankly, I fail to see why is it needed. I makes things hard to move around and creates this kind of bug.

Best regards,
Comment 3 Francois Prunier 2010-12-03 18:47:28 UTC

This just happened to me. I had all my settings set since a month so it's not something related to a crash just after setting a config.

I restarted KDM because KDE would not let me log out (unrelated, I don't know why it happened). KDE then restarted and all my settings were lost: default wallpaper, plasmoid runnings but notes empty and not at the right place.

KDE 4.5.1 on Kubuntu 10.10.
Comment 4 andre.cbarros 2010-12-04 23:23:18 UTC
Do what I described and you will be able to restore your settings. On my post I forgot to say that you need to switch to an other desktop/window manager to be able to do that (for example, login on openbox or something else instead of kde). After you restore your options, I suggest you to backup your configuration (it will help only to a extent - whenever a new identifier is generated you will need to go to this process again).

May you need a help, let me know,

Comment 5 Francois Prunier 2010-12-05 16:11:15 UTC
Thanks Andre but I manually set up my desktop again. 

I'd like to see the bug fixed though, this should not happen IMO. I don't see why a new activty ID is generated when plasma crashes and that would create new settings.

Comment 6 Francois Prunier 2010-12-06 12:29:54 UTC

I've just noticed that a new activity is created in plasma when it crashes, that's why brand new settings are visible. So it's very easy to restore your previous setting by selecting your old activity back and deleting the new one.

Still a bug IMO, but at least it's easy to recover from this one.
Comment 7 René Serral 2011-01-16 20:01:29 UTC
I have the same issue with a recent svn checkout of the 4.6 branch, I get an empty desktop randomly after logouts. I didn't experience the bug in 4.5 though.
Quite annoying in my opinion even if you can recover them manually.
Comment 8 Adriano Vilela 2011-04-14 01:57:03 UTC
This happens to me everytime the system crashes. I have been getting a lot of system crashes lately, apparently because of some regression in the radeon driver in kernel 2.6.38. Once I reboot and get back to KDE, all my settings are gone. Fonts, color schemes, dolphin settings, everything goes back to their default values. It's very annoying.

I'm using KDE 4.4 on Debian Testing.

Comment 9 Māris Nartišs 2012-01-28 15:49:01 UTC
I also got hit by this bug on 4.8.0. 

I found that plasma-desktop-appletsrc still contains notes from my notes applet (the most painful thing to loose), still I wasn't able to figure out what and where I have to replace to get my old settings back. I was trying different things with activityId, as suggested in #2, still I got only something like 5 new activities and none of them contains old content :(

Please provide step-by-step instructions for all unhappy users while developers are occupied implementing new and cool desktop effects. Thanks!
Comment 10 Roberto Maurizzi 2012-02-07 06:29:35 UTC
I confirm seeing this on Kubuntu since at least 4.5
Right now, due to a crash bug on logoff caused by interactions between video drivers and the new splashscreen they use, it resets my whole desktop at least twice a week.

If I backup ~/.kde/share/config/plasma-desktop-appletsrc can I simply recover everything restoring it?
Comment 11 Myriam Schweingruber 2012-05-17 19:05:28 UTC
Confirmed by comments.
Comment 12 Micha 2013-01-19 13:01:06 UTC
I confirm, this affects me too.
Some tome ago i was using kmail as it was the best mail program for me, but always after crash everything was gone. Now i use thunderbird instead. I had gbytes of mail to download from my imap server after every crash. It was painful.
Comment 13 Raman Gupta 2015-12-22 01:04:52 UTC
It doesn't just happen after a crash -- it seems to happen with normal restarts too. See Bug #346558.
Comment 14 Amnon 2016-07-25 12:53:07 UTC
Here is a bug I posted on the KUBUNTU pages. Seems similar to the presebt bug. 

Since 2010 and not fixed???


  "folder view": icon placement lost after reboot

Bug description:
  I use "folder view" layout in KUBUNTU. I like the icons on the secreen
  arranged in a particular way.

  After system reboot the icons get moved to the left side of the

  This forces me to rearrange the icons every time I reboot.

To manage notifications about this bug go to:
Comment 15 Amnon 2016-07-25 13:03:10 UTC
Here is my system:
 Dell desktop Optiplex 790 
 Kubuntu 16.04
 plasma ver 5.5.5
 qt ver 5.5.1
 kernel ver 4.4.0-31-generic
 os type 64 bit

Using Hebrew characters in some file names (can this have an effect?)
Comment 16 Raman Gupta 2016-09-01 14:27:37 UTC
I'm on Plasma 5.7.3 now, and haven't had this happen any more. Seems to be fixed!
Comment 17 andre.cbarros 2016-09-06 21:24:46 UTC
OK, I don't know if it is still the same problem and if the old correction still applies. Things have changed a little. You still have to look at ~/<kde_settings>/share/config/plasma-desktop-appletsrc. Look for ActivityId value. The different part now is that the configuration file that needs to be fixed is inside activitymanagerrc (is in same directory).

Had not experienced this for a looooong time (actually, not since 2011).
Comment 18 Nate Graham 2018-06-08 18:34:09 UTC

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham