https://bugs.kde.org/show_bug.cgi?id=58954
--- Comment #19 from Kai Krakow <kai kaishome de> 2009-05-10 18:21:26 --- Maybe it would be generally good practice (if not best practice) to split all config files in that way, that writing pure configuration (which only occurs when I reconfigure something) to another config file which is thus pretty stable and not subject to change often, and writing session specific configuration (like ids, position data, column ordering etc) to its own config file. The idea behind it is: It wouldn't be that hard to loose position data of plasmoids (I can simply move them where they've been) or mail listing settings (just a few clicks to reconfigure that), but it is very very annoying to find a completely zero state default plasma desktop, or find all your filter and account settings in kmail lost. :-( Of course this solution only alleviates the symptoms, the long term target should be to cure the root cause (wrong interaction with the filesystem, bad filesystem behaviour). One cannot guarantee that desktop systems are totally stable - there are many causes for power outage or hard locks: Instable graphics drivers (this doesn't only relate to closed-source drivers!), lack of ups'es (shutdown due to vis major), running out of battery (laptop). It's pretty normal that desktop systems run in hostile environments so the desktop environment should be implemented in a way to support this. Strange enough is that server software components are designed to support hostile environments better although these are usually run in friendly environments (good cooling, ups, no console with a human "attached"). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
