After Plasma 6.3, I keep getting KWin closed unexpectedly

Help
, ,
1

After the recent set of updates to Plasma 6.3, my laptop displays a “Kwin closed unexpectedly” notification immediately after logging in to an X11 session. I don’t know all of the consequences of this, but I don’t see my wallpaper. Nothing really happens when I launch a terminal and enter kwin_x11 --replace.

Using Wayland is not an option for me because it seems to be worse with the latest update. It works fine but at random times the mouse becomes unresponsive or extremely slow, keyboard keys get invoked hundreds of times at random intervals and messing up my code.

Does anyone else see this issue? I don’t have any special graphics settings so I’d be happy to just reset all graphics settings to “factory defaults”, if that helps.

My system is:

Operating System: KDE neon 6.2
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-17-generic (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Intel® Xe Graphics
Manufacturer: Dell Inc.
Product Name: XPS 13 9310
2

I had a weird one - jerky desktop, animations/video were horrible.

Turns out that somehow, after updating my Display Settings had switched from 60 to 25fps…

So never underestimate the power of Plasma to inject some weird sh1t where you least expect it :wink:

Test on a new USER, verify, and if all else fails - sure, do a thorough cleanup and pull back settings from backups/snapshots until you worked it out.

3

This is what I see immediately after I log in:

image
image395×211 12.2 KB

Clicking “Restart App” doesn’t do anything.

I spoke too soon. I ran that command in a terminal and after I closed that terminal (because i thought it wasn’t doing anything), I cannot click anywhere on the screen. For example, clicking on the Start menu does not launch it or clicking on the taskbar to switch windows has not effect.

Here’s the relevant stuff I see with sudo journalctl --since=-15m:

Feb 20 10:33:42 replicon systemd-coredump[1786]: [🡕] Process 1396 (kwin_x11) of user 1000 dumped core.
                                                 
  Module libgomp.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
  Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
  Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.5.amd64
  Module libudev.so.1 from deb systemd-255.4-1ubuntu8.5.amd64
  Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
  Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
  Module libnxegl.so without build-id.

This is followed by a bunch of stack trace information that I am skipping. Any help as to how to fix it is appreciated.

4

I don’t know if 6.3.1 is available for neon but the first maintenance brought a bunch of fixes.

5

Thanks, I don’t see 6.3.1 yet. I suppose I just have to wait for it.

6

Better still:

#!/usr/bin/env bash

systemctl --user restart plasma-plasmashell.service

Call it ‘prestart’ and put it in ~/.local/usr/bin.

chmod +x prestart then run ‘prestart’ from krunner.

You seem to have ignored my advice to test this with a new USER…

Also, as meven states - we’ve just picked up 6.3.1 so you shouldn’t be far behind.

7

Thanks, that did the trick!

Creating new user felt a little too drastic. I was hoping to find another solution and keep that as a last resort. Thankfully, your suggestion to restart plasmashell has helped.

I’m waiting for it. Hopefully, that will fix it permanently.

8

It only takes a few seconds - and is easily removed when finished, but it’s the next best thing to trying your system with a completely clean $USER config.

Usually this clears issues, it satisfies you that it is not actually your system at fault - then you know it’s time to go back and work out which part of your home folder/hidden files are messing up - from .config and .local, cleaning up .cache etc.

1 Like
9

The errors stopped after I upgraded to plasma 6.3.1.