Bug 400962 - Image editor doesn't display the image
Summary: Image editor doesn't display the image
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ImageEditor-Load (show other bugs)
Version: 5.9.0
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-12 11:44 UTC by m*sh
Modified: 2022-02-03 03:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0
Sentry Crash Report:

Attachments
Blank screen in image editor (21.54 KB, image/jpeg)
2018-11-12 11:44 UTC, m*sh 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description m*sh 2018-11-12 11:44:13 UTC 
Created attachment 116260 [details]
Blank screen in image editor

Image Editor doesn't display the image after first use.
If digikam is started new, the image editor works but is shown without menue. Can right click and get the main toolbar and edit the image. Editing another image fails and shows a blank screen.
Tried to repair database without success.
Deleted the database and recreated it. Problem persists with JPG and RAW images.

OBSERVED RESULT
Blank screen when opening 2nd image in the editor 

EXPECTED RESULT
Showing the image and Menu
Comment 1 caulier.gilles 2018-11-12 11:47:59 UTC 
Problem already reported. 

Which Qt version do you use ? Go to Help/Components Info dialog for details...

Gilles Caulier
Comment 2 Maik Qualmann 2018-11-12 12:32:39 UTC 
Look at this bug 395875. I am really surprised that still Linux distributions Qt-5.11 provide unpatched, since the problem is known since June and many more programs are affected.

Maik
Comment 3 m*sh 2018-11-12 12:40:29 UTC 
I am having Qt 5.11.2
Comment 4 caulier.gilles 2018-11-12 12:51:31 UTC 
The official digiKam 5.9.0 Linux AppImage bundle is compiled with Qt 5.9 must be safe to use in place without this kind of problem...

Gilles Caulier
Comment 5 Maik Qualmann 2018-11-15 13:28:19 UTC 

*** This bug has been marked as a duplicate of bug 395875 ***
Comment 6 caulier.gilles 2020-07-25 14:47:44 UTC 
Fixed with #395875