Version: 1.0.0-beta3 (using 4.3.00 (KDE 4.3.0), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.30.1mko - Using digikam with german translation - Created new album directory - moved hundreds of image files into this directory - From menu, used "Extras" -> "Search for new pictures" - digikam found all the images/directories I moved into the directory during searching for new files After the update-dialog is gone, the list only shows empty albums ( see attached screenshot ). Clicking on one of the albums doesn't show any image !? Restarting digikam did not solve the problem. The files reside on a mounted vfat directory. The root of the album directories has the following permissions : ls -al Pictures insgesamt 6148 drwsrwsrwx 11 nobody nogroup 4096 8. Aug 01:32 . drwxr-xr-x 9 root root 4096 8. Aug 01:20 .. drwxrwxrwx 5 nobody nogroup 4096 8. Aug 01:18 Autos -rw-r--r-- 1 manuel nogroup 6217728 8. Aug 01:32 digikam4.db -rw------- 1 manuel nogroup 47 8. Aug 01:29 .directory drwxrwxrwx 50 nobody nogroup 4096 31. Jul 12:58 Familie drwxrwxrwx 15 nobody nogroup 4096 10. Jan 2009 Freunde drwxrwxrwx 5 nobody nogroup 4096 7. Jun 2007 Musik drwxr-sr-x 5 manuel nogroup 4096 8. Aug 00:38 Panorama drwxrwxrwx 2 nobody nogroup 4096 16. Okt 2007 Referenz -rw-r--r-- 1 manuel nogroup 13312 8. Aug 01:32 thumbnails-digikam.db drwxrwxrwx 31 nobody nogroup 4096 7. Jul 20:32 Urlaub_Reisen drwxrwxrwx 12 nobody nogroup 4096 7. Okt 2008 Verschiedenes drwxrwxrwx 2 nobody nogroup 4096 8. Jan 2008 Wallpaper
Created attachment 35980 [details] screenshot showing empty albums
PS: The directory is an ext3 mount
*** Bug 203030 has been marked as a duplicate of this bug. ***
*** Bug 203028 has been marked as a duplicate of this bug. ***
Which version of the debian-digikam package do you have? ( apt-cache policy digikam ) 2:1.0.0~beta3-1 is known to have these symptoms, but they are fixed in 2:1.0.0~beta3-1+b1. 2:1.0.0~beta3-1+b1 is available in the repositories, so you can easily upgrade to it: apt-get update && apt-get install digikam
Sorry for submitting this bug multiple times... My installed version is 2:1.0.0~beta3-1 I will install the latest version as soon as it's available on a official debian repository ( as this seems to be ok, according to digikam website: "Debian repositories are mostly up to date, release candidates and beta's usually are available from the experimental repository." ) I retry this issue after new version is installed.
This is usually a packaging problem with the kioslaves, not found, duplicate versions installed, binarily incompatible, whatever
...and what does this mean ?? Can I do something to solve it ?
From digiKam team, nothing can be done. Check new packages, ask to Distro team for better packaging... You can also compile digiKam by hand and install it properly... Gilles Caulier
Can digikam detect and report about such problems? Right now figuring that out is quite problematic.
This problem is relevant of digiKam KIO Slaves and all of these have been dropped in favor of a multi-threaded interface to query the database.