Bug 437643

Summary: Crashing when closing Firefox
Product: [Applications] kdeconnect Reporter: José Ángel Martínez <jangel.martinez>
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED UPSTREAM    
Severity: crash CC: emil.sodergren, sitter
Priority: NOR Keywords: drkonqi
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description José Ángel Martínez 2021-05-25 00:12:28 UTC
Application: kdeconnectd (21.04.1)

Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.8.0-53-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.5
Distribution: KDE neon User Edition 5.21

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

I just close Firefox and several kde apps crashed suddenly at the same time

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Demonio de KDE Connect (kdeconnectd), signal: Aborted

[New LWP 10568]
[New LWP 10587]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fe4a5259aff in __GI___poll (fds=0x7ffe6d327868, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7fe4a172cd40 (LWP 10495))]

Thread 3 (Thread 0x7fe49e9b1700 (LWP 10587)):
#0  0x00007fe4a5259aff in __GI___poll (fds=0x7fe490004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fe4a3d4e36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fe4a57cb1eb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fe4a55e5a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fe4a55e6bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fe4a476f609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#8  0x00007fe4a5266293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fe49fbc2700 (LWP 10568)):
#0  0x00007fe4a5259aff in __GI___poll (fds=0x7fe498005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fe4a3d4e36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fe4a57cb1eb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fe4a55e5a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fe4a614ef4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fe4a55e6bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fe4a476f609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007fe4a5266293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fe4a172cd40 (LWP 10495)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x00007fe4a5169859 in __GI_abort () at abort.c:79
#6  0x00007fe4a55abbf7 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fe4a3a91d65 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x00007fe4a3aa316c in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#9  0x00007fe4a5803730 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fe4a5807773 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fe4a5807f13 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fe4a6341dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fe4a634abb8 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fe4a57cc6da in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fe4a5827be5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fe4a3d4e17d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fe4a3d4e400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fe4a57cb1eb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fe4a57d3394 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000055ba9a77e016 in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:174
[Inferior 1 (process 10495) detached]

Possible duplicates by query: bug 429344, bug 427384, bug 424911, bug 423222, bug 423132.

Reported using DrKonqi
Comment 1 Harald Sitter 2021-05-27 07:06:44 UTC
This means that the compositor crashed. Due to a Qt issue, when this happens, the app using it will crash too. KDE developers submitted a fix, but sadly it was not merged. See https://codereview.qt-project.org/c/qt/qtwayland/+/308984.

Until we get better handling of this in Qt, the best we can do is debug why the compositor crashed in the first place. So can you please get a backtrace of the crash in kwin_wayland and then file a new bug report with it on kwin | wayland-generic? Thanks!

You may be able to use the `coredumpctl` utility to retrieve the backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 2 cwo 2024-08-03 23:49:59 UTC
*** Bug 436107 has been marked as a duplicate of this bug. ***