Summary: | Kwin crashes on login with Wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | langsorigingaleia |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | nate |
Priority: | NOR | ||
Version: | 5.27.7 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
langsorigingaleia
2023-09-04 08:58:39 UTC
It sounds like Plasma crashed on login and failed to restart automatically. The root cause is probably the kwin_wayland crash, so let's debug that for now. Can you please attach a backtrace of the kwin_wayland crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Absolutely, I apologize, I'm a bit new to this. I went through the guide to collect the BT. So the kwin actually seems to have 3 crashed instances but I note that the program sent an interrupt signal. TIME PID UID GID SIG COREFILE EXE SIZE Wed 2023-09-06 05:53:16 CEST 23198 1000 1000 SIGABRT inaccessible /usr/bin/kwin_wayland - Wed 2023-09-06 05:53:12 CEST 22885 1000 1000 SIGABRT inaccessible /usr/bin/kwin_wayland - Wed 2023-09-06 05:53:09 CEST 22298 1000 1000 SIGABRT inaccessible /usr/bin/kwin_wayland - All seems to say the exact same thing. This is 23198 #0 0x00007f2081a9ee3b in pthread_kill () at /usr/lib/libc.so.6 #1 0x00007f2081a439a8 in raise () at /usr/lib/libc.so.6 #2 0x00007f2081a26478 in abort () at /usr/lib/libc.so.6 #3 0x00007f2083efb1ae in () at /usr/lib/libepoxy.so.0 #4 0x00007f2083efeb92 in () at /usr/lib/libepoxy.so.0 #5 0x00007f2084a650a6 in KWin::EglDmabuf::~EglDmabuf() () at /usr/lib/libkwin.so.5 #6 0x00007f2084a69c91 in KWin::AbstractEglBackend::~AbstractEglBackend() () at /usr/lib/libkwin.so.5 #7 0x00007f208499738e in () at /usr/lib/libkwin.so.5 #8 0x00007f20847c2cb3 in KWin::Compositor::stop() () at /usr/lib/libkwin.so.5 #9 0x00007f20847bb79c in KWin::Compositor::reinitialize() () at /usr/lib/libkwin.so.5 #10 0x00007f2082edb467 in () at /usr/lib/libQt5Core.so.5 #11 0x00007f208492f89a in KWin::Workspace::slotReconfigure() () at /usr/lib/libkwin.so.5 #12 0x00007f2082edb467 in () at /usr/lib/libQt5Core.so.5 #13 0x00007f2082edcf7f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #14 0x00007f2082ecd7ae in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x00007f208237a30f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x00007f2082ea55d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x00007f2082ef62da in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #18 0x00007f2082ef6b51 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #19 0x0000558f96984742 in () #20 0x00007f2082ea42c4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #21 0x00007f2082ea5783 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #22 0x0000558f96888515 in () #23 0x00007f2081a27f90 in () at /usr/lib/libc.so.6 #24 0x00007f2081a2804a in __libc_start_main () at /usr/lib/libc.so.6 #25 0x0000558f9688a315 in () But it looks like this is the exact same backtrace as the one I originally posted. Thanks, that's helpful. *** This bug has been marked as a duplicate of bug 466174 *** |