Application: plasmashell (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.6-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: i had been using a fat32 micro sd card in a usb stick to put some games on it and everytime i plugged in the stick plasmashell would crash once every 2 or 3 times i did it The crash can be reproduced sometimes. -- Backtrace (Reduced): Reported using DrKonqi
Created attachment 173081 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7b7f976a9a00 (LWP 21577))] (gdb) backtrace #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007b7f9dca5463 in __pthread_kill_internal (threadid=<optimized out>, signo=11) at pthread_kill.c:78 #2 0x00007b7f9dc4c120 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x00007b7fa0268711 in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash/kcrash-6.5.0/src/kcrash.cpp:606 #4 0x00007b7f9dc4c1d0 in <signal handler called> () at /usr/lib/libc.so.6 #5 0x00007b7f9ea813d1 in QQmlContextData::contextObject (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:128 #6 QQmlContextData::ContextGuard::objectDestroyedImpl (impl=0x56f83f1b9cf8) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:455 #7 0x00007b7f9ea8f2d2 in QQmlData::destroyed (this=0x56f843238c60, object=0x56f843238c40) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1415 #8 0x00007b7f9d791ffe in QObject::~QObject (this=0x56f843238c40, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1078 #9 0x00007b7f9f1d88f3 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem (this=0x56f843238c40, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:24 #10 QQuickLoader::~QQuickLoader (this=0x56f843238c40, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickloader.cpp:281 #11 QQmlPrivate::QQmlElement<QQuickLoader>::~QQmlElement (this=0x56f843238c40, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 #12 QQmlPrivate::QQmlElement<QQuickLoader>::~QQmlElement (this=0x56f843238c40, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 is this what you need?
Yes, thank you! No more "??" which indicates that symbols are missing.
Can't repro either, but the Qml related symbols makes me wonder if this is related to the notification somehow. Do you have desktop widgets that have USB information? Or widgets downloaded from the widget store?
(In reply to Akseli Lahtinen from comment #5) > Can't repro either, but the Qml related symbols makes me wonder if this is > related to the notification somehow. > > Do you have desktop widgets that have USB information? Or widgets downloaded > from the widget store? nope no third party widgets or any widgets on the desktop, i cant reproduce it either anymore :/
Lets hope it is fixed then! I will set this as NEEDSINFO WAITINGFORINFO so that this bug report will close itself automatically in 30 days. If you encounter it again, even after the bugreport is closed, feel free to reopen it and tell us what happened! Thanks for your report!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
*** Bug 493620 has been marked as a duplicate of this bug. ***