[kwin] [Bug 462289] 100% reproducible core dump in KWin::Output::vrrPolicy() using 2 display port monitors after power saving wakeup
https://bugs.kde.org/show_bug.cgi?id=462289 Nate Graham changed: What|Removed |Added Version Fixed In|5.27.0 |6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462289] 100% reproducible core dump in KWin::Output::vrrPolicy() using 2 display port monitors after power saving wakeup
https://bugs.kde.org/show_bug.cgi?id=462289 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/20b94c9025 ||1719729d1ac42edae92ecc4da0e ||098 Status|REPORTED|RESOLVED Version Fixed In||5.27.0 --- Comment #6 from Zamundaaa --- 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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462289] 100% reproducible core dump in KWin::Output::vrrPolicy() using 2 display port monitors after power saving wakeup
https://bugs.kde.org/show_bug.cgi?id=462289 Nate Graham changed: What|Removed |Added Keywords||wayland CC||n...@kde.org, ||xaver.h...@gmail.com Summary|[kwin_wayland] 100% |100% reproducible core dump |reproducible core dump |in |using 2 display port|KWin::Output::vrrPolicy() |monitors after power saving |using 2 display port |wakeup |monitors after power saving ||wakeup --- Comment #5 from Nate Graham --- 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 0x7f45e67b5ebb _ZNK4KWin6Output9vrrPolicyEv (libkwin.so.5 + 0x1b5ebb) #1 0x7f45e67b68a0 _ZNK4KWin19OutputConfiguration14constChangeSetEPNS_6OutputE (libkwin.so.5 + 0x1b68a0) #2 0x7f45e67b697d _ZN4KWin19OutputConfiguration9changeSetEPNS_6OutputE (libkwin.so.5 + 0x1b697d) #3 0x7f45e69b07ad n/a (libkwin.so.5 + 0x3b07ad) #4 0x7f45e25094f6 n/a (libffi.so.8 + 0x74f6) #5 0x7f45e2505f5e n/a (libffi.so.8 + 0x3f5e) #6 0x7f45e2508b73 ffi_call (libffi.so.8 + 0x6b73) #7 0x7f45e3900ada n/a (libwayland-server.so.0 + 0x8ada) #8 0x7f45e3905010 n/a (libwayland-server.so.0 + 0xd010) #9 0x7f45e39039e2 wl_event_loop_dispatch (libwayland-server.so.0 + 0xb9e2) #10 0x7f45e6996e4a _ZN14KWaylandServer7Display14dispatchEventsEv (libkwin.so.5 + 0x396e4a) #11 0x7f45e4ebda51 n/a (libQt5Core.so.5 + 0x2bda51) #12 0x7f45e4ebf904 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2bf904) #13 0x7f45e4ebfa48 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2bfa48) #14 0x7f45e4578b1c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b1c) #15 0x7f45e4e8cf98 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28cf98) #16 0x7f45e4ed690c _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x2d690c) #17 0x7f45e4ed7a01 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d7a01) #18 0x559e7240e952 n/a (kwin_wayland + 0x12c952) #19 0x7f45e4e8573c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28573c) #20 0x7f45e4e90269 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x290269) #21 0x559e7232f611 n/a (kwin_wayland + 0x4d611) #22 0x7f45e3e3c290 n/a (libc.so.6 + 0x23290) #23 0x7f45e3e3c34a __libc_start_main (libc.so.6 + 0x2334a) #24 0x559e72330c95 n/a (kwin_wayland + 0x4ec95) -- You are receiving this mail because: You are watching all bug changes.
