Bug 488769

Summary: Plasma crashed after the system woke up
Product: [Plasma] plasmashell Reporter: X <maverickxhunter>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kde, kdedev, nate
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.27.11   
Target Milestone: 1.0   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description X 2024-06-20 04:12:10 UTC 
Application: plasmashell (5.27.11)
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.30-gentoo x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
As the title says, got no clue as to why it crashed I got 3 monitors and at first when I tried to wake up the system, it seemed to have hanged up, proceeded to check if the monitors were on standby by turning it off then on left the computer for a few minutes and the system went back to sleep and I attempted to wake it up again with success but system was kinda slow and then the crash notice came.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x0000555d3c280ea4 in ??? ()
#5  0x0000555d3c29e49b in ??? ()
#6  0x00007effbe8a563d in ??? () at /usr/lib64/libQt5Core.so.5
#7  0x00007effbe8a9846 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#8  0x00007effbe89d543 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#9  0x00007effbf502cc2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#10 0x00007effbe872b70 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#11 0x00007effbe8c30f9 in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#12 0x00007effbe8c3a2c in ??? () at /usr/lib64/libQt5Core.so.5
#13 0x00007effbd4c8472 in ??? () at /usr/lib64/libglib-2.0.so.0
#14 0x00007effbd4cb4f7 in ??? () at /usr/lib64/libglib-2.0.so.0
#15 0x00007effbd4cbab8 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#16 0x00007effbe8c3d82 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#17 0x00007effbe87160b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#18 0x00007effbe879841 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#19 0x0000555d3c26f522 in ??? ()
#20 0x00007effbe048310 in ??? () at /usr/lib64/libc.so.6
#21 0x00007effbe0483c9 in __libc_start_main () at /usr/lib64/libc.so.6
#22 0x0000555d3c26f765 in ??? ()
[Inferior 1 (process 7075) detached]

Reported using DrKonqi
Comment 1 TraceyC 2024-06-20 21:15:39 UTC 
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:

#6  0x00007effbe8a563d in ??? () at /usr/lib64/libQt5Core.so.5
#12 0x00007effbe8c3a2c in ??? () at /usr/lib64/libQt5Core.so.5
#13 0x00007effbd4c8472 in ??? () at /usr/lib64/libglib-2.0.so.0
#14 0x00007effbd4cb4f7 in ??? () at /usr/lib64/libglib-2.0.so.0
#20 0x00007effbe048310 in ??? () at /usr/lib64/libc.so.6

There had been crashes reported similar to this and a fix was merged to Qt6. Could we ask you to update your Plasma install to 6.1?

Could you also please install debug symbols? That will allow future backtraces to be more complete. If the crash happens again, please 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!
Comment 2 Bug Janitor Service 2024-07-05 03:47:29 UTC 
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!
Comment 3 Bug Janitor Service 2024-07-20 03:46:35 UTC 
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!