SUMMARY Trying to logging to a wayland session ends up with a segfault that returns the user to sddm logging screen. STEPS TO REPRODUCE 1. From sddm select plasma wayland session. 2. Log in. OBSERVED RESULT The screen will go black for a few seconds and throw you back to sddm. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse Tumbleweed + kde unstable repositories KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Backtrace: #0 [34m0x00007f35691b6c30[m in [33mKWayland::Server::OutputDeviceInterface::d_func() const[m (this=0x0)[m [m at [32m/usr/src/debug/kwayland-5.62.0git.20191006T093754~e422755-ku.7.1.x86_64/src/server/outputdevice_interface.cpp[m:632 #1 [34m0x00007f35691b6c49[m in [33mKWayland::Server::OutputDeviceInterface::pixelSize() const[m (this=<optimized out>)[m [m at [32m/usr/src/debug/kwayland-5.62.0git.20191006T093754~e422755-ku.7.1.x86_64/src/server/outputdevice_interface.cpp[m:161 #2 [34m0x00007f35694e6951[m in [33mKWin::AbstractWaylandOutput::pixelSize() const[m (this=0x55c0f3ce7330)[m [m at [32m/usr/include/c++/9/bits/atomic_base.h[m:413 #3 [34m0x00007f35613e59d1[m in [33mKWin::DrmCrtc::blank()[m (this=0x55c0f3c62b40)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/plugins/platforms/drm/drm_object_crtc.cpp[m:95 #4 [34m0x00007f35613ed811[m in [33mKWin::DrmOutput::init(_drmModeConnector*)[m (this=0x55c0f3ce7330, connector=connector@entry=0x55c0f3c5bdf0)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/plugins/platforms/drm/drm_output.cpp[m:255 #5 [34m0x00007f35613df019[m in [33mKWin::DrmBackend::updateOutputs()[m (this=this@entry=0x55c0f3b65b80)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/plugins/platforms/drm/drm_backend.cpp[m:480 #6 [34m0x00007f35613e065d[m in [33mKWin::DrmBackend::openDrm()[m (this=0x55c0f3b65b80)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/plugins/platforms/drm/drm_backend.cpp[m:350 #7 [34m0x00007f3568618638[m in [33mQtPrivate::QSlotObjectBase::call(QObject*, void**)[m[m [m (a=0x7ffcf514d230, r=0x55c0f3b65b80, this=0x55c0f3be6060) at [32m../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h[m:394 #8 [34m0x00007f3568618638[m in [33mQMetaObject::activate(QObject*, int, int, void**)[m[m [m (sender=0x55c0f3b7b030, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>)[m [m at [32mkernel/qobject.cpp[m:3789 #9 [34m0x00007f35694bd032[m in [33mKWin::LogindIntegration::hasSessionControlChanged(bool)[m (this=<optimized out>, _t1=<optimized out>, [m [m_t1@entry=true)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/build/kwin_autogen/EWIEGA46WW/moc_logind.cpp[m:193 #10 [34m0x00007f3569598720[m in [33mKWin::LogindIntegration::<lambda(QDBusPendingCallWatcher*)>::operator()[m[m [m (__closure=0x55c0f3bac7e0, self=<optimized out>)[m [m at [32m/usr/src/debug/kwin5-5.17.80git.20191002T205147~81c733067-ku.105.4.x86_64/logind.cpp[m:341 #11 [34m0x00007f3569598720[m in [33mQtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QDBusPendingCallWatcher*>, void, KWin::LogindIntegration::takeControl()::<lambda(QDBusPendingCallWatcher*)> >::call[m (arg=<optimized out>, f=...)[m [m at [32m/usr/include/qt5/QtCore/qobjectdefs_impl.h[m:146 #12 [34m0x00007f3569598720[m in [33mQtPrivate::Functor<KWin::LogindIntegration::takeControl()::<lambda(QDBusPendingCallWatcher*)>, 1>::call<QtPrivate::List<QDBusPendingCallWatcher*>, void>[m (arg=<optimized out>, f=...) at [32m/usr/include/qt5/QtCore/qobjectdefs_impl.h[m:256 #13 [34m0x00007f3569598720[m in [33mQtPrivate::QFunctorSlotObject<KWin::LogindIntegration::takeControl()::<lambda(QDBusPendingCallWatcher*)>, 1, QtPrivate::List<QDBusPendingCallWatcher*>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)[m[m [m (which=<optimized out>, this_=0x55c0f3bac7d0, r=<optimized out>, a=<optimized out>, ret=<optimized out>)[m [m at [32m/usr/include/qt5/QtCore/qobjectdefs_impl.h[m:439 #14 [34m0x00007f3568618638[m in [33mQtPrivate::QSlotObjectBase::call(QObject*, void**)[m[m [m (a=0x7ffcf514d410, r=0x55c0f3b7b030, this=0x55c0f3bac7d0) at [32m../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h[m:394 #15 [34m0x00007f3568618638[m in [33mQMetaObject::activate(QObject*, int, int, void**)[m[m [m (sender=0x55c0f3bfd4f0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>)[m [m at [32mkernel/qobject.cpp[m:3789 #16 [34m0x00007f35690d993f[m in [33mQDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*)[m (this=<optimized out>, _t1=<optimized out>)[m [m at [32m.moc/moc_qdbuspendingcall.cpp[m:158 #17 [34m0x00007f35690d9a40[m in [33mQDBusPendingCallWatcherPrivate::_q_finished()[m (this=<optimized out>) at [32mqdbuspendingcall.cpp[m:494 #18 [34m0x00007f35690d9a40[m in [33mQDBusPendingCallWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)[m[m [m (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at [32m.moc/moc_qdbuspendingcall.cpp[m:86 #19 [34m0x00007f3568618eea[m in [33mQObject::event(QEvent*)[m (this=0x55c0f3bfd4f0, e=<optimized out>) at [32mkernel/qobject.cpp[m:1260 #20 [34m0x00007f3568a31c62[m in [33mQApplicationPrivate::notify_helper(QObject*, QEvent*)[m[m [m (this=this@entry=0x55c0f3b1ba50, receiver=receiver@entry=0x55c0f3bfd4f0, e=e@entry=0x55c0f3b9ad50)[m [m at [32mkernel/qapplication.cpp[m:3703 #21 [34m0x00007f3568a3b1e0[m in [33mQApplication::notify(QObject*, QEvent*)[m (this=0x7ffcf514db90, receiver=0x55c0f3bfd4f0, e=0x55c0f3b9ad50)[m [m at [32mkernel/qapplication.cpp[m:3449 #22 [34m0x00007f35685ed562[m in [33mQCoreApplication::notifyInternal2(QObject*, QEvent*)[m (receiver=0x55c0f3bfd4f0, event=0x55c0f3b9ad50)[m [m at [32m../../include/QtCore/../../src/corelib/kernel/qobject.h[m:143 #23 [34m0x00007f35685f01f8[m in [33mQCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)[m[m [m (receiver=0x0, event_type=0, data=0x55c0f3af6fc0) at [32mkernel/qcoreapplication.cpp[m:1840 #24 [34m0x00007f3568640da3[m in [33mQEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)[m (this=0x55c0f3b48290, flags=...)[m [m at [32mkernel/qeventdispatcher_unix.cpp[m:466 #25 [34m0x00007f35624a13fd[m in [33mQUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)[m[m [m (this=<optimized out>, flags=...) at [32mqunixeventdispatcher.cpp[m:63 #26 [34m0x00007f35685ec0cb[m in [33mQEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)[m (this=this@entry=0x7ffcf514d940, flags=..., [m [mflags@entry=...) at [32m../../include/QtCore/../../src/corelib/global/qflags.h[m:140 #27 [34m0x00007f35685f3d32[m in [33mQCoreApplication::exec()[m () at [32m../../include/QtCore/../../src/corelib/global/qflags.h[m:120 #28 [34m0x000055c0f1d4a405[m in [33mmain(int, char**)[m (argc=<optimized out>, argv=<optimized out>)[m [m [m05147~81c733067-ku.105.4.x86_64/main_wayland.cpp[m:676
I guess you're not using atomic mode setting. That's an edge case nowadays. Did you set the variable at one point or is it just not supported on your hardware? Would you be able to compile KWin to test out some patches? I currently can't really test it but in general the size data must be either available to the legacy interface early enough or we postpone the first blank.
The variable I mentioned is KWIN_DRM_NO_AMS. If this variable is NOT set atomic mode setting is used by KWin if the hardware supports it, otherwise it falls back to legacy mode setting.
Created attachment 123110 [details] qdbus org.kde.KWin /KWin supportInformation (In reply to Roman Gilg from comment #2) > The variable I mentioned is KWIN_DRM_NO_AMS. If this variable is NOT set > atomic mode setting is used by KWin if the hardware supports it, otherwise > it falls back to legacy mode setting. I don't have it set. Well it could be the hardware lacking, by technology years its fairly old already. It's an IGP with integrated radeon HD 3000, check the attatchment. > Would you be able to compile KWin to test out some patches? I am willing, yes. Able? Working on it, never compile kwin before. POint me to the patches. I am fallowing: https://community.kde.org/KWin/Building
I've tried with 2 more recent video cards, HD 7700 and R9 280 both using amdgpu driver instead of radeon. Same result in both cases.
Ralated/duplicated https://bugs.kde.org/show_bug.cgi?id=412152
Another test with a Current card RX 560. With this one i can logging into a wayland session but not into a FullWayland one. I get thrown into the logging screen as before but this time there are no logs, dumps or dmesg messages indicating what went wrong.
(In reply to Roman Gilg from comment #1) > Would you be able to compile KWin to test out some patches? If this bugs is https://bugs.kde.org/show_bug.cgi?id=412152 related, so my system is also affected. I've build kwin from git (r17395.10ace126b) and this bug still exists.
Can confirm that this happens with both of these graphics cards: 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] Running: Arch linux current. linux 5.3.6-arch1-1-ARCH with 'radeon' driver. mesa 19.2.1. qt5 5.13.1 kwin 5.17.0 KF5WaylandServer 5.63.0
I reproduce this on my desktop with a RX 560. I build from sources Plasma+KWin, I can help here.
Same issue on my 2015 macbook pro. segfault at 10 ip / error 4 in libKF5WaylandServer.so.5.63.0 device: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] (rev 83) and I'm using the AMDGPU driver. It works on my other laptop (also using AMDGPU) and on my desktop running a Radeon VII, so I don't believe it's a driver issue.
Before big update from KDE neon 5.16.5 to 5.17 logging to Wayland session worked fine but now freezes my computer (black screen, PC is not responsible), sometimes throws back to SDDM login screen and then "dmesg" is telling this: Oct 17 18:13:40 KDE kernel: [ 631.303567] show_signal_msg: 15 callbacks suppressed Oct 17 18:13:40 KDE kernel: [ 631.303570] kwin_wayland[5827]: segfault at 10 ip 00007f5199bff110 sp 00007fff9aa02618 error 4 in libKF5WaylandServer.so.5.63.0[7f5199b84000+fa000] Oct 17 18:13:40 KDE kernel: [ 631.303579] Code: 00 00 f3 c3 66 0f 1f 44 00 00 48 85 f6 74 0b 48 89 f7 e9 d3 94 fe ff 0f 1f 00 f3 c3 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 47 10 c3 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 e7 -- KDE neon 5.17 -- Plasma: 5.17.0 Frameworks: 5.63.0 Qt: 5.13.1 Kernel: 5.0.0-29-generic Arch: 64-bit Card: Advanced Micro Devices [AMD/ATI] RV530 [Radeon X1600 XT/X1650 GTO] Display Server: X.Org 1.19.6 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
Same problem here: Opensuse Tumbleweed snapshot 20191014 --- inxi -G Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics driver: i915 v: kernel Display: wayland server: X.Org 1.20.5 driver: intel resolution: 1440x900~60Hz, 2560x1440~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.1.7 --- Error: --- Oct 19 15:04:06 x301.example.com kernel: kwin_wayland[2549]: segfault at 10 ip 00007fb205ffbc30 sp 00007ffe619af818 error 4 in libKF5WaylandServer.so.5.63.0[7fb205fd6000+60000] Oct 19 15:04:06 x301.example.com 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 Oct 19 15:04:06 x301.example.com systemd[1]: Created slice system-systemd\x2dcoredump.slice. Oct 19 15:04:06 x301.example.com systemd[1]: Started Process Core Dump (PID 2638/UID 0). Oct 19 15:04:07 x301.example.com systemd-coredump[2639]: Process 2549 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 2549: #0 0x00007fb205ffbc30 _ZNK8KWayland6Server21OutputDeviceInterface6d_funcEv (libKF5WaylandServer.so.5) #1 0x00007fb205ffbc49 _ZNK8KWayland6Server21OutputDeviceInterface9pixelSizeEv (libKF5WaylandServer.so.5) #2 0x00007fb206308761 _ZNK4KWin21AbstractWaylandOutput9pixelSizeEv (libkwin.so.5) #3 0x00007fb1fe423991 n/a (KWinWaylandDrmBackend.so) #4 0x00007fb1fe42b451 _ZN4KWin9DrmOutput4initEP17_drmModeConnector (KWinWaylandDrmBackend.so) #5 0x00007fb1fe41cfd9 _ZN4KWin10DrmBackend13updateOutputsEv (KWinWaylandDrmBackend.so) #6 0x00007fb1fe41e61d _ZN4KWin10DrmBackend7openDrmEv (KWinWaylandDrmBackend.so) #7 0x00007fb205476638 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #8 0x00007fb2062df052 _ZN4KWin17LogindIntegration24hasSessionControlChangedEb (libkwin.so.5) #9 0x00007fb2063c6730 n/a (libkwin.so.5) #10 0x00007fb205476638 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #11 0x00007fb205f2993f _ZN23QDBusPendingCallWatcher8finishedEPS_ (libQt5DBus.so.5) #12 0x00007fb205f29a40 n/a (libQt5DBus.so.5) #13 0x00007fb205476eea _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #14 0x00007fb20588cc62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #15 0x00007fb2058961e0 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #16 0x00007fb20544b572 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #17 0x00007fb20544e208 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #18 0x00007fb20549edb3 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x00007fb1ff4776fd n/a (KWinQpaPlugin.so) #20 0x00007fb20544a0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #21 0x00007fb205451d42 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #22 0x000056546baec415 n/a (kwin_wayland) #23 0x00007fb204e06e0b __libc_start_main (libc.so.6) #24 0x000056546baec85a _start (kwin_wayland) Stack trace of thread 2605: #0 0x00007fb204ed4bdf __poll (libc.so.6) #1 0x00007fb2029153ce n/a (libglib-2.0.so.0) #2 0x00007fb20291549f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb2054a1981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20544a0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb205282021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb205ec74f6 n/a (libQt5DBus.so.5) #7 0x00007fb2052831a2 n/a (libQt5Core.so.5) #8 0x00007fb205f53f2a start_thread (libpthread.so.0) #9 0x00007fb204edf4af __clone (libc.so.6) Stack trace of thread 2614: #0 0x00007fb204ed4bdf __poll (libc.so.6) #1 0x00007fb2029153ce n/a (libglib-2.0.so.0) #2 0x00007fb20291549f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb2054a199b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20544a0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb205282021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb2052831a2 n/a (libQt5Core.so.5) #7 0x00007fb205f53f2a start_thread (libpthread.so.0) #8 0x00007fb204edf4af __clone (libc.so.6) Stack trace of thread 2611: #0 0x00007fb204ed4bdf __poll (libc.so.6) #1 0x00007fb2029153ce n/a (libglib-2.0.so.0) #2 0x00007fb20291549f g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb2054a1981 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20544a0db _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb205282021 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb2052831a2 n/a (libQt5Core.so.5) #7 0x00007fb205f53f2a start_thread (libpthread.so.0) #8 0x00007fb204edf4af __clone (libc.so.6) Oct 19 15:04:07 x301.example.com systemd[1]: systemd-coredump@0-2638-0.service: Succeeded. ---
There is a patch now at: https://phabricator.kde.org/D24829 I plan to merge it for 5.17.1 released today. But it would be great if someone experiencing this issue and with a KWin compile setup can test the patch before that.
(In reply to Roman Gilg from comment #13) > There is a patch now at: https://phabricator.kde.org/D24829 > > I plan to merge it for 5.17.1 released today. But it would be great if > someone experiencing this issue and with a KWin compile setup can test the > patch before that. Done, Working! I can log into a wayland/full wayland sessions now using the old amd igpu. I could not compile it while having mesa 19.3 packages installed though. Cmake complained with : Failed to find "GL/gl.h" in "/usr/include/libdrm".
Git commit 0d67a0b48a500b615ff4af7456b1461a38090e48 by Roman Gilg. Committed on 22/10/2019 at 09:28. Pushed by romangilg into branch 'Plasma/5.17'. Fix non-atomic output init Summary: The initial blank needs to happen after the output device has been initialized to get the current mode size. Also we can't assert in legacy mode on the page flip pending since a page flip can also be the result of a CRTC blank using a different. FIXED-IN: 5.17.1 Test Plan: Full Plasma session Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: zzag, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D24829 M +9 -3 plugins/platforms/drm/drm_output.cpp https://commits.kde.org/kwin/0d67a0b48a500b615ff4af7456b1461a38090e48
did this patch make it into 5.17.1 or does it need to be manually applied? I just upgraded and still have the same issue.
Scratch that, although most Arch packages are 5.17.1, it looks like kwin 5.17.1 hasn't been released yet.
Should be released now.
KDE neon updated from 5.17 to 5.17.1 and logging to a Wayland session is working again - thanks. But there is another issue with killed keyboard & mouse after resuming from sleep, like this https://forums.opensuse.org/showthread.php/530065-KDE-Plasma-on-Wayland-no-mouse-and-keyboard-after-resume - but this is a case for another bug report...