Bug 476313

Summary: On X11, plasmashell crash in dual-monitor setup after turning monitors back on
Product: [Plasma] plasmashell Reporter: csxeba
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kde, nate
Priority: NOR Keywords: drkonqi, multiscreen
Version First Reported In: 5.27.9   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description csxeba 2023-10-30 04:18:58 UTC 
Application: plasmashell (5.27.9)

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.5.9-arch2-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
Laptop + external screen setup with HDMI connection. No sleep and no hibernation invonved, only screens turning off after preset idle time.
When I 'wake' the computer/monitors up (note again that only the monitors are turned off), plasmashell is already crashed. If I restart plasmashell from terminal and send it to the background, closing the terminal usually crashes plasma again. If I use screen/tmux to restart plasmashell in the foreground and detach from the terminal multiplexer, plasmashell runs correctly and usually the crashes stop, until the next system restart.

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  0x00005561e52f0c1d in  ()
#5  0x00007f64194d1097 in  () at /usr/lib/libQt5Core.so.5
#6  0x00007f64194d2bcf in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#7  0x00007f64194c3b4e in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#8  0x00007f641a1788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#9  0x00007f641949c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#10 0x00007f64194ea7cb in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5
#11 0x00007f64194eae02 in  () at /usr/lib/libQt5Core.so.5
#12 0x00007f6418025f69 in  () at /usr/lib/libglib-2.0.so.0
#13 0x00007f6418084327 in  () at /usr/lib/libglib-2.0.so.0
#14 0x00007f6418024162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#15 0x00007f64194eaf7c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#16 0x00007f641949ae74 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#17 0x00007f641949c313 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#18 0x00005561e52c616c in  ()
#19 0x00007f6418c45cd0 in  () at /usr/lib/libc.so.6
#20 0x00007f6418c45d8a in __libc_start_main () at /usr/lib/libc.so.6
#21 0x00005561e52c6515 in  ()
[Inferior 1 (process 13602) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2023-10-30 19:22:34 UTC 
Cannot reproduce on Plasma 6 Wayland, no KDE code is implicated in what I can see from the backtrace, and the backtrace has no debug symbols for anything that would help. :(

If this crash is reproducible, could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Also, can you try this on the Wayland session too, to see if it happens there or if it's X11-only?

Thanks!
Comment 2 Bug Janitor Service 2023-11-14 03:45:49 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 2023-11-29 03:45:48 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!