Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Got this error when I wake up PC from sleep today. The crash can be reproduced sometimes. -- Backtrace (Reduced): #7 0x00007fe764e3ebbc in KCompressionDevice::readData(char*, long long) () from /lib/x86_64-linux-gnu/libKF5Archive.so.5 #8 0x00007fe7655e26ef in QIODevicePrivate::read(char*, long long, bool) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fe7655e2f24 in QIODevice::readAll() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #13 0x00007fe767aa6c09 in Plasma::Svg::pixmap(QString const&) () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 [...] #16 0x00007fe767469a92 in QQuickWindowPrivate::polishItems() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 Reported using DrKonqi
Created attachment 162399 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Thread 1 (Thread 0x7fe760a2a540 (LWP 6278)): [KCrash Handler] #5 0x00007fe7653718ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007fe764e3fab2 in ?? () from /lib/x86_64-linux-gnu/libKF5Archive.so.5 #7 0x00007fe764e3ebbc in KCompressionDevice::readData(char*, long long) () from /lib/x86_64-linux-gnu/libKF5Archive.so.5 #8 0x00007fe7655e26ef in QIODevicePrivate::read(char*, long long, bool) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fe7655e2f24 in QIODevice::readAll() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007fe767aa07d0 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #11 0x00007fe767aa29f8 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #12 0x00007fe767aa66d8 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #13 0x00007fe767aa6c09 in Plasma::Svg::pixmap(QString const&) () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #14 0x00007fe74d168824 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #15 0x00007fe74d16755f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #16 0x00007fe767469a92 in QQuickWindowPrivate::polishItems() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x00007fe76740bbcd in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x00007fe767476e20 in QQuickWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x00007fe766562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x00007fe7656b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00007fe765b2c4b3 in QPlatformWindow::windowEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x00007fe76656a1f9 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x00007fe7656b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007fe765708c31 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007fe7657094fc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007fe7640dc7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007fe7640dca38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007fe7640dcacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007fe765709836 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007fe7656b017b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x00007fe7656b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x0000559318c96dc3 in ?? () #33 0x00007fe7652461ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #34 0x00007fe765246285 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #35 0x0000559318c96ee1 in ?? ()
Thank you for the bug report! Unfortunately 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 for karchive and plasma, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. Thanks again!
Hello Nate, I will be happy to help. I have DEBUGINFOD_URLS="https://debuginfod.debian.net" configured, but not sure how to install dbg symbols for karchive and plasma in Debian. Anyway, I was able to find 3 crashes of plasma in my logs: Attaching result of export DEBUGINFOD_URLS="https://debuginfod.debian.net" && sudo coredumpctl debug [pid] for all three.
Created attachment 162454 [details] crash1
Created attachment 162455 [details] crash2
Created attachment 162456 [details] crash3
Thanks, however we're still missing debug symbols for both KArchive and Plasma. As for how to get debug symbols on Debian, hopefully something at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian will help; if not the debuginfod thing, then maybe you can install the -dbg packages manually
Thank you. I've read that page before. It doesn't say, unfortunately, what is the name of the package which contains symbols for these packages. I have line: export DEBUGINFOD_URLS="https://debuginfod.debian.net" already in /etc/profile (and it was there for quite some time). I searched for any package with plasma and dbg words, or karchive and dbg, or even qt and dbg, no result. I don't know where to find debug symbols for them, sorry.
You'll need to ask for help in a Debian-specific forum. Or just use your package manager to search for (for example) `kcodecs` and the the debug packages there. It's a shame Debian makes this so hard.
Please, Mr. Graham, don't talk bullshit. What is shameful here is a user who wants to use Debian without reading a line of manual and then asks for help from someone, like you, Mr. Graham, who doesn't know Debian at all
And update the Debian section of the page "Guidelines and HOWTOs/Debugging/How to create useful crash reports", is obsolete.
That's right, I don't know Debian, so I rely on our wiki documentation being correct. If it's not, someone who knows the situation better than me ought to update it. Do you know how to do this? If so, I'd very much appreciate it if you could update the wiki to be accurate. Thanks!
(In reply to Nate Graham from comment #10) > You'll need to ask for help in a Debian-specific forum. Or just use your > package manager to search for (for example) `kcodecs` and the the debug > packages there. > > It's a shame Debian makes this so hard. Hello Nate, Thanks for your reply. I revisited relevant documentation pages, and now I am able to install debugging symbols from additional Debian repository. It was my mistake not to prepare in advance, my apologies. Now, I should be able to get all process thread calls resolved, should the next crash occur. I can't analyse previous crashes, because systemd has deleted coredumps already. Awaiting the next crash, I will keep you informed. Thank you!
With pleasure! I'll sign up now and see what I can do. regards
(In reply to d7ghrrkcz from comment #14) > Thanks for your reply. I revisited relevant documentation pages, and now I > am able to install debugging symbols from additional Debian repository. It > was my mistake not to prepare in advance, my apologies. Now, I should be > able to get all process thread calls resolved, should the next crash occur. > I can't analyse previous crashes, because systemd has deleted coredumps > already. Awaiting the next crash, I will keep you informed. Thank you! With the debug packages installed, you can use `coredumpctl` to retrieve the existing crash as per the wiki page I mentioned earlier, and then it will have debug symbols in it. So no need to wait for a new crash!
(In reply to Nate Graham from comment #16) > With the debug packages installed, you can use `coredumpctl` to retrieve the > existing crash as per the wiki page I mentioned earlier, and then it will > have debug symbols in it. So no need to wait for a new crash! That's where I went already, crash logs are no longer there, they are being deleted by systemd. $ sudo coredumpctl list --no-pager | grep plasmashell Wed 2023-10-18 07:34:12 BST 6278 1000 1000 SIGSEGV missing /usr/bin/plasmashell - Wed 2023-10-18 07:34:18 BST 2985075 1000 1000 SIGBUS missing /usr/bin/plasmashell - Wed 2023-10-18 07:34:20 BST 2985270 1000 1000 SIGBUS missing /usr/bin/plasmashell - They have "missing" status. I will have to wait for new ones.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!