Bug 418205

Summary:	Notifications can freeze system and cause graphical glitches
Product:	[Plasma] plasmashell	Reporter:	Terry D. Boldt <fastsnip-bcard>
Component:	Notifications	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, plasma-bugs
Priority:	VHI
Version:	master
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=398117
Latest Commit:		Version Fixed In:

Description Terry D. Boldt 2020-02-25 22:59:18 UTC

SUMMARY
notifier box empty and system frozen, keyboard and mouse and touch pad inoperative. Magic Keys Alt-sysreq-b or -o inoperative. power button only option

STEPS TO REPRODUCE
1. boot and log in
2. WiFi notification box outline appears
3. outline only

OBSERVED RESULT
notification box Outline appears, never fills in. system totally frozen. Happens on about 50% of system boots. Got a notification box that that something about gmenu crashed. System then proceeded to operate normally for remainder of time until shutdown. Also,when clicking on KDE symbol, box outline appears and maybe fills i after 30 to 40 seconds. It it doesn't appear, system is frozen. Pausing mouse pointer on a task bar icon, e.g., keyboard indicator, the box outline appears only.


EXPECTED RESULT
Notification box should be filled with notice that wifi is activated or filled with info on taskbar icon.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 19.10 and whatever is installed with Kubuntu 19.10.  
(available in About System)
KDE Plasma Version: whatever is installed with Kubuntu 19.10
KDE Frameworks Version: whatever is installed with Kubuntu 19.10 
Qt Version: whatever is installed with Kubuntu 19.10

ADDITIONAL INFORMATION
On Asus FX505DU laptop

Comment 1 Nate Graham 2020-09-09 03:24:47 UTC

I have noticed variants of this myself. Notifications seem to spike the CPU when they arrive. When there's a flood of them all at once, the result is a bunch of un-filled outlines and the whole system freezes.

Comment 2 Nate Graham 2020-09-09 03:40:42 UTC


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