Random segfaults in kwin_wayland libQt6Core.so.6.7.2

Desktop Environments Plasma
1

Hello all! This last month or so I’ve been having an issue where my screens will freeze for about a second, then kwin restarts, taking most things with it. Looking at three seperate crashes in journalctl and grabbing the first strange lines I’m seeing

linux-desktop systemd-coredump[139845]: Process 4160 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing...
linux-desktop kernel: Code: 31 ff 48 8d 75 c0 c6 45 bf 00 48 89 5d c0 4c 89 65 c8 48 89 45 d0 e8 c3 4d f9 ff 84 c0 75 a1 48 8b 43 08 48 8d 0d 94 f5 ff ff <4c> 8b 70 58 4d 89 f5 41 8b 56 08 48 8b 3d 2a 7a 4b 00 8d 42 01 41
linux-desktop kernel: kwin_wayland[4160]: segfault at 30057 ip 00007d5ac2144c9c sp 00007fff5e6f0e00 [7d5ac208a000+394000] likely on CPU 5 (core 6, socket 0)
...
linux-desktop systemd-coredump[388456]: Process 287871 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing...
linux-desktop kernel: Code: 31 ff 48 8d 75 c0 c6 45 bf 00 48 89 5d c0 4c 89 65 c8 48 89 45 d0 e8 c3 4d f9 ff 84 c0 75 a1 48 8b 43 08 48 8d 0d 94 f5 ff ff <4c> 8b 70 58 4d 89 f5 41 8b 56 08 48 8b 3d 2a 7a 4b 00 8d 42 01 41
linux-desktop kernel: kwin_wayland[287871]: segfault at 89 ip 00007e03a3744c9c sp 00007fff164070e0 error 4 in libQt6Core.so.6.7.2 (deleted)[7e03a368a000+394000] likely on CPU 3 (core 4, socket 0)
...
linux-desktop systemd-coredump[477069]: Process 388513 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing...
linux-desktop kernel: Code: 31 ff 48 8d 75 c0 c6 45 bf 00 48 89 5d c0 4c 89 65 c8 48 89 45 d0 e8 a3 41 f9 ff 84 c0 75 a1 48 8b 43 08 48 8d 0d 94 f5 ff ff <4c> 8b 70 58 4d 89 f5 41 8b 56 08 48 8b 3d aa ec 4b 00 8d 42 01 41
linux-desktop kernel: kwin_wayland[388513]: segfault at 620a28000158 ip 00007baa11745a1c sp 00007ffd6772c5a0 error 4 in libQt6Core.so.6.7.2[7baa1168a000+39c000] likely on CPU 4 (core 5, socket 0)

My info center
Operating System: EndeavourOS
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.6.47-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

Kwin debugging asks for qdbus info, so here’s a pastebin for that

I’ve tried searching around but wasn’t able to find anything, so any help or troubleshooting tips would be greatly appreciated!

2

Just to try help narrow things down, does the same happen with only one monitor attached? If you sign in with a new user does the same happen?

3

They are pretty random infrequent, so I haven’t done too drastic of testing. But I can try them out and see if it happens again the next couple of days.

4

A couple of sources (here and here) point to the presence of a setting in ~/.config/kdeglobals as being a culprit.

This setting isn’t in my kdeglobals file, so not present by default it seems.

To check if it’s present, this will either return nothing (you don’t have this setting, so nevermind), or it’ll return the line number followed by the setting’s current value:

cat -n ~/.config/kdeglobals | grep SceneGraphBackend

If the setting is present, the advice offered at those links is to remove these lines from the file (then restart):

[QtQuickRendererSettings]
SceneGraphBackend=software
5 
cat -n ~/.config/kdeglobals | grep SceneGraphBackend

Doesn’t return anything, I poked around in etc to see if there was a system one, but didn’t see a kdeglobals.

1 Like
6

Not that then :wink:
…the hunt continues.

7

Thank you for trying!

2 Likes
8

Just had a side thought here, have you asked over on the kde forum? https://discuss.kde.org/
It may or may not help

1 Like
9

Definitely will now, thank you!

1 Like
10

Probably this bug here. https://bugs.kde.org/show_bug.cgi?id=488713
Happens to me exactly once a day. Seems to be related to some kind of timer in Qt

1 Like
11

Perhaps try X11 @blythe. The issue does seem to be Wayland related.

1 Like
12

Thank you! Looks like it might be the case. Is there anything I do to add to the troubleshooting there, or should I just keep an eye on it and see if it’s my issue?

13

Yeah, that might be the easiest, I will miss the smoothness of wayland, but hopefully the bug doesn’t stick too long!

14

You’re not alone. Wayland still remains too buggy for my everyday use on my workstation (with Nvidia GPU).

15

Just keep an eye on it. I’m pretty sure they are working on it. A lot of different bugs have been marked as duplicates of this bug as they have traced the issue to its root cause.

16

Following the instructions here → https://discussion.fedoraproject.org/t/fixed-updating-kinoite-broke-things-not-even-a-rollback-fixes-it/123578/7

That option can be found by checking “plasma renderer” in the start menu. Setting “rendering backend” to “automatic” fixed the issue for me