Bug 172730

Summary: Preview only, but no photo details shown at all
Product: [Applications] digikam Reporter: René Krell <renda.krell>
Component: Preview-ImageAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, marcel.wiesweg
Priority: NOR    
Version: 0.10.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 7.2.0
Sentry Crash Report:
Attachments: The empty image panel

Description René Krell 2008-10-13 17:18:17 UTC
Version:           0.10.0-beta4 (using 4.1.2 (KDE 4.1.2) "release 44.5", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.16-0.1-default

Since beta4, clicking on a photo in preview shows an empty (grey) panel, none of my photos can be watched anymore. This is new in beta4, this worked still in beta3.
Comment 1 René Krell 2008-10-13 17:42:08 UTC
Created attachment 27858 [details]
The empty image panel

There should be the photo visible I clicked on in the big grey panel. Pressing Escape I get back into the photo preview, where I can see a couple of photos.
Comment 2 caulier.gilles 2008-10-13 18:16:48 UTC
remove your ~/.kde/share/config/digikamrc and try again.

Gilles Caulier
Comment 3 René Krell 2008-10-13 18:26:40 UTC
Thank you. OK, I did this with the following effects:
- There were missing the preview photos of the albums again, already reported in http://bugs.kde.org/show_bug.cgi?id=171310 (marked as fixed)
- Following the hints in the above bug report, I switched between to tag view and back to album view. Now the preview photos were visible again.
- Now the photos are visible as expected.

That means, it works, but an older bug or side effect returned here.
Comment 4 René Krell 2008-10-13 18:33:40 UTC
Subsequent starts of digikam show the previews of photos automatically again.
The problem with the previews occured only on first start of Digikam after removing the digikamrc.
Comment 5 Marcel Wiesweg 2008-11-29 18:50:28 UTC
Most likely the same problem as the infamous bug 173746

*** This bug has been marked as a duplicate of bug 173746 ***
Comment 6 caulier.gilles 2020-09-22 04:15:45 UTC
Fixed with #173746