Bug 187032

Summary:	stored kde session is lost after powerdown without shutdown
Product:	[Unmaintained] ksmserver	Reporter:	Marc Schoechlin <ms-kdebugs>
Component:	general	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ms-kdebugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marc Schoechlin 2009-03-13 10:48:15 UTC

Version:           kdebase-workspace-bin  / 4:4.2.1a-0ubuntu1~intrepid1 (using KDE 4.2.1)
OS:                Linux
Installed from:    Ubuntu Packages

I configured the following option in system-settings:

 - System-Settings -> Advanced -> Session Manager -> On Login -> Restore manually stored session
 - After customizing the desktop select the follwing action in application launcher
   Application Launcher -> Leave -> Save Session

If my system is now stopped without a shutdown (i.e. if my laptop now runs out of battery power)
almost (i.e. not the modifications in the application launcher) all the stored desktop settings 
stored by the "Save session" operation are lost.

This is not what i expect :-)

This also happens for other settings in "System-Settings -> Advanced -> Session Manager -> On Login"

I really like KDE, thanks for writing this great desktop!

Comment 1 Oswald Buddenhagen 2009-05-30 20:16:28 UTC

this sounds like another instance of the "zero-sized files after crash" problem. are you using ext4 or xfs by any chance?

Comment 2 Marc Schoechlin 2009-05-31 08:04:07 UTC

Indeed i use XFS for my homedir....

$ find . -size 0
./share/apps/kabc/std.vcf
./share/apps/kabc/std.vcf_2
./share/apps/kabc/std.vcf_4
./share/apps/kabc/std.vcf_5
./share/apps/kfileplaces/bookmarks.xml.tbcache
./share/apps/networkmanagement/connections/{bd8889e3-347a-4479-8114-d9d0b07066ba}
./share/apps/amarok/my.cnf
./share/apps/amarok/mysqle/amarok/composers.MYD
./share/apps/amarok/mysqle/amarok/amazon.MYD
./share/apps/amarok/mysqle/amarok/lyrics.MYD
./share/apps/amarok/mysqle/amarok/devices.MYD
./share/apps/amarok/mysqle/amarok/urls.MYD
./share/apps/amarok/mysqle/amarok/labels.MYD
./share/apps/amarok/mysqle/amarok/playlist_tracks.MYD
./share/apps/amarok/mysqle/amarok/playlist_groups.MYD
./share/apps/amarok/mysqle/amarok/artists.MYD
./share/apps/amarok/mysqle/amarok/podcastchannels.MYD
./share/apps/amarok/mysqle/amarok/podcastepisodes.MYD
./share/apps/amarok/mysqle/amarok/images.MYD
./share/apps/amarok/mysqle/amarok/genres.MYD
./share/apps/amarok/mysqle/amarok/playlists.MYD
./share/apps/amarok/mysqle/amarok/tracks.MYD
./share/apps/amarok/mysqle/amarok/statistics.MYD
./share/apps/amarok/mysqle/amarok/urls_labels.MYD
./share/apps/amarok/mysqle/amarok/albums.MYD
./share/apps/amarok/mysqle/amarok/years.MYD
./share/apps/amarok/dynamic.xml

Comment 3 Oswald Buddenhagen 2009-05-31 10:21:04 UTC

you will certainly have even more of these right after the crash before kde boots up and re-intializes (many of) the configs.

you will find some semi-good news in the linked report, but that's about all we can offer.

*** This bug has been marked as a duplicate of bug 187172 ***