Bug 462289 - 100% reproducible core dump in KWin::Output::vrrPolicy() using 2 display port monitors after power saving wakeup
Summary: 100% reproducible core dump in KWin::Output::vrrPolicy() using 2 display port...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.26.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2022-11-26 21:38 UTC by Nigel Kukard
Modified: 2024-01-27 04:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0
Sentry Crash Report:


Attachments
Wayland core dump (142.90 KB, text/x-log)
2022-11-26 21:38 UTC, Nigel Kukard
Details
eglinfo (41.46 KB, text/plain)
2022-11-26 21:38 UTC, Nigel Kukard
Details
kscreen outputs (7.65 KB, text/plain)
2022-11-26 21:38 UTC, Nigel Kukard
Details
randr output (1.38 KB, text/plain)
2022-11-26 21:39 UTC, Nigel Kukard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nigel Kukard 2022-11-26 21:38:09 UTC
Created attachment 154058 [details]
Wayland core dump

SUMMARY

I have 2 AsusTek display port monitors connected to a Radeon 6600XT graphics adapter via DisplayPort.

Everything is fine, unless I leave the machine until the lock screen displays and the monitors power off.

When I come back and move the mouse, kwin_wayland crashes and all closed apps dissapear. After this the session is pretty much unsable and is just a blank black screen.

STEPS TO REPRODUCE
1.  Connect 2 display port monitors to a Radeon graphics adapter
2.  Leave the machine until the monitors power off after the lock screen is displayed
3.  Move the mouse, kwin_wayland core dumps

OBSERVED RESULT

kwin_wayland core dumps on monitor wakeup


EXPECTED RESULT

No core dumping and safe wakeup.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux

$ pacman -Q | grep -e plasma -e kde
kde-cli-tools 5.26.3-1
kde-gtk-config 5.26.3-1
kde-system-meta 22.08-2
kdeclarative 5.100.0-1
kdecoration 5.26.3-1
kded 5.100.0-1
kdegraphics-mobipocket 22.08.3-1
kdegraphics-thumbnailers 22.08.3-1
kdelibs4support 5.100.0-1
kdenetwork-filesharing 22.08.3-1
kdeplasma-addons 5.26.3-1
kdesu 5.100.0-1
libblockdev 2.28-1
plasma-browser-integration 5.26.3-1
plasma-desktop 5.26.3-1
plasma-disks 5.26.3-1
plasma-firewall 5.26.3-1
plasma-framework 5.100.1-1
plasma-integration 5.26.3-1
plasma-meta 5.25-1
plasma-nm 5.26.3-1
plasma-pa 5.26.3-1
plasma-sdk 5.26.3-1
plasma-systemmonitor 5.26.3-1
plasma-thunderbolt 5.26.3-1
plasma-vault 5.26.3-1
plasma-wayland-session 5.26.3-1
plasma-workspace 5.26.3-1
plasma-workspace-wallpapers 5.26.3-1
polkit-kde-agent 5.26.3-1
qt5-base 5.15.7+kde+r176-1
qt5-declarative 5.15.7+kde+r23-1
qt5-location 5.15.7+kde+r3-1
qt5-multimedia 5.15.7+kde+r1-1
qt5-quickcontrols2 5.15.7+kde+r6-1
qt5-speech 5.15.7+kde+r1-1
qt5-svg 5.15.7+kde+r9-1
qt5-tools 5.15.7+kde+r1-2
qt5-wayland 5.15.7+kde+r55-1
qt5-webchannel 5.15.7+kde+r3-1
xdg-desktop-portal-kde 5.26.3-1

ADDITIONAL INFORMATION
Attached some logs.
Comment 1 Nigel Kukard 2022-11-26 21:38:38 UTC
Created attachment 154059 [details]
eglinfo
Comment 2 Nigel Kukard 2022-11-26 21:38:55 UTC
Created attachment 154060 [details]
kscreen outputs
Comment 3 Nigel Kukard 2022-11-26 21:39:15 UTC
Created attachment 154061 [details]
randr output
Comment 4 Nigel Kukard 2022-11-26 21:40:51 UTC
I've tested this from a clean installation just to make sure nothing I had done caused it.
Comment 5 Nate Graham 2022-11-30 20:18:08 UTC
Pasting backtrace inline for searchability:


Nov 26 21:10:53 nkukard-desktop2.lan systemd-coredump[30026]: Process 1750 (kwin_wayland) of user 11000 dumped core.
Stack trace of thread 1750:
#0  0x00007f45e67b5ebb _ZNK4KWin6Output9vrrPolicyEv (libkwin.so.5 + 0x1b5ebb)
#1  0x00007f45e67b68a0 _ZNK4KWin19OutputConfiguration14constChangeSetEPNS_6OutputE (libkwin.so.5 + 0x1b68a0)
#2  0x00007f45e67b697d _ZN4KWin19OutputConfiguration9changeSetEPNS_6OutputE (libkwin.so.5 + 0x1b697d)
#3  0x00007f45e69b07ad n/a (libkwin.so.5 + 0x3b07ad)
#4  0x00007f45e25094f6 n/a (libffi.so.8 + 0x74f6)
#5  0x00007f45e2505f5e n/a (libffi.so.8 + 0x3f5e)
#6  0x00007f45e2508b73 ffi_call (libffi.so.8 + 0x6b73)
#7  0x00007f45e3900ada n/a (libwayland-server.so.0 + 0x8ada)
#8  0x00007f45e3905010 n/a (libwayland-server.so.0 + 0xd010)
#9  0x00007f45e39039e2 wl_event_loop_dispatch (libwayland-server.so.0 + 0xb9e2)
#10 0x00007f45e6996e4a _ZN14KWaylandServer7Display14dispatchEventsEv (libkwin.so.5 + 0x396e4a)
#11 0x00007f45e4ebda51 n/a (libQt5Core.so.5 + 0x2bda51)
#12 0x00007f45e4ebf904 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2bf904)
#13 0x00007f45e4ebfa48 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2bfa48)
#14 0x00007f45e4578b1c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b1c)
#15 0x00007f45e4e8cf98 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28cf98)
#16 0x00007f45e4ed690c _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x2d690c)
#17 0x00007f45e4ed7a01 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d7a01)
#18 0x0000559e7240e952 n/a (kwin_wayland + 0x12c952)
#19 0x00007f45e4e8573c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28573c)
#20 0x00007f45e4e90269 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x290269)
#21 0x0000559e7232f611 n/a (kwin_wayland + 0x4d611)
#22 0x00007f45e3e3c290 n/a (libc.so.6 + 0x23290)
#23 0x00007f45e3e3c34a __libc_start_main (libc.so.6 + 0x2334a)
#24 0x0000559e72330c95 n/a (kwin_wayland + 0x4ec95)
Comment 6 Zamundaaa 2024-01-22 17:20:20 UTC
I fixed a bunch of similar issues with https://invent.kde.org/plasma/kwin/-/commit/20b94c90251719729d1ac42edae92ecc4da0e098, so I assume this is fixed. If it's still happening for you, please reopen this