Bug 366211 - When changing database, cannot open thumbnails into edit window
Summary: When changing database, cannot open thumbnails into edit window
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Database (show other bugs)
Version: 5.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-28 18:02 UTC by higdon001
Modified: 2018-12-22 23:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description higdon001 2016-07-28 18:02:53 UTC
This happens when I swap from one existing database to another:  all files and tags are all available in the database I have moved to, but, when I click on a thumbnail or try to edit the image all I get is a blank screen.  If I then close down Digikam, and bring it back up all functionality is fully restored.

Reproducible: Always

Steps to Reproduce:
1.Use setting, database configuration to move from one existing database to another existing database.
2.Select any thumbnail and try to edit the image.
3.

Actual Results:  
Blank screen instead of enlarged image.

Expected Results:  
Edit screen with image in.

As stated in description above, if I then close down digikam and then reload, full functionality is restored.

Note: operating system Windows 8.1
Comment 1 caulier.gilles 2016-07-28 20:51:17 UTC
Swati,

It's fully reproducible under Linux and OSX. The new database is not fully available to work after changes.

Sound like a call or a sequence is missing in setup dialog to close current database and re-init properly the database accordingly with new backend selected in config.

Gilles Caulier
Comment 2 swatilodha27 2016-08-08 14:04:53 UTC
I confirm this too under Linux. It's reproducible maximum times. 
DB is fully restored only after restarting DK.
Comment 3 Maik Qualmann 2018-12-22 23:46:57 UTC
This is now fixed in digikam-6.0.0-beta3 because the ItemInfo cache is deleted.

Maik