Kubuntu Hardy: Dolphin: unable to save bookmarks

[Kivech]

Binary package hint: dolphin-kde4

When trying to exit dolpin while browsing my home directory, I got this error message:

Unable to save bookmarks in /home/marc/.kde/share/apps/d3lphin/bookmarks.xml. Reported error was: Permission denied. This error message will only be shown once. The cause of the error needs to be fixed as quickly as possible, which is most likely a full hard drive.

This is with 175.8 Gb free reported by dolphin. As opposed to what the message claims, the message is not shown only once but now every time I try to close dolphin after I opened my home directory from the taskbar: System Menu>Home Folder.

At first I didn't have this message, but only after resizing the window and wanting to close it to save the new window size, I got this message that now shows up every time I try to close dolphin. Resizing the window again, doesn't make the error message go away.

[Harald Sitter (apachelogger)]

The message is not related to KDE 4
Anyway, the file is having a wrong permission (I guess it is owned by root)
sudo chown $USER:$USER /home/marc/.kde/share/apps/d3lphin/bookmarks.xml
should fix this issue.
Thanks for this report nonetheless.

[Kivech (kivech-deactivatedaccount)]

It seems only to happen when someone as root has used dolphin.

One can solve the bug by using rm /home/marc/.kde/share/apps/d3lphin/bookmarks.xml at the terminal.

Clearly, it was trying to overwrite the one that belonged to root. Obviously the system should deal with this in such a fashion that it shouldn't be a problem to switch from root to regular user. That is, if this is possible.

If this turns out to be difficult, one could opt for the system automatically not saving these type of settings for a root user, considering that Kubuntu doesn't know a root user account where one normally would store these settings.

[Kivech (kivech-deactivatedaccount)]

We cross posted, thanks for the reply. Just wanted to make you aware of this minor issue.

[Harald Sitter (apachelogger)]

Please also see Bug #198429 :)