Version: 4.2.4 (KDE 4.2.4) (using 4.2.4 (KDE 4.2.4), Mandriva Linux release 2009.1 (Official) for i586) Compiler: gcc OS: Linux (i686) release 2.6.29.6-desktop586-2mnb During operation of my Mandriva 2009.1 system, my home directory space was consumed to 100%. This led to the total loss of all bookmarks in konqueror(!?!) upon elimination of the offending files. Konqueror kept producing a message that "bookmarks could not be saved". This should not happen. No new bookmarks were added, none were edited. I was just browsing at the time my disk space ran out yet this led to the total loss of all my bookmarks. The bookmark file should be unaffected by disk space issues just as all my pdfs, txt files, etc, are unaffected by disk space. The bookmarks file only needs updating/saving when something actually changes and THEN it should fail safe such that if disk space runs out while attempting to add a new bookmark or change the layout/order of current bookmarks that no change is made and the immediate previous bookmarks file remains unchanged.
A similar bug was fixed in KDE4.3.2/4.4, the config files were being saved empty with a disk-full situation: bug 206596 I wonder if it could be the same. Regards
This just happend to me, too (kde-4.4.4). This is a bug that really can make you angry, as it _SHOULD NEVER HAPPEN_. I've had this error before (year(s)(?) ago), and the only thing that doesn't make me destroy my desk chair is the knowledge of me having a backup. This is a major broken "feature" and should have been fixed a long time ago.
This bug is _still_ valid in KDE-4.5.2.
Konq is the only browser in which i like use bookmarks. It's very stupid to lost them. This bug also exist with some files on kontact. KDE-4.4.5
Still valid for 4.5.4! :-(
*** This bug has been confirmed by popular vote. ***
Just got biten by this myself. KDE SC 4.9.0. /home mounted as ext4. In my case, the first 10-15 bookmarks (out of ~150) made it to disk. This is a nasty one, nobody likes his bookmarks deleted. Hopefully it's just a matter of doing the normal write-fsync-move danse ?
*** Bug 182985 has been marked as a duplicate of this bug. ***