Application: akonadiserver (5.22.2 (22.12.2)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: Wayland compositor crashed when changing display scale of primary monitor from 300% to 200%. All active applications disappeared. May have been caused by changing which monitor was primary, but I don't know whether I did that before or immediately after it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x000056426eb40323 in ?? () #5 0x00007f06d5707d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x00007f06d56dc1bd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x00007f06d56df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x00007f06d5734413 in ?? () from /lib64/libQt5Core.so.5 #9 0x00007f06d391ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #10 0x00007f06d391be48 in ?? () from /lib64/libglib-2.0.so.0 #11 0x00007f06d391bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #12 0x00007f06d5733c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #13 0x00007f06d56dac5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #14 0x00007f06d56e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #15 0x000056426eb367a1 in ?? () #16 0x00007f06d4e2caf0 in __libc_start_call_main () from /lib64/libc.so.6 #17 0x00007f06d4e2cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #18 0x000056426eb39265 in ?? () [Inferior 1 (process 19809) detached] Reported using DrKonqi
Unfortunately this bug report only has a crash of the akonadi server. Can you attach a backtrace for kwin_wayland?
(In reply to Nate Graham from comment #1) > Unfortunately this bug report only has a crash of the akonadi server. Can > you attach a backtrace for kwin_wayland? Glad to. Do you have the specific commands to run? I don't know how to. If this report looks like it's missing something (such as the desired backtrace) that might be because I had to force-kill drkonqi after about an hour of it endlessly "submitting report".
Yep, see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
(In reply to Nate Graham from comment #3) > Yep, see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. That documentation is vaguely confusing, and anyway, I don't have the time currently to read through it. Can you just tell me the exact commands to run? I'm happy to provide the output, if the logs still exist. I'm using the same system and OS, so ideally they should.
The section I linked you to tells you exactly what you need to do. I can't give you the commends myself because they will be different depending on the output of `coredumpctl --reverse`.
Created attachment 157341 [details] Screenshot of output of sudo + initial command specified by documentation. (In reply to Nate Graham from comment #5) > The section I linked you to tells you exactly what you need to do. I can't > give you the commends myself because they will be different depending on the > output of `coredumpctl --reverse`. My last log is from 2023-03-03T13:54:10+0000 rather than 2023-02-25T19:22Z, which appears to be when bugzilla reports that this reported. Reckon that the log has been lost?
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!
Still waiting for a backtrace of the crashing kwin_wayland process. We can't move forward without it.