Bug 370392 - digikam does not start on wayland
Summary: digikam does not start on wayland
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ColorManagement-Backend (show other bugs)
Version: 5.1.0
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-10 08:36 UTC by miku84
Modified: 2022-02-01 11:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.4.0

Attachments
crash report (2.89 KB, text/plain)
2016-10-10 15:12 UTC, miku84 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description miku84 2016-10-10 08:36:34 UTC 
digikam does not start on wayland

Reproducible: Always

Steps to Reproduce:
1. boot to wayland (plasma 5)
2. start digikam


Actual Results:  
digikam crashes

Expected Results:  
digikam should run
Comment 1 caulier.gilles 2016-10-10 08:55:32 UTC 
We need a GDB backtrace please...

Gilles Caulier
Comment 2 miku84 2016-10-10 15:12:12 UTC 
Created attachment 101510 [details]
crash report

crash report
Comment 3 miku84 2016-10-10 15:15:39 UTC 
Crash report attached.
From terminal "digikam" starts OK and also "digikam -qwindowtitle %c". If I create a shortcut to the desktop I get the attached crach report.
Comment 4 caulier.gilles 2016-10-10 15:46:27 UTC 
I crash in X11 API where with Wayland this must never happen of course. X11 API is used here to get screen color profile from X server if this is one set by end user.

Q : Which system did you use to run Wayland ?

Gilles Caulier
Comment 5 miku84 2016-10-10 15:47:43 UTC 
Manjaro Plasma 5.8 KF 5.26
Comment 6 Maik Qualmann 2016-11-13 09:13:50 UTC 
*** Bug 372420 has been marked as a duplicate of this bug. ***
Comment 7 Maik Qualmann 2016-11-14 19:43:21 UTC 
Git commit 31e5507db917d7d914f1e3f3c24f5d6777d61f88 by Maik Qualmann.
Committed on 14/11/2016 at 19:42.
Pushed by mqualmann into branch 'master'.

try to fix crash under wayland, native support later

M  +6    -0    libs/dimg/filters/icc/iccsettings.cpp

http://commits.kde.org/digikam/31e5507db917d7d914f1e3f3c24f5d6777d61f88
Comment 8 caulier.gilles 2016-11-28 11:34:24 UTC 
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last
bundle is available at this url:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 9 caulier.gilles 2016-12-25 14:08:36 UTC 
Any feedback with current 5.4.0 AppImage Linux bundle ?

Gilles Caulier
Comment 10 caulier.gilles 2016-12-27 11:51:05 UTC 
I just tested digiKam 5.4.0 with Gnome+Wayland under Mageia6 (Cauldron).

It do not crash. Color Management have been enabled of course.

digiKam still compiled with XCB support through KF5 framework. It do not use Wayland directly. It slow, as a gateway work in background to support XCB based application.

Using Wayland directly is another story, more complicated to handle, as Qt5+KF5 Wayland support need to be enabled. This will be for later, when this environnement will be more dispatched everywhere.

So for me the current situation work.

Gilles Caulier

Gilles Caulier
Comment 11 caulier.gilles 2016-12-27 11:53:19 UTC 
To Miku84:

I want to be sure. 

Can you run a KDE application on your system (a based one, installed with a package), and go to Help/About dialog. Copy the contents of Version tab in this thread. 

Thanks in advance

Gilles Caulier
Comment 12 caulier.gilles 2016-12-27 11:56:21 UTC 
Note : KF5 5.29 and Qt 5.6.2 is used here under Mageia6 Cauldron.

Gilles Caulier
Comment 13 miku84 2017-01-13 19:43:01 UTC 
I have tried it with digikam 5.4, KF 5.29, Plasma 5.8.4 and it crashed as before, but only from the desktop shortcut.
From terminal digikam -qwindowtitle %c" is working.
Comment 14 miku84 2017-02-24 21:12:16 UTC 
I managed digikam to work with
QT_QPA_PLATFORM=xcb digikam 
command. Plus is, it needs D-bus registration feedback.