Hey!
I usually keep my OS up to date daily. Recently after updates I encountered that KDE Plasma shell has been crashing a lot. I had to roll back to about august 28 at least. Now it is stable. Did anyone else encounter this problem recently?
1 Like
Hi, I’d like to report ‘No’, personally I haven’t experienced any Plasma shell crashes.
Questions:
- How do you update?
- X11 or Wayland?
- NVIDIA involved?
I update in the terminal with the command sudo zypper dup
X11
GTX 1070 8Gb card.
For now I suggest you try on Wayland, and report if the crashes persist.
Another question: Was anything customized? I.e. theming, widgets?
I did experience quite some crashes recently but I don’t remember which version. All I know is that sometimes out of nowhere, KDE will crash numerous times consecutively.
1 Like
Please don’t come up with just anecdotes. Your post contains zero information.
2 Likes
I have been experiencing Plasma shell crashes too, I have two computers on Tumbleweed 20250829, Intel integrated graphics, Wayland, default panel configurations and themes. For me, Plasma shell crashes are usually triggered by web browsers, such as Google Chrome; and Plasma shell will attempt to reload after a crash only to continuously crash indefinitely until the web browser is closed. This has never happened to me before until Tumbleweed 20250829 and I check on Discover every day to see if there’s a Plasma update that would fix that.
1 Like
I can confirm this is happening to me too, since one of the updates in the last two weeks. For me plasmashell is crashing when opening certain files (some .mp3 files in VLC Player for example). It then crashes in an infinite loop until the files are closed again.
I use an Nvidia GPU and Wayland. Some custom themes but nothing crazy. Already tried deleting the respective .cache and .config folders, the problem persists.
The crash handler tells me that it couldn’t collect any data and then gives me this:
Starting debugger gdb --init-eval-command=set auto-solib-add off --nw --nx --batch --command=/tmp/drkonqi.hEgBHf --command=/tmp/drkonqi.qjkvUS --core=/tmp/drkonqi-core.fCEoxy/core /usr/bin/plasmashell
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.opensuse.org/>
Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
warning: Can't open file /home/User/.cache/plasmashell/qmlcache/5b7bbfd96267d74c2fdae847420d463d51481b0a.qmlc (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing
warning: Can't open file /home/User/.cache/plasmashell/qmlcache/0616d79c8d9e078afcf8b3de51c2335fd990d994.qmlc (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:/.glXXXXXX (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed mapping note processing
warning: Can't open file /home/User/.cache/plasmashell/qmlcache/fc599fdd317071f4185a148ca3787910deb87469.qmlc (deleted) during file-backed mapping note processing
warning: Can't open file /home/User/.cache/plasma_theme_default.kcache (deleted) during file-backed mapping note processing
warning: Can't open file /home/User/.cache/plasmashell/qmlcache/ceea0ef8d55135e6277d50918e758bf1836b1f55.qmlc (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing
[New LWP 2641]
[New LWP 2734]
[New LWP 2687]
[New LWP 2757]
[New LWP 2655]
[New LWP 2726]
[New LWP 2656]
[New LWP 2740]
[New LWP 2650]
[New LWP 5322]
[New LWP 5323]
[New LWP 5166]
[New LWP 5326]
[New LWP 5327]
[New LWP 5439]
[New LWP 5342]
[New LWP 5164]
[New LWP 2753]
[New LWP 5324]
[New LWP 5325]
[New LWP 5165]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fd896a9dd5c in __pthread_kill_implementation () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fd8931ad580 (LWP 2641))]
python sentry-sdk not installed :(
Cannot QML trace cores :(
add symbol table from file "/lib64/libc.so.6"
Traceback (most recent call last):
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 812, in print_preamble
print_preamble_internal()
~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 803, in print_preamble_internal
print_sentry_payload(thread)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 727, in print_sentry_payload
payload = SentryEvent().make(program, thread)
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 520, in make
stacktrace = SentryTrace(crash_thread, True).to_dict()
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 367, in to_dict
SentryTrace.load_solib(self.thread, cramped_memory)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 351, in load_solib
sentry_sdk.add_breadcrumb(
^^^^^^^^^^
NameError: name 'sentry_sdk' is not defined
name 'sentry_sdk' is not defined
Debugging ended with exit code '1' and exit status 'NormalExit'
Don’t really know what to make of it.
I have experienced plasma crashing since a few updates ago. For me it is confined strictly with 2 applications. (1) Deadbeef. Upon launching Deadbeef plasma crashes and the automatic bug reporter opens and I submit the crash report.
(2) I uninstalled Deadbeef and installed Qmmp. With Qmmp plasma would crash sporadically upon launching. The automatic bug reporter opens and I submit the crash report.
Yesterday Qmmp began to crash with each launch. So I uninstalled Qmmp, cleared the .dot files, reinstalled Qmmp and it seems to hold up.
Anecdotal I know, should it happen again I project to launch Qmmp from the terminal and include that with the automatic bug reporter. As soon as this is posted , will launch Qmmp from a terminal, and see how it goes (not wanting another crash to obliterate my post).
[A reply to myself, told by that this post was either too long or too old to edit]
Launched Qmmp from the terminal and no plasma crash. (For what it’s worth).
I’ve encountered the inifnite loop as well. I can’t even report the crash because it crashes again in an infinite loop
1 Like
I’ve tried updating again. Seemed stable no crashes. altouh there was an nvidia driver update that wasn’t there before.
I recently play some retro games like VTM Bloodline - became unplayable, Kingpin Life of Crime dropped me an error that I need a graphics card that supports OpenGL. WTF is happenning? Rolled back again to August 28, they work fine again.
Did you reboot after the NVIDIA driver update?
Well, you cannot rollback forever. I don’t see any real attempt to fix anything.
Yes.
Been a broken, crashing, freezing mess since SELinux changes.
Yes. I always reboot after every update. But I saw another topic on nvidia drivers problem 
I locked nvidia updates and updated everything else. Seemed stable, now I’ve got another plasma crash
Where did you get the advice to do that? In short: you should not.
Theres a topic that the nvidia updates broke stuff, and I also experienced this. Thats why I tried it
There are dozens of NVIDIA related topics 
. With
I meant a URL to the thread/post