[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #24 from Martin Flöser --- (In reply to Shmerl from comment #23) > It is still a KWin bug though, since the session shoulnd't be crashing when > there are no outputs found (which is the case here for a split moment caused > by amdgpu bug above). No, this is working as intended. KWin exits gracefully as on the DRM platform we require screens to be present. KWin cannot start up without screens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #23 from Shmerl --- It is still a KWin bug though, since the session shoulnd't be crashing when there are no outputs found (which is the case here for a split moment caused by amdgpu bug above). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #22 from Shmerl --- It's fixed now for amdgpu in Linux kernel master and the fix should be available in 4.20 release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #21 from Martin Flöser --- Great that you finally found the reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #20 from Shmerl --- It looks like it's related to https://bugs.freedesktop.org/show_bug.cgi?id=107978 My monitor (Dell U2413) has a setting for toggling DisplayPort 1.2. When I disable it, Wayland Plasma session isn't crashing anymore and is logging in properly! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Mustafa Muhammad changed: What|Removed |Added CC||mustafa10...@gmail.com --- Comment #19 from Mustafa Muhammad --- (In reply to Shmerl from comment #18) > It can be a downstream issue with Debian specifically (since according to > Mesa developers, it doesn't happen on Arch). So I also opened a Debian bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636 I'm not a developer, but I suggest you try booting the latest Neon ISO to check if it works on your hardware, if it does, it is upstream or distribution issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #18 from Shmerl --- It can be a downstream issue with Debian specifically (since according to Mesa developers, it doesn't happen on Arch). So I also opened a Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Roman Gilg changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |UPSTREAM CC||subd...@gmail.com --- Comment #17 from Roman Gilg --- This is likely an upstream bug. If they say something differently, pls reopen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #16 from Shmerl --- Corresponding wayland-client bug: https://gitlab.freedesktop.org/wayland/wayland/issues/56 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 --- Comment #15 from Shmerl --- I managed to make it produce a core. It's from kwin_wayland. After installing needed debug symbol packages, here is a backtrace: Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/x86_64'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7eff59760f30 in wl_closure_init (message=message@entry=0x7, size=size@entry=52, num_arrays=num_arrays@entry=0x7eff5140858c, args=args@entry=0x0) at ../src/connection.c:562 562 ../src/connection.c: No such file or directory. [Current thread is 1 (Thread 0x7eff51409700 (LWP 7249))] (gdb) bt #0 0x7eff59760f30 in wl_closure_init (message=message@entry=0x7, size=size@entry=52, num_arrays=num_arrays@entry=0x7eff5140858c, args=args@entry=0x0) at ../src/connection.c:562 #1 0x7eff59761aa0 in wl_connection_demarshal (connection=0x7eff440053e0, size=size@entry=52, objects=objects@entry=0x7eff440052e8, message=0x7) at ../src/connection.c:698 #2 0x7eff5975fae8 in queue_event (len=52, display=0x7eff44005270) at ../src/wayland-client.c:1364 #3 read_events (display=0x7eff44005270) at ../src/wayland-client.c:1466 #4 wl_display_read_events (display=display@entry=0x7eff44005270) at ../src/wayland-client.c:1549 #5 0x7eff59760169 in wl_display_dispatch_queue (display=0x7eff44005270, queue=0x7eff44005338) at ../src/wayland-client.c:1788 #6 0x7eff5d123933 in KWayland::Client::ConnectionThread::Privateoperator() (__closure=0x7eff44009550) at ./src/client/connection_thread.cpp:129 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWayland::Client::ConnectionThread::Private::setupSocketNotifier():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:128 #8 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:238 #9 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x7eff44009540, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:421 #10 0x7eff5e606910 in QtPrivate::QSlotObjectBase::call (a=0x7eff514087d0, r=0x564a80be84f0, this=0x7eff44009540) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #11 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject.cpp:3754 #12 0x7eff5e606dd7 in QMetaObject::activate (sender=sender@entry=0x7eff44009440, m=m@entry=0x7eff5e863c60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7eff514087d0) at kernel/qobject.cpp:3633 #13 0x7eff5e611ff9 in QSocketNotifier::activated (this=this@entry=0x7eff44009440, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:136 #14 0x7eff5e612341 in QSocketNotifier::event (this=0x7eff44009440, e=0x7eff51408a30) at kernel/qsocketnotifier.cpp:266 #15 0x7eff5e9cb4a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7eff5e9d2ae0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7eff5e5dd579 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at ../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307 #18 0x7eff5e62fe4a in QCoreApplication::sendEvent (event=0x7eff51408a30, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #19 socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () at kernel/qeventdispatcher_glib.cpp:106 #20 0x7eff5a647287 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7eff5a6474c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7eff5a64754c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7eff5e62f223 in QEventDispatcherGlib::processEvents (this=0x7eff44000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #24 0x7eff5e5dc24b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #25 0x7eff5e42b176 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #26 0x7eff5e434d47 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #27 0x7eff5efb5f2a in start_thread (arg=0x7eff51409700) at pthread_create.c:463 #28 0x7eff5e0fdedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Shmerl changed: What|Removed |Added Summary|Wayland session is coring |Wayland session is coring |right after login |right after login |[radeonsi/DisplayPort] |[amdgpu/DisplayPort] -- You are receiving this mail because: You are watching all bug changes.
