Help with plasmashell stuck in a crashing loop

Help
1

whenever I start my computer my plasmashell begins crashing immediately after I login, this started after a forced shutdown due to a gamefreeze that also caused a plasmashell crash. the developer/debug info is here


This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.fedoraproject.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.
[New LWP 3573]
[New LWP 3572]
[New LWP 3509]
[New LWP 3508]
[New LWP 3036]
[New LWP 2988]
[New LWP 2983]
[New LWP 2982]
[New LWP 2981]
[New LWP 2980]
[New LWP 2975]
[New LWP 2974]
[New LWP 2970]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f094a0876c2 in __syscall_cancel_arch () from /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 783, in print_preamble_internal
    resolve_modules()
    ~~~~~~~~~~~~~~~^^
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 766, in resolve_modules
    raise RuntimeError("No corefile found. Cannot resolve modules.")
RuntimeError: No corefile found. Cannot resolve modules.
No corefile found. Cannot resolve modules.
A debugging session is active.

    Inferior 1 [process 2968] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 2968) detached]
Sentry is attempting to send 2 pending events
Waiting up to 30 seconds
Press Ctrl-C to quit
Debugging ended with exit code '1' and exit status 'NormalExit' ```
The terminal shows some variation of this after using `killall plasmashell' to interrupt the loop
```IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG"
IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG"
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::end: Painter not active, aborted
KCrash: Attempting to start /usr/bin/plasmashell
KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
kf.plasma.quick: Applet preload policy set to 1```
1 Like
2

FIXED: I used a second user to delete the .config of my primary user, this was a bit brute force bc I didn’t know what in that folder was causing the issue, but it did work.

3

@Symphony I had exactly the same symptoms occur yesterday. I was still able to spawn a terminal via the shortcut ctrl+alt+T , which allowed me to tinker with removing drivers, rolling things back, updating, etc. I even removed my GPU and tried to fall back to my Intel iGPU, but had no luck.

In the end, I did find a solution! In this thread: archlinux topic ID 300012 it was mentioned that changing settings in the Plasma Renderer settings could resolve a similar issue. After launching the settings pane (/usr/bin/kcmshell6 kcm_qtquicksettings), I changed the Rendering Backend to Open GL and the Render Loop to Threaded. This seems to have resolved the crash loop and I am now reinstalling my Nvidia drivers to see how things go.

1 Like
4

@dan0v Thank you so much! The kcmshell6 kcm_qtquicksettings fixed the problem entierly for me. I never knew that menu existed! :clap:

When I started it (you can use Alt+Space to open KRunner even when KDE Plasma is crashed and black wallpaper) “Rendering Backend” was set to “Software”! I changed it back to “Automatic” and “Render Loop” was already set to “Automatic”, and it worked.

BTW Plasma started crashing, after I was playing a Game with HDR enabled, and when I tried to take a Screenshot, with Spectacle (Print Screen Button). It was so strange to me that it happened like that… :sweat_smile: :face_with_monocle: