https://bugs.kde.org/show_bug.cgi?id=226853 Summary: No images shown after upgrading from previous version
image database
Product: digikam
Version: 1.1.0
Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo:
[hidden email]
ReportedBy:
[hidden email]
Version: 1.1.0 (using KDE 4.4.0)
Compiler: gcc
OS: Linux (i686) release 2.6.25.20-0.5-pae
Installed from: openSUSE RPMs
After updating digikam from version 0.9.3, to 1.1.0 and launching the
application the welcome wizard appears asking for album and database file
locations.
Both were kept previously at the same location on a mounted NFS4 share with
properly set-up file locking (lockd) so the SQLite engine ran flawlessly with
version 0.9.3. (took me a few days to get it working trying it with NFS3 in
unsuccessfully). I tried all the below on a local drive as well just to make
sure and the same thing happens.
After entering the locations the wizard recognized the previous database file
and asked to choose between upgrading it or creating a new DB. As I had lots of
tags/ratings I decided to go for the upgrade. It started crunching the files,
it was 60+ GB so it took a while but finished successfully.
After the upgrade I could not see any images in the browser window.
The followings work properly:
- all albums were shown properly
- Creating/deleting new albums works properly
- all my old tags were imported properly
- all import/export functions, bulk tools saw all images, the OpenGL image
viewer displayed the slideshow properly
The following does not work:
- None of the original images are shown in the browser window
- Selecting "Scan for new images" scans all the images but still nothing is
shown
- Making a change on the file system (renaming an album folder) and then "Scan
for new images" scans all the images and properly detects the change in the
album structure but no images are shown
- Selecting "Rebuild Thumbnails" starts rebuilding thumbnails but after
completing still no images/thumbnails are shown
The following scenario I carried over might help to tackle the issue:
- Creating a new album named Test - success
- Importing an image file from a memory card a.jpg works and the newly imported
image's thumbnail shows properly. All image related functions work properly
(tried: editing, saving, emailing, assigning tags, modifying EXIF data)
- mv a.jpg b.jpg - digikam detects the change and the image is displayed
correctly
- cp b.jpg c.jpg - digikam detects the change and both images are displayed
correctly
- cp ../Existing_album/existing_file.jpg ./d.jpg - the new image d.jpg is not
shown (../Existing_album/existing_file.jpg was in the old DB so subject to the
upgrade process)
- mv d.jpg e.jpg - nothing changes only b.jpg and c.jpg are displayed (same
image)
- mv e.jpg c.jpg - whoops, digikam detects the change and the second thumbnail
is replaced with the new content
- cd ../Existing_album
- touch * - nothing happens, still no images are displayed
This is where I stopped. Somewhere the watching algorithm for directory content
changes an the DB upgrade output mess up with each other I suspect, knowing
virtually nothing of digikam internals.
--
Configure bugmail:
https://bugs.kde.org/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
