Results 1 to 5 of 5

Thread: KDE Crashes on logout

  1. #1

    Default KDE Crashes on logout

    When I try to logout, kdeinit5 crashes with either a Segfault or with an Abort message.

    Here is the Developer Info.

    Code:
     Application: kdeinit5 (kdeinit5), signal: Aborted
     Using host libthread_db library "/lib64/libthread_db.so.1".
     [KCrash Handler]
     #4  0x00007f67d94630a7 in raise () at /lib64/libc.so.6
     #5  0x00007f67d9464458 in abort () at /lib64/libc.so.6
     #6  0x00007f67d94a0764 in  () at /lib64/libc.so.6
     #7  0x00007f67d94a5fce in malloc_printerr () at /lib64/libc.so.6
     #8  0x00007f67d94a6ce6 in _int_free () at /lib64/libc.so.6
     #9  0x00007f67da82f026 in xcb_disconnect () at /usr/lib64/libxcb.so.1
     #10 0x00007f67c836cbd5 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #11 0x00007f67c836cc55 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #12 0x00007f67c8379215 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #13 0x00007f67d9a8ccc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
     #14 0x00007f67d9b0e8ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
     #15 0x00007f67d9a99a89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
     #16 0x00007f67d9a5d18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
     #17 0x00007f67d9a5ce95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
     #18 0x00007f67d9ab1743 in QEventDispatcherUNIX::activateSocketNotifiers() () at /usr/lib64/libQt5Core.so.5
     #19 0x00007f67d9ab1beb in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) () at /usr/lib64/libQt5Core.so.5
     #20 0x00007f67d9ab1f3b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
     #21 0x00007f67c7f1b33d in  () at /usr/lib64/libQt5XcbQpa.so.5
     #22 0x00007f67d9a5ad53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
     #23 0x00007f67d9a628f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
     #24 0x00007f67c8376a1a in kdemain () at /usr/lib64/libkdeinit5_klauncher.so
     #25 0x00000000004086fc in _start ()

  2. #2

    Default Re: KDE Crashes on logout

    Hmm Switching from GLX to EGL fixed the problem.

    EDIT: Spoke too soon. The crashes continue.

  3. #3

    Default Re: KDE Crashes on logout

    OK disabling session saving seems to have stopped the crashes. We will see for how long.

  4. #4

    Default Re: KDE Crashes on logout

    OK obviously meddling with the graphical and session settings stops the crashes for a while, but eventually the crashes begin again.

    Here is another segmentation fault.

    Code:
     Application: kdeinit5 (kdeinit5), signal: Segmentation fault
     Using host libthread_db library "/lib64/libthread_db.so.1".
     [KCrash Handler]
     #4  0x00007f07922872a6 in malloc_usable_size () at /lib64/libc.so.6
     #5  0x00007f0790234219 in  () at /usr/X11R6/lib64/libGL.so.1
     #6  0x00007f078e22f1fc in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
     #7  0x00007f079360c026 in xcb_disconnect () at /usr/lib64/libxcb.so.1
     #8  0x00007f0781149bd5 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #9  0x00007f0781149c55 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #10 0x00007f0781156215 in  () at /usr/lib64/libkdeinit5_klauncher.so
     #11 0x00007f0792869cc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
     #12 0x00007f07928eb8ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
     #13 0x00007f0792876a89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
     #14 0x00007f079283a18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
     #15 0x00007f0792839e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
     #16 0x00007f079288e743 in QEventDispatcherUNIX::activateSocketNotifiers() () at /usr/lib64/libQt5Core.so.5
     #17 0x00007f079288ebeb in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) () at /usr/lib64/libQt5Core.so.5
     #18 0x00007f079288ef3b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
     #19 0x00007f0780cf833d in  () at /usr/lib64/libQt5XcbQpa.so.5
     #20 0x00007f0792837d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
     #21 0x00007f079283f8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
     #22 0x00007f0781153a1a in kdemain () at /usr/lib64/libkdeinit5_klauncher.so
     #23 0x00000000004086fc in _start ()

  5. #5

    Default Re: KDE Crashes on logout

    Quote Originally Posted by Dellius View Post
    OK obviously meddling with the graphical and session settings stops the crashes for a while, but eventually the crashes begin again.

    Here is another segmentation fault.
    Well, this crash at least is in the nvidia driver, in its libGL in particular:
    Code:
     Application: kdeinit5 (kdeinit5), signal: Segmentation fault
     Using host libthread_db library "/lib64/libthread_db.so.1".
     [KCrash Handler]
     #4  0x00007f07922872a6 in malloc_usable_size () at /lib64/libc.so.6
     #5  0x00007f0790234219 in  () at /usr/X11R6/lib64/libGL.so.1
     #6  0x00007f078e22f1fc in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
    You're not the first one complaining about problems when using the nvidia driver...
    Although switching to nouveau is probably not the best option either. Depending on your card, the G03 driver might work better, or not.

    I would definitely recommend to switch to GLX or XRender though, *not* EGL. AFAIK EGL is not really well supported by the nvidia driver.
    And if using GLX, it might make a difference whether you set it to OpenGL 2.1 or OpenGL 3.0.
    Have you tried to disable compositing altogether?

    Other than that, I can only suggest to report your crashes to bugs.kde.org (the crash dialog should allow you to do that anyway), and/or ask in the KDE forums at http://forum.kde.org/.
    You'll also reach the KDE (and kwin in particular) developers this way.
    Last edited by wolfi323; 18-Mar-2016 at 01:52.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •