https://bugs.kde.org/show_bug.cgi?id=458936
Bug ID: 458936
Summary: Stability issues related to notifications (or images
in them?) on debian testing/unstable
Product: plasmashell
Version: 5.25.4
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Notifications
Assignee: plasma-b...@kde.org
Reporter: s...@hjkos.com
CC: k...@privat.broulik.de
Target Milestone: 1.0
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
possibly related to https://bugs.kde.org/show_bug.cgi?id=457847
If you leave system working while notifications are happening there's a chance
that plasmashell will lock up, prolonging this will cause whole system to
mostly lock up. It seems that some (rogue? broken icon?) notification may cause
plasmashell to lockup entirely and take some other processes (i.e. ones
generating notifications) talking to it a hostage.
STEPS TO REPRODUCE
1. Have something generating notifications preferably with custom icons (i.e.
microblogging pleroma-based websites, IM like matrix or slack).
2. Make sure you actually have plasmashell notifications appearing on screen
(i.e. there's notification widget and DND isn't turned on)
3. Go on about your day
OBSERVED RESULT
Eventually, plasmashell will lockup and become unresponsive (especially
noticeable if you have seconds in time widget), there will be an artifact like
a black rectange or hall-of-mirrors effect or similar depending whether
composition is on or off. Killing plasmashell helps but has high chance of
crashing whatever was generating notifications (i.e. chromium). If this state
persists, system will most likely lock up (cpu usage spike? kwin locking up?)
stop responding to (newly plugged?) USB keyboards/mice, trying to switch to TTY
yields black screen with non-blinking cursor. If system goes to sleep in this
state it will be still broken when woken up but lock screen seems to work fine.
EXPECTED RESULT
Your day is just about the same as before
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: kernel 5.18.0-4-amd64
(available in About System)
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.4
ADDITIONAL INFORMATION
Using X11 (kwin-x11).
I have two devices where this happens - a dell laptop with intel graphics and
amd desktop, and this happens on both of them, so I don't think it's a MESA
issues, not to mention this happens with and without compositing. However,
turning DND mode on helped tremendously - the notifications that go through are
"critical" ones and on my system those are from psi-notify daemon, which
doesn't use icons and system is much more stable, even with sleeps.
My guess is that notification happens, most likely coming from microblogging or
IM, which tends to use user avatar as an icon, icon fails to render properly
and plasma doesn't know how to handle it and locks up, while it's locked up it
cannot respond to other requests to notifications and/or possibly leaks memory.
Debugging it in this state is near impossible, but I managed to ssh into locked
system once and had to kill/restart sddm to make it work again, but usually the
only solution is a hard-reset with a hardware button. No crash dumps for
plasmashell in /var/crash only chromium crashes there, but next time it happens
i might try to get some + get some logs. Nothing out of ordinary in
.xsession-errors either.
--
You are receiving this mail because:
You are watching all bug changes.
