[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #40 from Tomasz Paweł Gajc --- Openmandriva Lx Cooker with Plasma-5.22.3, Frameworks-5.84.0 and up to date patchset for Qt5 i no longer observer any plasmashell crashes with Wayland. coredumpctl is clean when my monitor goes into standby, but yet plasmashell as a process is terminated: Jul 18 00:50:36 omv-rockpro64 org_kde_powerdevil[97696]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 kded5[97674]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: Old primary output: QScreen(0x3a12a290, name="HDMI-A-1") New primary output: QScreen(0x3bd30840, name="") Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:121: TypeError: Cannot read property 'x' of null Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:135: TypeError: Cannot read property 'y' of null Jul 18 00:50:36 omv-rockpro64 systemd[84533]: Started dbus-:1.2-org.kde.KSplash@2.service. Jul 18 00:50:37 omv-rockpro64 kded5[97674]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. Jul 18 00:50:37 omv-rockpro64 plasmashell[97698]: The Wayland connection experienced a fatal error: Błąd protokołu Jul 18 00:50:40 omv-rockpro64 kded5[97674]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:40 omv-rockpro64 org_kde_powerdevil[97696]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:40 omv-rockpro64 kded5[97674]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. Jul 18 00:51:17 omv-rockpro64 klauncher[97917]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jul 18 00:51:37 omv-rockpro64 plasma_waitforname[97885]: org.kde.knotifications: WaitForName: Service was not registered within timeout Jul 18 00:51:37 omv-rockpro64 systemd[84533]: dbus-:1.2-org.kde.KSplash@2.service: Main process exited, code=exited, status=1/FAILURE Jul 18 00:51:37 omv-rockpro64 systemd[84533]: dbus-:1.2-org.kde.KSplash@2.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #39 from Xu Zhao --- (In reply to Nate Graham from comment #37) > Is this affected by the fix for Bug 438789? No, I tested with patched kwin, and the problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #38 from Mircea Kitsune --- I could confirm today the issue is far from resolved in Plasma 5.22 (Manjaro Linux) albeit it has gotten a step closer to being fixed. I tried the Wayland session and let my monitor go into standby with the following results: This time I'm taken to a black screen with a message written in large font, saying the screen locker stopped working and I need to use a systemctl command to unlock my session. Out of curiosity I jumped to another runlevel (Control + Alt + F#) logged in as root and unlocked: This time I could at least return to my session without noticing any major glitches! But icons on my taskbar were reordered, indicating plasmashell might have crashed and restarted. The monitor obviously didn't remain in standby: It attempts going to sleep then wakes up and I'm faced with the message about the screen locker crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #37 from Nate Graham --- Is this affected by the fix for Bug 438789? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Xu Zhao changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #36 from Xu Zhao --- Can confirm this issue on openSUSE Tumbleweed 20210701, KDE Plasma 5.22.2, KDE Frameworks 5.83.0 on Wayland, AMD 6800 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 oxal...@pm.me changed: What|Removed |Added CC||oxal...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=438839 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Patrick Silva changed: What|Removed |Added Keywords||wayland CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437808 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added CC||neopy...@gmail.com --- Comment #35 from Nate Graham --- *** Bug 433342 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Yannick changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #34 from Yannick --- I have the exact same issue as Rainer Finke described, on Plasma 5.22.0. Plasmashell crashes just by turning my DisplayPort monitor off and on. Restarting plasmashell brings the session back. Sadly I didn't find any related core dump with coredumpctl. OS: Arch Linux KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9 GPU: AMD RX560 (mesa drivers) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #33 from Mircea Kitsune --- (In reply to Rainer Finke from comment #32) > I tried it on Plasma 5.22 beta. Just by turning the monitor off and on again > with the power button, the plasmashell/session will crash. But Kwin kept > running so I was able to manually start plasmashell again. > > Operating System: Arch Linux > KDE Plasma Version: 5.21.90 > KDE Frameworks Version: 5.82.0 > Qt Version: 5.15.2 > Kernel Version: 5.12.3-arch2-1 (64-bit) > Graphics Platform: Wayland > Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor > Memory: 31.4 GiB of RAM > Graphics Processor: AMD Radeon VII This is concerning: The release notes for 5.22 say the issue should have been fixed, and I was hoping to try moving to Wayland again given this was the core reason why I had to revert back to X11. I understand WL had issues knowing how to handle itself when all displays are disconnected and none are left active at a given moment, which should have been addressed in the display stack code. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Anthony Messina changed: What|Removed |Added CC||amess...@messinet.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #32 from Rainer Finke --- I tried it on Plasma 5.22 beta. Just by turning the monitor off and on again with the power button, the plasmashell/session will crash. But Kwin kept running so I was able to manually start plasmashell again. Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.3-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon VII -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Bernie Innocenti changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #31 from Bernie Innocenti --- (In reply to Mircea Kitsune from comment #30) > (In reply to Tomasz Paweł Gajc from comment #29) > > I hear Plasma 5.22 comes with some improvements for Wayland. No idea if that > includes this issue, perhaps let us know if you notice a difference after > its update. No, last week it was still happening on git master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #30 from Mircea Kitsune --- (In reply to Tomasz Paweł Gajc from comment #29) I hear Plasma 5.22 comes with some improvements for Wayland. No idea if that includes this issue, perhaps let us know if you notice a difference after its update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Tomasz Paweł Gajc changed: What|Removed |Added CC||tpg...@gmail.com --- Comment #29 from Tomasz Paweł Gajc --- same thing happens on OpenMandriva Lx cooker with up to date Plasma 5.21.5 and framweworks 5.82.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #28 from Santiago Cézar --- Here is the info I got from coredumpctl for plasmashell PID: 53482 (plasmashell) UID: 1002 (santi) GID: 1002 (santi) Signal: 6 (ABRT) Timestamp: Thu 2021-05-06 17:16:29 -03 (7min ago) Command Line: plasmashell -d -n Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1002.slice/user@1002.service/app.slice/app-org.kde.konsole-c7898390fcab48f4a33a7b08fc3b0fb5.scope Unit: user@1002.service User Unit: app-org.kde.konsole-c7898390fcab48f4a33a7b08fc3b0fb5.scope Slice: user-1002.slice Owner UID: 1002 (santi) Boot ID: a7fa3af3286c470485bf9405b9833b2a Machine ID: 82ad6e578fd041e19a9ca05f32db1210 Hostname: mini Storage: /var/lib/systemd/coredump/core.plasmashell.1002.a7fa3af3286c470485bf9405b9833b2a.53482.162033218900.zst (present) Disk Size: 14.1M Message: Process 53482 (plasmashell) of user 1002 dumped core. Stack trace of thread 53482: #0 0x7f54c1a2b292 raise (libc.so.6 + 0x3d292) #1 0x7f54c1a148a4 abort (libc.so.6 + 0x268a4) #2 0x7f54c1e8f42d _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xb142d) #3 0x7f54bfd9b4d4 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x804d4) #4 0x7f54bfd9b6ea _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x806ea) #5 0x7f54bfda8ace _ZN15QtWaylandClient14QWaylandWindow10setVisibleEb.part.0 (libQt5WaylandClient.so.5 + 0x8dace) #6 0x7f54c24a2aab _ZN14QWindowPrivate10setVisibleEb (libQt5Gui.so.5 + 0x172aab) #7 0x55d8f59fb755 _ZN11ShellCorona20primaryOutputChangedEv (plasmashell + 0x44755) #8 0x7f54c208d4b0 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2af4b0) #9 0x7f54c248b606 _ZN15QGuiApplication20primaryScreenChangedEP7QScreen (libQt5Gui.so.5 + 0x15b606) #10 0x7f54c24bb9bf _ZN7QScreenD1Ev (libQt5Gui.so.5 + 0x18b9bf) #11 0x7f54c24bbc7d _ZN7QScreenD0Ev (libQt5Gui.so.5 + 0x18bc7d) #12 0x7f54c2478d0b _ZN22QWindowSystemInterface19handleScreenRemovedEP15QPlatformScreen (libQt5Gui.so.5 + 0x148d0b) #13 0x7f54bfd9e8c6 _ZN15QtWaylandClient15QWaylandDisplay22registry_global_removeEj (libQt5WaylandClient.so.5 + 0x838c6) #14 0x7f54c04a0c04 ffi_call_unix64 (libffi.so.6 + 0x6c04) #15 0x7f54c04a0107 ffi_call (libffi.so.6 + 0x6107) #16 0x7f54c1929d10 wl_closure_invoke.constprop.0 (libwayland-client.so.0 + 0x6d10) #17 0x7f54c192a42b dispatch_event.isra.0 (libwayland-client.so.0 + 0x742b) #18 0x7f54c192a61c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x761c) #19 0x7f54bfd9b6d3 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x806d3) #20 0x7f54c208d4fd _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2af4fd) #21 0x7f54c208fb3a _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2b1b3a) #22 0x7f54c20902d4 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2b22d4) #23 0x7f54c2ccbe73 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1ade73) #24 0x7f54c205cf48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x27ef48) #25 0x7f54c20aa17f _ZL28socketNotifierSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2cc17f) #26 0x7f54c05314cf g_main_context_dispatch (libglib-2.0.so.0 + 0x554cf) #27 0x7f54c05854e8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa94e8) #28 0x7f54c052ec03 g_main_context_iteration (libglib-2.0.so.0 + 0x52c03) #29 0x7f54c20a96f8 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2cb6f8) #30 0x7f54c205b9b2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x27d9b2) #31 0x7f54c2063544 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x285544) #32 0x55d8f59ddfd1 main (plasmashell + 0x26fd1) #33 0x7f54c1a15b75 __libc_start_main (libc.so.6 + 0x27b75) #34 0x55d8f59de3ee _start (plasmashell + 0x273ee) Stack trace of thread 53483: #0 0x7f54c1ae39ff __poll (libc.so.6 + 0xf59ff) #1 0x7f54c058547c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa947c)
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #27 from Santiago Cézar --- > I just tried to turn off my monitor and after this i successfully returned > back, only plasmashell is gone I've recently tried running Plasma on Wayland again and had exactly this behaviour > with plasma from master, on stable its still a crash probably I've installed Plasma 5.21.4 from Fedora 34 repositories -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #26 from Seqularise --- with plasma from master, on stable its still a crash probably -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #25 from Seqularise --- I just tried to turn off my monitor and after this i successfully returned back, only plasmashell is gone -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #24 from Vlad Zahorodnii --- (In reply to Argy M from comment #23) > Thread 1 (Thread 0x7ff9bc422940 (LWP 1486) "kwin_wayland"): > #0 0x7ff9c1b749d5 in raise () from /lib64/libc.so.6 > #1 0x7ff9c1b5d8a4 in abort () from /lib64/libc.so.6 > #2 0x7ff9c1b5d789 in __assert_fail_base.cold () from /lib64/libc.so.6 > #3 0x7ff9c1b6d026 in __assert_fail () from /lib64/libc.so.6 > #4 0x7ff9c1faf20f in epoxy_get_proc_address () from /lib64/libepoxy.so.0 > #5 0x7ff9c1f5c3aa in epoxy_glDeleteProgram_global_rewrite_ptr () from > /lib64/libepoxy.so.0 > #6 0x7ff9c1aee2e4 in KWin::ContrastEffect::~ContrastEffect() () from > /lib64/libkwin4_effect_builtins.so.1 > #7 0x7ff9c1aee3ad in KWin::ContrastEffect::~ContrastEffect() () from > /lib64/libkwin4_effect_builtins.so.1 > #8 0x7ff9c39c0dee in > KWin::EffectsHandlerImpl::destroyEffect(KWin::Effect*) () from > /lib64/libkwin.so.5 > #9 0x7ff9c39c1c6d in KWin::EffectsHandlerImpl::unloadEffect(QString > const&) () from /lib64/libkwin.so.5 Does libepoxy print anything related to missing OpenGL context? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Donovan Zimmerman changed: What|Removed |Added CC||s@zimmedon.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Piotr Piotrowski changed: What|Removed |Added CC||p...@poczta.onet.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Argyris M changed: What|Removed |Added CC||argy...@gmail.com --- Comment #23 from Argyris M --- I get the same issue, kwin crashing after the display shuts off due to inactivity. For whatever reason, the coredump from systemd-coredumpd gets truncated every time. I've obtained a stack trace by manually attaching gdb. Hope it's useful, stack traces are generally my nemesis. --- Operating System: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-201.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4910MQ CPU @ 2.90GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 --- [Detaching after fork from child process 2363] [Detaching after fork from child process 2491] Thread 1 "kwin_wayland" received signal SIGABRT, Aborted. 0x7ff9c1b749d5 in raise () from /lib64/libc.so.6 Thread 10 (Thread 0x7ff9919fb640 (LWP 1499) "kwin_wayland"): #0 0x7ff9c15826c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff9c1927cec in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7ff9c1927d1f in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7ff992ffd640 (LWP 1496) "QQmlThread"): #0 0x7ff9c1c2d80f in poll () from /lib64/libc.so.6 #1 0x7ff9bfd9a6f6 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7ff9bfd45d43 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff9c23196f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff9c22cb57b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff9c2130b67 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff9c0e435ec in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7ff9c2131df0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7ff99b8b9640 (LWP 1494) "kwin_wa:disk$3"): #0 0x7ff9c15826c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff99d86295b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7ff99d86241b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7ff993fff640 (LWP 1493) "kwin_wa:disk$2"): #0 0x7ff9c15826c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff99d86295b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7ff99d86241b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7ff99c0ba640 (LWP 1492) "kwin_wa:disk$1"): #0 0x7ff9c15826c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff99d86295b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7ff99d86241b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7ff99c8bb640 (LWP 1491) "kwin_wa:disk$0"): #0 0x7ff9c15826c2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff99d86295b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7ff99d86241b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff9c1c38903 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7ff9ad8d5640 (LWP 1489) "libinput-connec"): #0 0x7ff9c1c2d80f in poll () from /lib64/libc.so.6 #1 0x7ff9bfd9a6f6 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7ff9bfd45d43 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff9c23196f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff9c22cb57b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff9c2130b67 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff9c2131df0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7ff9c157c3f9 in start_thread () from /lib64/libpthread.so.0 #8
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Santiago Cézar changed: What|Removed |Added CC||santiagocezar2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED --- Comment #22 from Nate Graham --- Ah so there is. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #21 from Tavian Barnes --- (In reply to Nate Graham from comment #20) > Until we get better handling of this in Qt, the best we can do is debug why > the compositor crashed in the first place. So can you please get a backtrace > of the crash in kwin_wayland and then file a new bug report with it on kwin > | wayland-generic? Thanks! I posted one already in this thread, does it help? https://bugs.kde.org/show_bug.cgi?id=420160#c16 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #20 from Nate Graham --- #6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that the compositor crashed. Due to a Qt issue, when this happens, the app using it will crash too. KDE developers submitted a fix, but sadly it was not merged. See https://codereview.qt-project.org/c/qt/qtwayland/+/308984. Until we get better handling of this in Qt, the best we can do is debug why the compositor crashed in the first place. So can you please get a backtrace of the crash in kwin_wayland and then file a new bug report with it on kwin | wayland-generic? Thanks! You may be able to use the `coredumpctl` utility to retrieve the backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #19 from Patrick Lang --- I tried this again, still happening with updated kernel & KDE Framework. Would anyone be able to look at this if I took some core dumps? Operating System: Fedora 34 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-0.rc3.122.fc34.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4590T CPU @ 2.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Adarsha HD changed: What|Removed |Added CC||m...@adarshahd.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Seqularise changed: What|Removed |Added CC||seqular...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 ber...@codewiz.org changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Neros changed: What|Removed |Added CC||cont...@neros.fr -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #18 from Patrick Lang --- (In reply to Patrick Lang from comment #17) Operating System: Fedora 34 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-0.rc6.20201202git509a15421674.91.fc34.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4590T CPU @ 2.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Patrick Lang changed: What|Removed |Added CC||patrick.l...@hotmail.com --- Comment #17 from Patrick Lang --- I believe I'm hitting the same issue too on Fedora rawhide (34) with KDE Plasma. When I switch my KVM, which disconnects the monitor, it crashes. When I switch off the machine, I get a sequence like this showing USB & DP disconnection ``` Dec 07 22:06:50 xubuntu-itx-amd64 polkit-kde-authentication-agent-1[1525]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 kded5[1506]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 klauncher[1497]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 kwalletd5[1382]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 org_kde_powerdevil[1588]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 kdeconnectd[1548]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 DiscoverNotifier[1540]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 dolphin[1574]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 kactivitymanagerd[1567]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 baloorunner[2403]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 konsole[2412]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: trying to show an empty dialog Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: trying to show an empty dialog Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: Old primary output: QScreen(0x559ffceaaee0, name="DP-1") New primary output: QScreen(0x559ffe2eb5c0, name="") Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: trying to show an empty dialog Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: trying to show an empty dialog Dec 07 22:06:50 xubuntu-itx-amd64 plasmashell[1527]: The Wayland connection experienced a fatal error: Protocol error Dec 07 22:06:50 xubuntu-itx-amd64 kernel: usb 4-4.4: USB disconnect, device number 4 Dec 07 22:06:50 xubuntu-itx-amd64 kernel: usb 4-4.4.1: USB disconnect, device number 5 Dec 07 22:06:51 xubuntu-itx-amd64 kded5[1506]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. Dec 07 22:06:51 xubuntu-itx-amd64 pcscd[2187]: 40310639 ccid_usb.c:857:WriteUSB() write failed (3/14): -1 LIBUSB_ERROR_IO Dec 07 22:06:51 xubuntu-itx-amd64 pcscd[2187]: 0088 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 612 Dec 07 22:06:51 xubuntu-itx-amd64 pcscd[2187]: 0014 eventhandler.c:336:EHStatusHandlerThread() Error communicating to: Yubico YubiKey OTP+FIDO+CCID 00 00 Dec 07 22:06:51 xubuntu-itx-amd64 kernel: usb 3-4.4.1: clear tt 1 (1112) error -71 Dec 07
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160
--- Comment #16 from Tavian Barnes ---
Reproduced it. First I get this on the console (typed manually, hopefully no
mistakes):
qt.qpa.wayland: Ignoring unexpected wl_surface.leave received for output with
id: 44 screen name: "DP-1" screen model: "DP-1-DELL U2718Q/4K8X703G06LL" This
is most likely a bug in the compositor.
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kwin_wayland: ../libepoxy/src/dispatch_common.c:863: epoxy_get_proc_address:
Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
The Wayland connection broke. Did the Wayland compositor die?
Here's the backtrace:
#0 0x7f7fe8856615 in raise () at /usr/lib/libc.so.6
#1 0x7f7fe883f912 in abort () at /usr/lib/libc.so.6
#2 0x7f7fe883f747 in _nl_load_domain.cold () at /usr/lib/libc.so.6
#3 0x7f7fe884ebf6 in () at /usr/lib/libc.so.6
#4 0x7f7fe8c7fea8 in () at /usr/lib/libepoxy.so.0
#5 0x7f7fe8c351aa in () at /usr/lib/libepoxy.so.0
#6 0x7f7fe18ac8f9 in
QScopedPointerDeleter::cleanup(KWin::GLShader*)
(pointer=0x556c47f8e4c0) at /usr/include/qt/QtCore/qscopedpointer.h:52
oldD = 0x556c47f8e4c0
#7 QScopedPointerDeleter::cleanup(KWin::GLShader*)
(pointer=0x556c47f8e4c0)
at /usr/include/qt/QtCore/qscopedpointer.h:52
oldD = 0x556c47f8e4c0
#8 QScopedPointer
>::~QScopedPointer()
(this=0x556c47fb95c8, __in_chrg=) at
/usr/include/qt/QtCore/qscopedpointer.h:107
oldD = 0x556c47f8e4c0
#9 KWin::LanczosFilter::~LanczosFilter() (this=0x556c47fb95a0,
__in_chrg=)
at /usr/src/debug/kwin-5.20.3/plugins/scenes/opengl/lanczosfilter.cpp:47
#10 0x7f7fe18ac949 in KWin::LanczosFilter::~LanczosFilter()
(this=0x556c47fb95a0, __in_chrg=)
at /usr/src/debug/kwin-5.20.3/plugins/scenes/opengl/lanczosfilter.cpp:51
#11 0x7f7fe18af134 in operator() (__closure=0x556c480aba10)
at /usr/src/debug/kwin-5.20.3/plugins/scenes/opengl/scene_opengl.cpp:1070
this = 0x556c46c2aef0
#12 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, const
QRegion&, KWin::WindowPaintData&):: >::call
(arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#13
QtPrivate::Functor,
0>::call, void> (arg=, f=...)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#14
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x556c480aba00, r=,
a=, ret=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#15 0x7f7fe9006dd6 in () at /usr/lib/libQt5Core.so.5
#16 0x7f7fe9006dd6 in () at /usr/lib/libQt5Core.so.5
#17 0x7f7fea92fd89 in KWin::DrmBackend::updateOutputs()
(this=0x556c46b60e60)
at /usr/src/debug/kwin-5.20.3/plugins/platforms/drm/drm_backend.cpp:520
resources = {d = 0x556c46b97c00}
oldConnectors = {d = 0x556c47ccab30}
oldCrtcs = {d = 0x556c46b97770}
connectedOutputs = {d = 0x556c48354530}
pendingConnectors = {d = 0x556c482cbc50}
removedOutputs = {d = 0x7f7fe90b9940 }
it =
#18 0x7f7fea930e51 in operator() (__closure=0x556c46c2cea0)
at /usr/src/debug/kwin-5.20.3/plugins/platforms/drm/drm_backend.cpp:349
device = std::unique_ptr = {get() = 0x556c46c1dd40}
this = 0x556c46b60e60
#19 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWin::DrmBackend::openDrm():: >::call (arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#20 QtPrivate::Functor,
0>::call, void>
(arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#21 QtPrivate::QFunctorSlotObject, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *)
(which=, this_=0x556c46c2ce90, r=,
a=, ret=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#22 0x7f7fe9006dd6 in () at /usr/lib/libQt5Core.so.5
#23 0x7f7fe900a340 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#24 0x7f7fe900ab4d in QSocketNotifier::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#25 0x7f7fe9a99752 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib/libQt5Widgets.so.5
#26 0x7f7fe8fcfa7a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib/libQt5Core.so.5
#27 0x7f7fe90259d4 in
QEventDispatcherUNIXPrivate::activateSocketNotifiers() ()
at /usr/lib/libQt5Core.so.5
#28 0x7f7fe9025e55 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#29 0x7f7fe321493e in
QUnixEventDispatcherQPA::processEvents(QFlags)
() at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so
#30 0x7f7fe8fce3fc in
QEventLoop::exec(QFlags) ()
at /usr/lib/libQt5Core.so.5
#31 0x7f7fe8fd6894 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#32 0x556c45fd984e in main(int, char**) (argc=,
argv=)
at
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #15 from Tavian Barnes --- I haven't reproduced it yet with debug symbols, but I did some additional debugging on the core dump from the last crash. It looks like the crash is this assertion failure in libepoxy: "Couldn't find current GLX or EGL context." https://github.com/anholt/libepoxy/blob/1.5.4/src/dispatch_common.c#L863 The proc being looked up is glDeleteProgram. The only call to glDeleteProgram() I see in kwin is in ~GLShader(): https://github.com/KDE/kwin/blob/v5.20.3/libkwineffects/kwinglutils.cpp#L159 I'm guessing the screen/display is disappearing when it turns off/sleeps, and when stuff gets torn down the destructors try to touch a GL context that isn't there any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #14 from Mircea Kitsune --- (In reply to Tavian Barnes from comment #13) Thanks for the helpful information, hopefully it can aid in solving this sooner! As my system is for desktop use I can't easily experiment with debugging the session or installing debug compiled versions of KDE components. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #13 from Tavian Barnes --- Here's a stack trace without debug symbols. I'm rebuilding with debug info now. #0 0x7f73c69cb615 in raise () at /usr/lib/libc.so.6 #1 0x7f73c69b4912 in abort () at /usr/lib/libc.so.6 #2 0x7f73c69b4747 in _nl_load_domain.cold () at /usr/lib/libc.so.6 #3 0x7f73c69c3bf6 in () at /usr/lib/libc.so.6 #4 0x7f73c6df4ea8 in () at /usr/lib/libepoxy.so.0 #5 0x7f73c6daa1aa in () at /usr/lib/libepoxy.so.0 #6 0x7f73bf7528f9 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #7 0x7f73bf752949 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f73bf755134 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #9 0x7f73c717bdd6 in () at /usr/lib/libQt5Core.so.5 #10 0x7f73c717bdd6 in () at /usr/lib/libQt5Core.so.5 #11 0x7f73bffb8d89 in KWin::DrmBackend::updateOutputs() () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #12 0x7f73bffb9e51 in () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #13 0x7f73c717bdd6 in () at /usr/lib/libQt5Core.so.5 #14 0x7f73c717f340 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #15 0x7f73c717fb4d in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f73c7c0e752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f73c7144a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7f73c719a9d4 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #19 0x7f73c719ae55 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f73c138993e in () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #21 0x7f73c71433fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #22 0x7f73c714b894 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #23 0x55941086b84e in () #24 0x7f73c69b6152 in __libc_start_main () at /usr/lib/libc.so.6 #25 0x55941086c0de in _start () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Tavian Barnes changed: What|Removed |Added CC||taviana...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Martin Insulander changed: What|Removed |Added CC||mar...@insulander.info --- Comment #12 from Martin Insulander --- This sounds very similar to what I experience. The computer is brand-new, so I have not yet figured out any details. Sometimes Konqi crashes ~20 times, sometimes other applications and sometimes the session goes down. It may depend on if I have an external monitor connected or if I put it to sleep manually. i will keep close look at it. I saw that Rainer also is running AMD if that could be a common denominator. Operating System: Debian Testing (KDE from Preining) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.0-3-amd64 OS Type: 64-bit Processors: 8 × AMD Ryzen 7 3700U Memory: 13,7 GiB of RAM Graphics Processor: AMD Radeon Vega 10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added Component|general |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Nagy Tamás changed: What|Removed |Added CC||tbondvag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #11 from Mircea Kitsune --- Still an issue in Plasma 5.20.0 / Framework 5.75.0. Only difference now is that the session as a whole no longer crashes when the monitor enters standby: Some other system process(es) do(es) causing the monitor to immediately come out of standby once more. As it does I'm met with a mangled desktop I need to reboot out of, with desktop effects no longer working among other visual glitches. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Rainer Finke changed: What|Removed |Added Version|5.18.4 |5.20.0 CC||rai...@finke.cc --- Comment #10 from Rainer Finke --- I've seen as well several crashes of Kwin. Mostly when my system goes to standby, my monitor is turning itself to sleep then after 20min. When my system wakes up, I get a black screen with a cursor. I will try to get a backtrace. Operating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.0-arch1-1 OS Type: 64-bit Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon VII -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 David Murray changed: What|Removed |Added CC||david...@davidmurray.name -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #9 from Vlad Zahorodnii --- You could also ssh from another computer and attach gdb or lldb to the running instance of kwin_wayland. gdb --pid `pidof kwin_wayland` 2>&1 | tee kwin.gdb from https://community.kde.org/KWin/Debugging -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #8 from Mircea Kitsune --- Clarification: I get the exact same behavior when using "startplasma-wayland", I only see a splash screen briefly then any session I have active crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Mircea Kitsune changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Assignee|kwin-bugs-n...@kde.org |sonichedgehog_hyperblast00@ ||yahoo.com Ever confirmed|1 |0 --- Comment #7 from Mircea Kitsune --- Created attachment 132132 --> https://bugs.kde.org/attachment.cgi?id=132132=edit kwin_wayland --exit-with-session konsole I followed that tutorial but was unable to successfully run the debug session. Running "kwin_wayland" from a console caused a new session window to appear briefly, then my original session (X11) crashed to the login screen and I had to reboot. Running it from a different runlevel (Control + Alt + F1) resulted in a black screen in that run level. I was able to run "kwin_wayland --exit-with-session konsole" which also resulted in a black window but didn't crash... I attached the console output of that in case it explains what's not working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 David Edmundson changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from David Edmundson --- If kwin is crashing, then it's a kwin bug. Moving there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 David Edmundson changed: What|Removed |Added Component|general |general Product|Powerdevil |kwin Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
