Created attachment 185901 [details] glitch SUMMARY Taskbar visual glitch happens on laptop internal screen when 2nd monitor is unplugged. After about 10 minutes plasmashell lockups using 100% of CPU, taskbar become unresponsive. Host PC is ASUS TUF A14 2025 (2560x1600 140% DPI), external screen is Gigabyte M32U (3840x2160 105% DPI), extended to the right side. STEPS TO REPRODUCE 1. Connect external screen (Or connected before boot up) 2. Unplug external screen 3. Glitch happens 4. Wait about 10 minutes 5. Shell dead OBSERVED RESULT Visual glitch and shell dead EXPECTED RESULT No glitch SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.3-3-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen AI 7 H 350 w/ Radeon 860M Memory: 32 GiB of RAM (29.0 GiB usable)
Well that's strange. Does it ever happen with a new clean user account on the same machine with no customization except for moving the panel to the left side?
(In reply to Nate Graham from comment #1) > Well that's strange. Does it ever happen with a new clean user account on > the same machine with no customization except for moving the panel to the > left side? Yes it also happens with a new clean user. The only thing I did is move the panel to the left side, then clone the panel to external monitor.
Thanks!
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? If there are no coredumps, then this isn't actually a crash, and there are other steps we can try. Thanks.
(In reply to TraceyC from comment #4) > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > If there are no coredumps, then this isn't actually a crash, and there are > other steps we can try. > > Thanks. I think the plasmashell "crash" (more like lockup, doesn't take any input) after Taskbar glitch maybe is caused by something else, in last 2 days' reproduction the lockup didn't happen. I've coredumpctl installed and the last dump is something else earlier.
Thanks for clarifying. It does sound like two things happened. We'll keep this report focused on the taskbar glitch and plasmashell lockup. If you see another crash, please create a new report for it. Can you run `sudo perf top -g` until the system misbehaves and take a screenshot, then attach that to this report? That will give us an idea of what's causing the lockup. Thanks.
The issue is disappeared after updating to 6.5.0, good job !
That's great to hear! Thanks for letting us know.