Bug 442945 - KdeConnect and other applications error and crash when plasma shell crashes
Summary: KdeConnect and other applications error and crash when plasma shell crashes
Status: RESOLVED LATER
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-09-25 16:49 UTC by Andrew DeMarsh
Modified: 2022-01-01 06:02 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.26 KB, text/plain)
2021-11-14 13:17 UTC, poultrymanager
Details
New crash information added by DrKonqi (3.37 KB, text/plain)
2022-01-01 06:02 UTC, suntianchen2001
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew DeMarsh 2021-09-25 16:49:58 UTC
Application: kdeconnectd (21.08.0)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.10.0-8-amd64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.5
Distribution: Debian GNU/Linux bookworm/sid

-- Information about the crash:
- What I was doing when the application crashed:
adjusting the firefox webrender mode to enabled in the default firefox snap package.
- Unusual behavior I noticed:
on loading youtube to see the effect this took the desktop crashed.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007f4676662536 in __GI_abort () at abort.c:79
#6  0x00007f4676aa0bf1 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f4674b87f99 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x00007f4674b96dfa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#9  0x00007f4676cf35e0 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f4676cf69df in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f4676cf71db in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f467780615f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f4676cbcfca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f4676d150d5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f467516785b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f4675167b08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f4675167bbf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f4676d1451f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f4676cbb98b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f4676cc3c00 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x0000557a9f9fe9c1 in ?? ()
#22 0x00007f4676663e4a in __libc_start_main (main=0x557a9f9fe5b0, argc=1, argv=0x7fff1bf98588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff1bf98578) at ../csu/libc-start.c:314
#23 0x0000557a9f9fec5a in _start ()
[Inferior 1 (process 2607) detached]

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

Reported using DrKonqi
Comment 1 poultrymanager 2021-11-14 13:17:11 UTC
Created attachment 143539 [details]
New crash information added by DrKonqi

kdeconnectd (20.12.3) using Qt 5.15.2

- What I was doing when the application crashed:

The screen went to sleep, and when I came back a message appeared saying that the unlocker crashed

- Unusual behavior I noticed:

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007f8836013864 in __GI_abort () at abort.c:79
#6  0x00007f8836484c77 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:893
[...]
#9  0x00007f88329a5f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
Comment 2 Petr Kadlec 2021-12-03 13:53:32 UTC
This is probably the same thing which happened to me: When working in Jetbrains Idea, the screen went suddenly black, all applications restarted and a bunch of error reporters appeared, reporting various crashed apps. Among them, even the crash reporter:

Application: The KDE Crash Handler (drkonqi), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140488933714304) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140488933714304) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=140488933714304, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007fc6244d4476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fc6244ba7b7 in __GI_abort () at abort.c:79
#9  0x00007fc624979ba3 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#10 QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:893
#11 0x00007fc62341ce45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007fc62342d06a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#13 0x00007fc624bd9a88 in doActivate<false> (sender=0x55fdf681e660, signal_index=3, argv=0x7ffe4b413f30) at kernel/qobject.cpp:3898
#14 0x00007fc624bd2d67 in QMetaObject::activate (sender=sender@entry=0x55fdf681e660, m=m@entry=0x7fc624e3f180 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe4b413f30) at kernel/qobject.cpp:3946
#15 0x00007fc624bdcf63 in QSocketNotifier::activated (this=this@entry=0x55fdf681e660, _t1=..., _t2=<optimized out>, _t3=...) at .moc/moc_qsocketnotifier.cpp:178
#16 0x00007fc624bdd793 in QSocketNotifier::event (this=0x55fdf681e660, e=0x7ffe4b414050) at kernel/qsocketnotifier.cpp:302
#17 0x00007fc6258336b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007fc624ba216a in QCoreApplication::notifyInternal2 (receiver=0x55fdf681e660, event=0x7ffe4b414050) at kernel/qcoreapplication.cpp:1063
#19 0x00007fc624bfc155 in socketNotifierSourceDispatch (source=0x55fdf681eac0) at kernel/qeventdispatcher_glib.cpp:107
#20 0x00007fc6235548bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fc6235a7f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fc623552003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fc624bfb548 in QEventDispatcherGlib::processEvents (this=0x55fdf681e5c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x00007fc624ba0a9b in QEventLoop::exec (this=this@entry=0x7ffe4b414260, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x00007fc624ba9024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x000055fdf5207b5d in main (argc=<optimized out>, argv=<optimized out>) at ./src/main.cpp:219
[Inferior 1 (process 20816) detached]
Comment 3 Nicolas Fella 2021-12-14 00:15:54 UTC
What happens is that when the Wayland compositor (KWin) crashes then all GUI applications crash too. This is something that will get fixed eventually on a toolkit-level.
Comment 4 suntianchen2001 2022-01-01 06:02:22 UTC
Created attachment 145002 [details]
New crash information added by DrKonqi

kdeconnectd (21.12.0) using Qt 5.15.2

- What I was doing when the application crashed:
nothing but waking the desktop from sleep mode

- Unusual behavior I noticed:
nothing but waking the desktop from sleep mode


- Custom settings of the application:
nothing but waking the desktop from sleep mode

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139961234492992) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139961234492992) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139961234492992, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007f4b47a29476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f4b47a0f7b7 in __GI_abort () at abort.c:79