[kwin] [Bug 436022] kwin_wayland crashes when mounting an external USD harddrive

Pawel bugzilla_noreply at kde.org
Mon Apr 26 20:16:13 BST 2021


https://bugs.kde.org/show_bug.cgi?id=436022

--- Comment #6 from Pawel <bednarczyk.pawel at outlook.com> ---
I am not sure if the below helps. I will try with valgrind but I am not sure
which app to attach it to

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/dolphin'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7fce16447d80 (LWP 1965))]
(gdb) bt
#0  __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007fce1cccbfcc in KCrash::defaultCrashHandler(int) () from
/lib/x86_64-linux-gnu/libKF5Crash.so.5
#2  <signal handler called>
#3  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#4  0x00007fce1ac10859 in __GI_abort () at abort.c:79
#5  0x00007fce1b050bf7 in qt_message_fatal (context=..., message=<synthetic
pointer>...) at global/qlogging.cpp:1914
#6  QMessageLogger::fatal (this=this at entry=0x7fff8e1bbd80,
msg=msg at entry=0x7fce18c010b8 "The Wayland connection broke. Did the Wayland
compositor die?") at global/qlogging.cpp:893
#7  0x00007fce18b44d65 in QtWaylandClient::QWaylandDisplay::checkError
(this=<optimized out>) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90
#8  QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at
qwaylanddisplay.cpp:204
#9  0x00007fce18b5616c in QtWaylandClient::QWaylandDisplay::flushRequests
(this=0x55e2613c4cb0) at qwaylanddisplay.cpp:222
#10 0x00007fce1b2a8730 in doActivate<false> (sender=0x55e2614306d0,
signal_index=3, argv=0x7fff8e1bbe90) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#11 0x00007fce1b2a1ac7 in QMetaObject::activate
(sender=sender at entry=0x55e2614306d0, m=m at entry=0x7fce1b50b1c0
<QAbstractEventDispatcher::staticMetaObject>,
local_signal_index=local_signal_index at entry=0, 
    argv=argv at entry=0x0) at kernel/qobject.cpp:3946
#12 0x00007fce1b26e264 in QAbstractEventDispatcher::aboutToBlock
(this=this at entry=0x55e2614306d0) at .moc/moc_qabstracteventdispatcher.cpp:143
#13 0x00007fce1b2cbfb6 in QEventDispatcherGlib::processEvents
(this=0x55e2614306d0, flags=...) at kernel/qeventdispatcher_glib.cpp:410
#14 0x00007fce1b2701eb in QEventLoop::exec (this=this at entry=0x7fff8e1bbfb0,
flags=..., flags at entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#15 0x00007fce1b278394 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#16 0x000055e260ca4c82 in main (argc=<optimized out>, argv=<optimized out>) at
./src/main.cpp:222
(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list