Bug 378591

Summary:	Selecting Database Configuration Type on first startup crashed application
Product:	[Applications] digikam	Reporter:	Espen Fossen <espenaf>
Component:	Setup-Database	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	crash	CC:	arojas, caulier.gilles
Priority:	NOR	Keywords:	drkonqi
Version:	5.5.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:	7.6.0
Sentry Crash Report:

Description Espen Fossen 2017-04-09 16:39:17 UTC

Application: digikam (5.5.0)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-1-macbook x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

First start of digiKam and on the Database Configuration screen I try to click the Type dialog, where SQlite is select, and the application just crashes. Last log was:

digikam.general: Testing  "mysql_install_db" ...
digikam.general: Found  "mysql_install_db"
digikam.general: Testing  "mysqld" ...
digikam.general: Found  "mysqld"
sock_file=/run/user/1000/kdeinit5__1
[1]   Segmentation fault      (core dumped) digikam

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f044cefddc0 (LWP 30898))]

Thread 2 (Thread 0x7f040abd4700 (LWP 30899)):
#0  0x00007f044839967d in poll () at /usr/lib/libc.so.6
#1  0x00007f043c65b7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x00007f043c65b8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#3  0x00007f04492d706b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#4  0x00007f044928089a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#5  0x00007f04490a2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x00007f0443221125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x00007f04490a76d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x00007f0442ff42e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x00007f04483a354f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f044cefddc0 (LWP 30898)):
[KCrash Handler]
#6  0x00007f040fd54df7 in  () at /usr/lib/libwayland-client.so.0
#7  0x00007f040fd553c8 in  () at /usr/lib/libwayland-client.so.0
#8  0x00007f040fd532cd in wl_proxy_marshal () at /usr/lib/libwayland-client.so.0
#9  0x00007f0449f97f06 in QWidgetPrivate::raise_sys() () at /usr/lib/libQt5Widgets.so.5
#10 0x00007f0449fa1c38 in QWidget::raise() () at /usr/lib/libQt5Widgets.so.5
#11 0x00007f0449fa8a80 in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5
#12 0x00007f0449fab6d5 in QWidget::setVisible(bool) () at /usr/lib/libQt5Widgets.so.5
#13 0x00007f044a06aef8 in QComboBox::showPopup() () at /usr/lib/libQt5Widgets.so.5
#14 0x00007f044a06b555 in  () at /usr/lib/libQt5Widgets.so.5
#15 0x00007f0449fac64f in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#16 0x00007f044a067676 in QComboBox::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#17 0x00007f0449f6434c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#18 0x00007f0449f6c8c5 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#19 0x00007f0449282440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#20 0x00007f0449f6b0cd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /usr/lib/libQt5Widgets.so.5
#21 0x00007f0449fc63e6 in  () at /usr/lib/libQt5Widgets.so.5
#22 0x00007f0449fc8e03 in  () at /usr/lib/libQt5Widgets.so.5
#23 0x00007f0449f6434c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#24 0x00007f0449f6bb61 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#25 0x00007f0449282440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#26 0x00007f04497cfd53 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5
#27 0x00007f04497d18c5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
#28 0x00007f04497ad44b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#29 0x00007f040ffe7d00 in  () at /usr/lib/libQt5WaylandClient.so.5
#30 0x00007f043c65b5a7 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#31 0x00007f043c65b810 in  () at /usr/lib/libglib-2.0.so.0
#32 0x00007f043c65b8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#33 0x00007f04492d704f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#34 0x00007f044928089a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#35 0x00007f044a152917 in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5
#36 0x0000000000405510 in  ()
#37 0x00007f04482d7511 in __libc_start_main () at /usr/lib/libc.so.6
#38 0x0000000000406a2a in _start ()

Reported using DrKonqi

Comment 1 caulier.gilles 2017-04-09 16:47:40 UTC

Look like it crash in wayland plugin from Qt5 :

Thread 1 (Thread 0x7f044cefddc0 (LWP 30898)):
[KCrash Handler]
#6  0x00007f040fd54df7 in  () at /usr/lib/libwayland-client.so.0

There is nothing wrong from digiKam side here. All work fine here with a fresh  X11 installation of digiKam in these conditions.

Sound like an Arch packaging problem. Please report it to your distro team...

Gilles Caulier

Comment 2 Antonio Rojas 2017-04-09 19:05:46 UTC

This is crashing on Wayland, the fact that it works on X11 is completely irrelevant. If digikam doesn't support Wayland, just close it as wontfix, and please announce it on the release notes so that distros are aware of it. If it does support Wayland, then this shouldn't be dismissed just because it works on X11

Comment 3 caulier.gilles 2017-04-09 20:40:42 UTC

digiKam as nothing to do with Wayland. It don't know and don't need to know what's screen manager run in background, especially when you setup database.

In fact we use Qt5 as frontend. This mask the screen manager. This permit to run under OSX or Windows without any problem.

I suspect a Qt5 compilation problem from the distro. that all. In the backtrace, only system internal library can be visible. There is nothing from digiKam side.

Gilles Caulier