Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53625 - [digikam] Selecting Database Configuration Type on first startup crashes application

Attached to Project: Arch Linux
Opened by Espen Fossen (espenaf) - Sunday, 09 April 2017, 17:10 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 08 March 2018, 08:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Selecting Database Configuration Type on first startup crashes application

Additional info:
* package version(s)
5.5.0
* config and/or log files etc.
KDE 5.9.4 with Wayland
Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-1-macbook x86_64

Steps to reproduce:

* Start digikam for the first time
* Click Next twice, and then get to the Database Configuration screen
* Try to click the Type to change Database type

-- 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

First reported to KDE project, they think it is a wayland bug.
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 08 March 2018, 08:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems to work fine in Qt 5.10
Comment by Antonio Rojas (arojas) - Sunday, 09 April 2017, 17:34 GMT
Not a packaging issue, please report upstream
edit: I missed the last line, please post the upstream bug link
Comment by Espen Fossen (espenaf) - Sunday, 09 April 2017, 18:07 GMT Comment by Antonio Rojas (arojas) - Sunday, 09 April 2017, 19:15 GMT
The digikam developer apparently doesn't care about bugs that can't be reproduced on his standard setup. This is an upstream issue, probably in Qt rather then digikam, but it's hard to know without debug symbols. Note that plasma Wayland is still considered experimental, so issues are to be expected.

Loading...