Version: (using KDE 4.4.0) OS: Linux Installed from: Ubuntu Packages Whenever I try to scan for new images, Digikam closes the window scanning new images at 90%. I do not have time to see if it always do that on the same image though. I deleted the digikam.db to force digikam to recreate it. It did it well but still "scan for new images" does not finish. Digikam does not crash. I'm using digikam from SVN as of 01/03/2010 on kubuntu 9.10 KDE 4.4.
Can you run digiKam in a console and post there all messages... Gilles Caulier
Does the process quit or is the main window still open and usable after the scan dialog closes? Is something missing that should be scanned, some albums or pictures not shown? Or is the problem just the dialog closing at 90%?
(In reply to comment #1) > Can you run digiKam in a console and post there all messages... > > Gilles Caulier I'll do that tonight but I did not see any messages when the windows closes. (In reply to comment #2) > Does the process quit or is the main window still open and usable after the > scan dialog closes? > Is something missing that should be scanned, some albums or pictures not shown? > Or is the problem just the dialog closing at 90%? Digikam does not crash, only the "scan images" window does.
Created attachment 41272 [details] Output from digikam loaded in command line
Thanks for your log file. I see that there is a problem with the two collections you have: "/home/nono/DocumentsMedias/PicturesVideo" and "/home/nono/DocumentsMedias/PicturesVideos". Something is wrong and leads to confusing albums in PicturesVideos/ with PicturesVideo/s/. Now, with a quick test, I could not reproduce this problem. I would ask you two things: - backup and remove your database file, "/home/nono/DocumentsMedias/PicturesVideos/digikam4.db". With a recent version, try to add again your two collections. If that works, your problem was due to a bug in digikam that is now fixed. - if that does not work, please send me the newly created digikam4.db file Thank you
Using Digikam > 1.3 it does happen anymore. Must have been fixed. Thanks