Summary: | Plasma 5.17 reports crash after login into wayland session | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | joern477 |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | fabian, mitchell, plasma-bugs, w.pelser |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.17.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
joern477
2019-10-19 11:41:00 UTC
Created attachment 123347 [details]
New crash information added by DrKonqi
plasmashell (5.17.0) using Qt 5.13.1
- What I was doing when the application crashed:
Login to wayland session
- Custom settings of the application:
Nvidia PC, using Kwin's EGLStreams support.
-- Backtrace (Reduced):
#6 0x00007f10e5e56a52 in () at /usr/lib/libnvidia-egl-wayland.so.1
#7 0x00007f10ecfd6183 in wl_egl_window_destroy () at /usr/lib/libwayland-egl.so.1
#8 0x00007f10e657188b in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so
#9 0x00007f10f2728aac in QWindowPrivate::setVisible(bool) () at /usr/lib/libQt5Gui.so.5
#10 0x00007f10f2727ed9 in QWindowPrivate::destroy() () at /usr/lib/libQt5Gui.so.5
Yesterday I reported a similar bug to openSUSE. https://bugzilla.suse.com/show_bug.cgi?id=1154535, sddm cant start wayland. maybe it is the same problem. I was asked to report it to bugs.kde.org. OS: openSUSE-Tumbleweed current Plasma-Version 5.17 QT-Version 5.13.1 The problems began with the latest updates of plasma on 2019-10-16 This is the text of the description: Sddm can start only x-session Blackcreen when sddm tries to start wayland or fullwayland. Reboot necessary. Systemdjounal shows: kernel kwin_wayland[6442]: segfault at 10 ip 00007f4adc4c0c30 sp 00007ffe7192ff08 error 4 in libKF5WaylandServer.so.5.63.0[7f4adc49b000+60000] See attachment systemd backtrace.txt I tried everything, but could not repair this. There are a lot of customizations maybe there could be a connection. When I start an x-session and execute in a terminal: env GDK_BACKEND=wayland QT_QPA_PLATFORM=wayland dbus-run-session /usr/bin/startplasma-wayland wayland is starting. Attachment in full text: 19.10.19 10:14 systemd-logind New session 6 of user walther. 19.10.19 10:14 systemd Started Session 6 of user walther. 19.10.19 10:14 sddm-helper pam_unix(sddm:session): session opened for user walther(uid=1000) by (uid=0) 19.10.19 10:14 sddm-helper Starting: "/usr/share/sddm/scripts/wayland-session env GDK_BACKEND=wayland QT_QPA_PLATFORM=wayland-egl dbus-run-session /usr/bin/startplasma-wayland" 19.10.19 10:14 sddm Session started 19.10.19 10:14 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.135' (uid=1000 pid=6437 comm="/usr/bin/startplasma-wayland ") 19.10.19 10:14 systemd Starting Locale Service... 19.10.19 10:14 dbus-daemon [system] Successfully activated service 'org.freedesktop.locale1' 19.10.19 10:14 systemd Started Locale Service. 19.10.19 10:14 kernel show_signal_msg: 40 callbacks suppressed 19.10.19 10:14 kernel kwin_wayland[6442]: segfault at 10 ip 00007f4adc4c0c30 sp 00007ffe7192ff08 error 4 in libKF5WaylandServer.so.5.63.0[7f4adc49b000+60000] 19.10.19 10:14 kernel Code: 00 00 c3 0f 1f 80 00 00 00 00 48 85 f6 74 0b 48 89 f7 e9 33 a9 fd ff 0f 1f 00 c3 90 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 <48> 8b 47 10 c3 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 e7 19.10.19 10:14 systemd Created slice system-systemd\x2dcoredump.slice. 19.10.19 10:14 systemd Started Process Core Dump (PID 6446/UID 0). 19.10.19 10:14 sddm-helper [PAM] Closing session 19.10.19 10:14 systemd-logind Failed to restore VT, ignoring: Input/output error 19.10.19 10:14 sddm-helper pam_unix(sddm:session): session closed for user walther 19.10.19 10:14 sddm-helper [PAM] Ended. 19.10.19 10:14 sddm Auth: sddm-helper exited successfully 19.10.19 10:14 sddm Greeter stopping... 19.10.19 10:14 sddm Socket server stopping... 19.10.19 10:14 sddm Socket server stopped. 19.10.19 10:14 sddm Display server stopping... 19.10.19 10:14 sddm-greeter The X11 connection broke: I/O error (code 1) 19.10.19 10:14 sddm-helper [PAM] Closing session 19.10.19 10:14 systemd-coredump Process 6442 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 6442: #0 0x00007f4adc4c0c30 _ZNK8KWayland6Server21OutputDeviceInterface6d_funcEv (libKF5WaylandServer.so.5) #1 0x00007f4adc4c0c49 _ZNK8KWayland6Server21OutputDeviceInterface9pixelSizeEv (libKF5WaylandServer.so.5) #2 0x00007f4adc7cd761 _ZNK4KWin21AbstractWaylandOutput9pixelSizeEv (libkwin.so.5) #3 0x00007f4ad4845991 n/a (KWinWaylandDrmBackend.so) #4 0x00007f4ad484d451 _ZN4KWin9DrmOutput4initEP17_drmModeConnector (KWinWaylandDrmBackend.so) #5 0x00007f4ad483efd9 _ZN4KWin10DrmBackend13updateOutputsEv (KWinWaylandDrmBackend.so) #6 0x00007f4ad484061d _ZN4KWin10DrmBackend7openDrmEv (KWinWaylandDrmBackend.so) #7 0x00007f4adb93b638 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #8 0x00007f4adc7a4052 _ZN4KWin17LogindIntegration24hasSessionControlChangedEb (libkwin.so.5) #9 0x00007f4adc88b730 n/a (libkwin.so.5) #10 0x00007f4adb93b638 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #11 0x00007f4adc3ee93f _ZN23QDBusPendingCallWatcher8finishedEPS_ (libQt5DBus.so.5) #12 0x00007f4adc3eea40 n/a (libQt5DBus.so.5) #13 0x00007f4adb93beea _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #14 0x00007f4adbd51c62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #15 0x00007f4adbd5b1e0 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #16 0x00007f4adb910572 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #17 0x00007f4adb913208 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #18 0x00007f4adb963db3 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x00007f4ad593b6fd n/a (KWinQpaPlugin.so) #20 0x00007f4adb90f0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #21 0x00007f4adb916d42 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #22 0x0000555b77330415 n/a (kwin_wayland) #23 0x00007f4adb2cbe0b __libc_start_main (libc.so.6) #24 0x0000555b7733085a _start (kwin_wayland) Stack trace of thread 6443: #0 0x00007f4adb399bdf __poll (libc.so.6) #1 0x00007f4ad8dda3ce n/a (libglib-2.0.so.0) #2 0x00007f4ad8dda49f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f4adb966981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f4adb90f0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f4adb747021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f4adc38c4f6 n/a (libQt5DBus.so.5) #7 0x00007f4adb7481a2 n/a (libQt5Core.so.5) #8 0x00007f4adc418f2a start_thread (libpthread.so.0) #9 0x00007f4adb3a44af __clone (libc.so.6) Stack trace of thread 6445: #0 0x00007f4adb399bdf __poll (libc.so.6) #1 0x00007f4ad8dda3ce n/a (libglib-2.0.so.0) #2 0x00007f4ad8dda49f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f4adb966981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f4adb90f0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f4adb747021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f4adb7481a2 n/a (libQt5Core.so.5) #7 0x00007f4adc418f2a start_thread (libpthread.so.0) #8 0x00007f4adb3a44af __clone (libc.so.6) Stack trace of thread 6444: #0 0x00007f4adb399bdf __poll (libc.so.6) #1 0x00007f4ad8dda3ce n/a (libglib-2.0.so.0) #2 0x00007f4ad8dda49f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f4adb966981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f4adb90f0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f4adb747021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f4adb7481a2 n/a (libQt5Core.so.5) #7 0x00007f4adc418f2a start_thread (libpthread.so.0) #8 0x00007f4adb3a44af __clone (libc.so.6) It seems, that with Kwin 5.17.1 my problem is solved. Sddm can start wayland again. For me it also seems to be solved with Plasma 5.17.1 on KDE Neon user. Tested several login / logouts without any crash reported. Since Plasma 5.17 I can finally use wayland session as daily driver with dual Monitor setup :-) Thank you all for the amazing work! fixed with Plasma 5.17.1 |