Version: 0.9.1 (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux My application data is located on a partition which is mounted rw during boot as ~/files. My photos are located in ~/files/photos. This has worked until very recently. When I try to download photos from my camera to ~/files/photos/<albumname>, the camera window shows the first image downloaded properly (green checkmark above image thumbnail), but the second and all subsequent images pop up the message "Failed to download file "IMG_1239.JPG". Do you want to continue?", and show a red X above the image thumbnail. Examining the album window, even the image that appeared to download properly isn't there. In a terminal window, "touch ~/files/test" returns the message, "touch: cannot touch `test': Read-only file system". Mount shows ~/files is mounted rw. ps -ax shows the following open processes: 8540 ? S 0:00 kio_media [kdeinit] media /tmp/ksocket-kjmck/klaunche rmpk8vb.slave-socket /tmp/ksocket-kjmck/kdedqyczeb.slave-socket 8541 ? S 0:00 kio_kamera [kdeinit] camera /tmp/ksocket-kjmck/klaunc hermpk8vb.slave-socket /tmp/ksocket-kjmck/kio_mediab4Iqsc.slave-socket 8548 ? S 0:00 kio_digikamdates [kdeinit] digikamdates /tmp/ksocket- kjmck/klaunchermpk8vb.slave-socket /tmp/ksocket-kjmck/digikamy7S9uc.slave-socket 8549 ? S 0:00 kio_digikamalbums [kdeinit] digikamalbums /tmp/ksocke t-kjmck/klaunchermpk8vb.slave-socket /tmp/ksocket-kjmck/digikam1EXioc.slave-sock et 8550 ? S 0:00 kio_file [kdeinit] file /tmp/ksocket-kjmck/klauncherm pk8vb.slave-socket /tmp/ksocket-kjmck/digikamVZq9db.slave-socket 8551 ? S 0:00 kio_file [kdeinit] file /tmp/ksocket-kjmck/klauncherm pk8vb.slave-socket /tmp/ksocket-kjmck/digikamHwzOpb.slave-socket 8557 ? S 0:00 kio_digikamthumbnail [kdeinit] digikamthumbnail /tmp/ ksocket-kjmck/klaunchermpk8vb.slave-socket /tmp/ksocket-kjmck/digikam0KBZsa.slav e-socket 8558 ? S 0:00 kio_file [kdeinit] file /tmp/ksocket-kjmck/klauncherm pk8vb.slave-socket /tmp/ksocket-kjmck/digikamOBYesa.slave-socket 8559 ? S 0:00 kio_file [kdeinit] file /tmp/ksocket-kjmck/klauncherm pk8vb.slave-socket /tmp/ksocket-kjmck/digikam0Yherc.slave-socket After exiting digikam I did the following: 1. Killed one of the digikam*.slave-socket processes that remained open. 2. umount-ed ~/files 3. mount-ed ~/files 4. touch-ed ~/files/test It appears that once digikam is started I am unable to write not only to ~/files/photos, but anywhere else in ~/files. Killing all digikam processes and remounting ~/files restores write access to my data directory. I have reproduced this behavior several times. I believe this is related to the "Failed to convert db to new db format" bug, because I got that message several times (but not of course as I tried to reproduce this bug). I am not using NFS or any other network file access method.
Kevin, Can you check if this problem still exist with last stable digiKam 0.9.2 release ? Thanks in advance Gilles Caulier
I'll investigate. Kevin On 18 Aug 2007 07:32:21 -0000 Gilles Caulier <caulier.gilles@gmail.com> wrote: [bugs.kde.org quoted mail]
Gilles, To do this I would need to update 31 packages and install 8 more; I don't know what this would do to the rest of my system. Kevin On 18 Aug 2007 07:32:21 -0000 Gilles Caulier <caulier.gilles@gmail.com> wrote: [bugs.kde.org quoted mail]
Gilles, Good news. I was backing up my system, preparing to upgrade digiKam to 0.9.2. When I did fsck on my files partition, fsck complained about a corrupted superblock. Once I fixed this problem I attached the camera and downloaded all its pictures. For now the problem has disappeared. Please close the bug; I'll watch for recurrence and post a new report if it re-appears. Thank you, Kevin On 18 Aug 2007 07:32:21 -0000 Gilles Caulier <caulier.gilles@gmail.com> wrote: [bugs.kde.org quoted mail]
As original poster you can always re-open this bug, if necessary.