Bug 464797

Summary: Plasma crashes and reloads when clicking on the panel
Product: [Plasma] plasmashell Reporter: Tommaso Fonda <fondatommaso2>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: niccolo.venerandi, nicolas.fella
Priority: NOR    
Version: 5.26.5   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: journalctl log

Description Tommaso Fonda 2023-01-25 13:23:59 UTC
Created attachment 155631 [details]
journalctl log

SUMMARY
In the past few days I've experienced quite a bit of Plasma crashes (the panel disappears, the desktop wallpaper becomes black, and then Plasma starts up again and the panel and the wallpaper come back).

The windows I have open are unaffected (they stay open).

This happens randomly, after I interact with the panel for any reason: I just had one of these crashes while starting Firefox by clicking on its icon in the panel. Yesterday I faced the same crash while clicking on the battery applet, if I recall correctly.

Attached is (what I believe is) the relevant part of journalctl.
Thanks.

STEPS TO REPRODUCE
1. Click on a program's icon in the process manager (icons only version) located on the panel

OBSERVED RESULT
Observe that the program starts or its window is focused if it is already running, but the panel sometimes crashes and the desktop wallpaper becomes black.

EXPECTED RESULT
The program starts or its window is focused if it is already running, without having the panel and the wallpaper to crash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Comment 1 Tommaso Fonda 2023-01-25 13:27:21 UTC
I am not 100% sure it has happened when clicking on applets too, although I think it has.
It definitely happens "often" when clicking on program icons in the task manager (today, 5 or 6 times in a few hours of usage).
Comment 2 Nicolas Fella 2023-01-25 13:55:39 UTC

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