Bug 409685 - ImageEditor can only be invoked once
Summary: ImageEditor can only be invoked once
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ImageEditor-Core (show other bugs)
Version: 5.9.0
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-10 13:27 UTC by Alain Knaff
Modified: 2020-07-25 14:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Knaff 2019-07-10 13:27:00 UTC
SUMMARY

Image editor can only be invoked once from digikam's main window

STEPS TO REPRODUCE
1. In an album, select a picture
2. Click Image Editor button
3. Image editor opens (albeit, without its menu)
4. Close image editor
5. In main window, click Image Editor button again

OBSERVED RESULT
After Step 5, an image editor window with a white background (and nothing else) appears. At the same time, the following message is printed to STDERR:

digikam.geoiface: ----
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48058, resource id: 96469350, major code: 19 (DeleteProperty), minor code: 0

... and after closing the useless image editor:
digikam.geoiface: ----



EXPECTED RESULT
Image editor should appear normally (i.e. with selected photo), even when opening it the second time.



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux 4.19.0-5-amd64, Debian 10, KDE 5.54.0-1
(available in About System)
KDE Plasma Version: 4:5.14.5.1-1
KDE Frameworks Version: 
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Comment 1 Alain Knaff 2019-07-10 13:44:34 UTC
I just noticed: the problem only occurs when closing the Image Editor window using the "cross" icon on its title bar (top-right corner). It doesn't occur when using the "Close Editor" from the Image Editor's own "Main toolbar"
Comment 2 Maik Qualmann 2019-07-10 15:20:14 UTC

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