Summary: | Plasma desktop settings lost after every system crash | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | karl.r.ernst |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | adriano.vilela, amyekut, andre.cbarros, asraniel, francoisprunier, kdebugs, maris.kde, michal, r.maurizzi, rocketraman, rserral |
Priority: | NOR | ||
Version: | 4.8.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
karl.r.ernst
2010-10-21 17:35:15 UTC
this should not happen. plasma saves it's config periodicaly. At most you should lose something like 2 minutes of configuration. 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, Andre Hi, 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. 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, Regards, André 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. Regards, Francois Andre, 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. 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. 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. Adriano 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! 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? Confirmed by comments. 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. It doesn't just happen after a crash -- it seems to happen with normal restarts too. See Bug #346558. Here is a bug I posted on the KUBUNTU pages. Seems similar to the presebt bug. Since 2010 and not fixed??? -------- Title: "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 screen. This forces me to rearrange the icons every time I reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1584304/+subscriptions 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?) I'm on Plasma 5.7.3 now, and haven't had this happen any more. Seems to be fixed! 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). Hello! 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 |