Bug 483103 - Frequent Segfaulting in libkwin.so since KDE6 upgrade
Summary: Frequent Segfaulting in libkwin.so since KDE6 upgrade
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-10 12:04 UTC by leon.beer
Modified: 2024-04-09 03:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leon.beer 2024-03-10 12:04:16 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
Behaviour occurs Randomly, when under medium to high Graphical load
OBSERVED RESULT
All applications close and The entire KDE Desktop goes blank before reinitializing as if just rebooted.

EXPECTED RESULT

Kwin gracefully handling the crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux 6.7.9-zen1-1-zen
(available in About System)
KDE Plasma Version:  6.0.1
KDE Frameworks Version: 6.0.0 
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Same crash was happening in earlier versions of KDE5, until it was fixed in an unknown update.
Using Garuda Linux.

DMESG output:

```[   30.994891] BTRFS: device fsid fd0b99f1-3a33-4e92-960e-1b471b15da7b devid 1 transid 3222 /dev/sda1 scanned by pool-udisksd (4031)
[   31.004425] BTRFS info (device sda1): first mount of filesystem fd0b99f1-3a33-4e92-960e-1b471b15da7b
[   31.004439] BTRFS info (device sda1): using crc32c (crc32c-intel) checksum algorithm
[   31.004444] BTRFS info (device sda1): using free space tree
[   31.022738] ntfs3: Max link count 4000
[   31.022740] ntfs3: Enabled Linux POSIX ACLs support
[   31.022741] ntfs3: Read-only LZX/Xpress compression included
[   31.023733] ntfs3: sdb3: It is recommened to use chkdsk.
[   31.025111] ntfs3: sdb3: volume is dirty and "force" flag is not set!
[   31.633019] BTRFS info (device sda1): auto enabling async discard
[   31.678997] Bluetooth: RFCOMM TTY layer initialized
[   31.679006] Bluetooth: RFCOMM socket layer initialized
[   31.679008] Bluetooth: RFCOMM ver 1.11
[   32.482263] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   45.645925] systemd-journald[550]: Time jumped backwards, rotating.
[   63.686359] BTRFS info: devid 1 device path /dev/nvme0n1p2 changed to /dev/disk/by-uuid/e37a4f59-b128-457f-a395-347ee01997e7 scanned by Thread (pooled) (12195)
[  211.435890] Guest personality initialized and is inactive
[  211.435937] VMCI host device registered (name=vmci, major=10, minor=120)
[  211.435938] Initialized host personality
[  211.439068] NET: Registered PF_VSOCK protocol family
[ 7043.042342] amdgpu 0000:2d:00.0: [drm] enabling link 1 failed: 15
[ 7043.087611] snd_hda_codec_hdmi hdaudioC0D0: HDMI: Unknown ELD version 0
[ 8921.959870] kwin_wayland[3728]: segfault at 7ffc10a04fa8 ip 00007ec8c67681c7 sp 00007ffc10a04fb0 error 6 in libkwin.so.6.0.1[7ec8c6745000+454000] likely on CPU 3 (core 3, socket 0)
[ 8921.959881] Code: 48 81 ec 28 03 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 18 03 00 00 31 c0 4c 8d a4 24 c0 00 00 00 4c 8d b4 24 80 00 00 00 <ff> 15 eb 3e 5d 00 48 8b 6b 08 4c 89 e7 4c 8b 68 10 4c 89 ee ff 15
[10786.426121] kwin_wayland[1531118]: segfault at 7ffc97956fe8 ip 000079aeba1681c7 sp 00007ffc97956ff0 error 6 in libkwin.so.6.0.1[79aeba145000+454000] likely on CPU 14 (core 6, socket 0)
[10786.426132] Code: 48 81 ec 28 03 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 18 03 00 00 31 c0 4c 8d a4 24 c0 00 00 00 4c 8d b4 24 80 00 00 00 <ff> 15 eb 3e 5d 00 48 8b 6b 08 4c 89 e7 4c 8b 68 10 4c 89 ee ff 15```
Comment 1 Nicolas Fella 2024-03-10 12:30:08 UTC
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?

Thanks!
Comment 2 leon.beer 2024-03-10 12:55:02 UTC
(In reply to Nicolas Fella from comment #1)
> 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?
> 
> Thanks!

Heya, Coredumpctl does not list a valid crash for kwin directly, only for plasmashell (This one is too old to be the right one) and Xwayland (Also too old), as well as discord, whcih are the only recent ones
Comment 3 Bug Janitor Service 2024-03-25 03:46:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-04-09 03:48:25 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!