Bug 506822

Summary:	Excessive Crashing happening in Plasmashell due to notifications & other elements
Product:	[Plasma] plasmashell	Reporter:	Pyx <kde>
Component:	Notifications	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	crash	CC:	kde, kde, kdedev
Priority:	NOR
Version First Reported In:	6.4.0
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Pyx 2025-07-09 20:09:59 UTC

SUMMARY

Sometimes, when receiving notifications, Plasmashell will sometimes either crash and reload or infinitely hang, requiring manual intervention.

STEPS TO REPRODUCE
Log into Plasma 6.4<
Receive many notifications, mine are happening in the "Vesktop" (discord) program

OBSERVED RESULT
Sometimes, Plasmashell will crash.

EXPECTED RESULT
Plasmashell should not be crashing *nearly* as much as it has been.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × 13th Gen Intel® Core™ i3-13100F
Memory: 48 GB of RAM (46.9 GB usable)
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER

ADDITIONAL INFORMATION
Before upgrading to 6.4 Plasmashell hardly crashed at all but now I'm observing 10+ crashes and hangs a day, some persisting over reboots like my current inability to launch Krunner (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) or use Alt A to open my taskbar.

Comment 1 TraceyC 2025-07-09 22:22:52 UTC

As the message at the top of the summary says, 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 ?

Comment 2 Pyx 2025-07-09 22:26:12 UTC

(In reply to TraceyC from comment #1)
> As the message at the top of the summary says, 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 ?

Here is the output: https://gist.github.com/pyxfluff/694f1295d4a0ef1ffd0d56973f505f06

Comment 3 David Edmundson 2025-07-10 09:16:34 UTC

>                #4  0x00007fe79f3c12e3 n/a (libnvidia-glcore.so.575.64.03 + 0xfc12e3)

Crash is in nvidia, there's not much we can do, sorry.

>                #4  0x00007fe7cf169ac6 n/a (libWallpaperEngineKde.so + 0x369ac6)

Please try without wallpaper engine.

Comment 4 Pyx 2025-07-10 09:20:33 UTC

(In reply to David Edmundson from comment #3)
> >                #4  0x00007fe79f3c12e3 n/a (libnvidia-glcore.so.575.64.03 + 0xfc12e3)
> 
> Crash is in nvidia, there's not much we can do, sorry.
Sad but understood. I thought I was done with the weird nvidia + linux issues but I guess not.

> >                #4  0x00007fe7cf169ac6 n/a (libWallpaperEngineKde.so + 0x369ac6)
> 
> Please try without wallpaper engine.

It is actually disabled right now, my wallpaper is the default Plasma one because I had to reset my configuration last night due to an infinite crash loop. It shouldn't be affecting anything.