Bug 453436

Summary: switching inputs on monitor causes plasmashell to crash.
Product: [Plasma] plasmashell Reporter: antonio <rustytone>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs>
Severity: normal CC: nate
Priority: NOR    
Version: 5.24.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: crash log backtrace - inputs for nate

Description antonio 2022-05-05 19:07:27 UTC

Sorry if this is a repost, i have a crash when on newest kde at time on arch, where i switch inputs in my monitor inbuilt menu from displayport (pc) to hdmi 1 (my television equipment)

i have a lg 27inch 4k screen, amd 6600xt gpu. virgin media tv 360 box is the hdmi.

it makes the bottom panel disappear when i go back to use computer after watching the television.

1. switch on computer, use it as normal, nothing wrong.
2. switch input whilst computer is still powered on, to hdmi - for tv box.
3. switch back to displayport and the panel is missing from kde desktop, bug filing pop ups. (says there is not enough info to report it automatically)


after switching inputs on monitor it crashes and disappears the panel.


panel still being present and being able to use the computer as intended. 

Windows:  wut?
macOS: nah.
Linux/KDE Plasma: 5.17.5-arch 1 (was it asking for kernel?) arch rolling release.
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

Comment 1 Nate Graham 2022-05-05 22:14:01 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!
Comment 2 antonio 2022-05-06 09:51:19 UTC
Created attachment 148602 [details]
crash log backtrace - inputs for nate

sorry for not providing it initially, hope this comes in handy, I can recreate the bug if you need another log, let me know, more than happy to help.
Comment 3 Nate Graham 2022-05-09 15:32:58 UTC

*** This bug has been marked as a duplicate of bug 451267 ***