Created attachment 160197 [details] output from systemd-coredump for three crashes SUMMARY I run KDE on a laptop, which I periodically attach to a 4K monitor/keyboard using a USB 3.0 hub. If I use my laptop standalone, allow it to go into standby, then connect to the monitor, when it wakes, kwin dumps core fairly frequently (I can't be sure that it's every time, but certainly frequently enough that I now avoid the scenario entirely if possible). Under the following scenario: * use laptop standalone * allow laptop to go into standby * connect laptop to hub * wake up laptop STEPS TO REPRODUCE 1. use laptop standalone 2. allow laptop to go into standby 3. connect laptop to hub 4. wake up laptop and enter credentials OBSERVED RESULT kwin_wayland dumps core and restarts, apps require restart EXPECTED RESULT kwin_wayland doesn't dump core SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 (but has been happening for a while through several versions) KDE Frameworks Version: 5.107 Qt Version: 5.15.10 ADDITIONAL INFORMATION (this doesn't appear version specific but including for completeness) Kernel: 6.4.2-arch1-1 GPU: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev d1) Mesa: 23.1.3-1
#0 0x00007fead478ac03 n/a (libkwin.so.5 + 0x38ac03) #1 0x00007fead478b299 _ZN4KWin9DrmOutput12setGammaRampERKSt10shared_ptrINS_19ColorTransformationEE (libkwin.so.5 + 0x38b299) #2 0x00007fead45baf95 _ZN4KWin11ColorDevice6updateEv (libkwin.so.5 + 0x1baf95) #3 0x00007fead2cd06a7 n/a (libQt5Core.so.5 + 0x2d06a7) #4 0x00007fead45c6096 _ZN4KWin6Output8setStateERKNS0_5StateE (libkwin.so.5 + 0x1c6096) #5 0x00007fead478534a _ZN4KWin9DrmOutput14updateDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x38534a) #6 0x00007fead4788524 _ZN4KWin9DrmOutput14setDrmDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x388524) #7 0x00007fead4788760 _ZN4KWin9DrmOutput11setDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x388760) #8 0x00007fead475e7dc _ZN4KWin10DrmBackend13turnOutputsOnEv (libkwin.so.5 + 0x35e7dc) #9 0x00007fead4786142 _ZN4KWin9DrmOutput18applyQueuedChangesERKNS_19OutputConfigurationE (libkwin.so.5 + 0x386142) #10 0x00007fead4768160 _ZN4KWin10DrmBackend18applyOutputChangesERKNS_19OutputConfigurationE (libkwin.so.5 + 0x368160) #11 0x00007fead470da8d _ZN4KWin9Workspace25updateOutputConfigurationEv (libkwin.so.5 + 0x30da8d) #12 0x00007fead470e3cd _ZN4KWin9Workspace31slotOutputBackendOutputsQueriedEv (libkwin.so.5 + 0x30e3cd) #13 0x00007fead2cd06a7 n/a (libQt5Core.so.5 + 0x2d06a7) #14 0x00007fead476addf _ZN4KWin10DrmBackend13updateOutputsEv (libkwin.so.5 + 0x36addf) #15 0x00007fead4764298 _ZN4KWin10DrmBackend15handleUdevEventEv (libkwin.so.5 + 0x364298) #16 0x00007fead2cd06a7 n/a (libQt5Core.so.5 + 0x2d06a7) #17 0x00007fead2cd1ea4 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2d1ea4) #18 0x00007fead2cd1fe8 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2d1fe8) #19 0x00007fead237893f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x17893f) #20 0x00007fead2c9b778 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29b778) #21 0x00007fead2ce919c _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x2e919c) #22 0x00007fead2cea1e5 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ea1e5) #23 0x000055d9dddc9502 n/a (kwin_wayland + 0x134502) #24 0x00007fead2c9a484 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29a484) #25 0x00007fead2c9b923 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x29b923) #26 0x000055d9ddce52fb n/a (kwin_wayland + 0x502fb) #27 0x00007fead1c39850 n/a (libc.so.6 + 0x23850) #28 0x00007fead1c3990a __libc_start_main (libc.so.6 + 0x2390a) #29 0x000055d9ddce6ed5 n/a (kwin_wayland + 0x51ed5)
Please attach the output of drm_info (https://gitlab.freedesktop.org/emersion/drm_info)
Created attachment 160534 [details] drm_info without external screen
Created attachment 160535 [details] drm_info with external screen attached
Sure. I've added two attachments; one with, one without the external screen.
I can't think of a way this could happen, we'll need a better backtrace. Can you please install debuginfod if you haven't already, start the gdb console with > coredumpctl debug kwin_wayland and then get the backtrace with "bt full"?
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!
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!