Results 1 to 8 of 8

Thread: kmserver failure after graphics driver upgraded

  1. #1
    Join Date
    Sep 2009
    Location
    Liverpool
    Posts
    140

    Default kmserver failure after graphics driver upgraded

    This is not really a big deal but from time to time apper notifies me of a new nVidia driver. When I update the driver I then can't log out of KDE. Also if I switch to a terminal and try to log on as superuser (so as to terminate nicely) my password is rejected as incorrect.
    The error seems to be a problem in ksmserver-logout-greeter, which displays a panel with the following debug info:

    Code:
    Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: AbortedUsing host libthread_db library "/lib64/libthread_db.so.1".
    [Current thread is 1 (Thread 0x7f166f12f940 (LWP 17865))]
    
    
    Thread 4 (Thread 0x7f165559a700 (LWP 17868)):
    #0  0x00007f166aac020d in poll () from /lib64/libc.so.6
    #1  0x00007f166504c314 in ?? () from /usr/lib64/libglib-2.0.so.0
    #2  0x00007f166504c42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
    #3  0x00007f166b3cd1ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #4  0x00007f166b37abfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #5  0x00007f166b1b5f5a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
    #6  0x00007f166d38a3d8 in ?? () from /usr/lib64/libQt5Qml.so.5
    #7  0x00007f166b1baa29 in ?? () from /usr/lib64/libQt5Core.so.5
    #8  0x00007f1665569744 in start_thread () from /lib64/libpthread.so.0
    #9  0x00007f166aac8aad in clone () from /lib64/libc.so.6
    
    
    Thread 3 (Thread 0x7f1655d9b700 (LWP 17867)):
    #0  0x00007f1665570a7c in __lll_lock_wait () from /lib64/libpthread.so.0
    #1  0x00007f166556b7fb in pthread_mutex_lock () from /lib64/libpthread.so.0
    #2  0x00007f1664688e4c in ?? () from /usr/X11R6/lib64/libGL.so.1
    #3  0x00007f166468dd81 in ?? () from /usr/X11R6/lib64/libGL.so.1
    #4  0x00007f166468e298 in ?? () from /usr/X11R6/lib64/libGL.so.1
    #5  0x00007f16602a4102 in ?? () from /usr/lib64/tls/libnvidia-tls.so.384.98
    #6  0x00007f166508c750 in ?? () from /usr/lib64/libglib-2.0.so.0
    #7  0x00007f166504be49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
    #8  0x00007f166504c2a8 in ?? () from /usr/lib64/libglib-2.0.so.0
    #9  0x00007f166504c42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
    #10 0x00007f166b3cd1ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #11 0x00007f166b37abfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #12 0x00007f166b1b5f5a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
    #13 0x00007f166bf30295 in ?? () from /usr/lib64/libQt5DBus.so.5
    #14 0x00007f166b1baa29 in ?? () from /usr/lib64/libQt5Core.so.5
    #15 0x00007f1665569744 in start_thread () from /lib64/libpthread.so.0
    #16 0x00007f166aac8aad in clone () from /lib64/libc.so.6
    
    
    Thread 2 (Thread 0x7f16578c1700 (LWP 17866)):
    #0  0x00007f166aac020d in poll () from /lib64/libc.so.6
    #1  0x00007f1665dc93e2 in ?? () from /usr/lib64/libxcb.so.1
    #2  0x00007f1665dcafcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
    #3  0x00007f1659e240d9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
    #4  0x00007f166b1baa29 in ?? () from /usr/lib64/libQt5Core.so.5
    #5  0x00007f1665569744 in start_thread () from /lib64/libpthread.so.0
    #6  0x00007f166aac8aad in clone () from /lib64/libc.so.6
    
    
    Thread 1 (Thread 0x7f166f12f940 (LWP 17865)):
    [KCrash Handler]
    #6  0x00007f166aa138d7 in raise () from /lib64/libc.so.6
    #7  0x00007f166aa14caa in abort () from /lib64/libc.so.6
    #8  0x00007f166b1a63be in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
    #9  0x00007f166da5b719 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib64/libQt5Quick.so.5
    #10 0x00007f166da62ac9 in ?? () from /usr/lib64/libQt5Quick.so.5
    #11 0x00007f166da63413 in ?? () from /usr/lib64/libQt5Quick.so.5
    #12 0x00007f166b8d2ace in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5
    #13 0x00007f166da958e5 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5
    #14 0x0000000000409021 in ?? ()
    #15 0x00007f166c50328c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
    #16 0x00007f166c5078ea in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
    #17 0x00007f166b37cbe5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
    #18 0x00007f166b8c8591 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5
    #19 0x00007f166b8c907d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5
    #20 0x00007f166b8aaeab in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5
    #21 0x00007f1659e518a0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
    #22 0x00007f166504c134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
    #23 0x00007f166504c388 in ?? () from /usr/lib64/libglib-2.0.so.0
    #24 0x00007f166504c42c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
    #25 0x00007f166b3cd18c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #26 0x00007f166b37abfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
    #27 0x00007f166b382ae6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
    #28 0x000000000040629e in ?? ()
    #29 0x00007f166a9ff6e5 in __libc_start_main () from /lib64/libc.so.6
    #30 0x00000000004063c9 in _start ()
    The only thing I can then do is power down to reboot, after which everything is fine. But it does seem there's a little bug here somewhere.

    Regards

    Fred

  2. #2
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,070

    Default Re: kmserver failure after graphics driver upgraded

    Quote Originally Posted by fredsie View Post
    When I update the driver I then can't log out of KDE. Also if I switch to a terminal and try to log on as superuser (so as to terminate nicely) my password is rejected as incorrect.
    I experience the same issue with unable to logout of the current session after updating the nvidia driver via yast.

    Dropping to a virtual terminal and issuing:

    Code:
    sudo /sbin/shutdown -r now
    requests the root password, which is accepted.

    Perhaps try that the next time, rather than attempting to login as root and then terminate, although why that doesn't work I don't know.
    Regards, Paul

    Tumbleweed (Snapshot: 20190612) KDE Plasma 5
    Leap 15.0 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected]

  3. #3
    Join Date
    Sep 2009
    Location
    Liverpool
    Posts
    140

    Default Re: kmserver failure after graphics driver upgraded

    Thanks Paul, I'll try that next time. It seems sudo is retrieving the password through a different route than the attempted logon to root.

  4. #4
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,070

    Default Re: kmserver failure after graphics driver upgraded

    Actually this appears to be a bug which was first reported mid 2016.

    "Crash on logout after Nvidia driver update."
    https://bugs.kde.org/show_bug.cgi?id=364593
    Regards, Paul

    Tumbleweed (Snapshot: 20190612) KDE Plasma 5
    Leap 15.0 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected]

  5. #5
    Join Date
    Sep 2008
    Posts
    2,997

    Default Re: kmserver failure after graphics driver upgraded

    I usually go ctrl+alt+F1 login as root and do
    Code:
    init 6
    happened to me once or twice not as often to be a nuisance
    out of curiosity what nvidia driver do you use I'm on G03 as I have an old card but never had any real issues

  6. #6
    Join Date
    Sep 2009
    Location
    Liverpool
    Posts
    140

    Default Re: kmserver failure after graphics driver upgraded

    Quote Originally Posted by I_A View Post
    I usually go ctrl+alt+F1 login as root and do
    Code:
    init 6

    out of curiosity what nvidia driver do you use I'm on G03 as I have an old card but never had any real issues
    Yeah but as I said originally that's part of the issue; I can't log in as root in these circumstances.

    G04

  7. #7
    Join Date
    Sep 2009
    Location
    Liverpool
    Posts
    140

    Default Re: kmserver failure after graphics driver upgraded

    Quote Originally Posted by tannington View Post
    Dropping to a virtual terminal and issuing:

    Code:
    sudo /sbin/shutdown -r now
    requests the root password, which is accepted.
    Actually Paul, having looked at the MAN page for shutdown, I see that I can also specify a delay before shutdown. So this means I can issue a shutdown/reboot with say a 20 minute delay before kicking off the upgrade, and then walk away and leave it to sort itself out. I'll do this next time. (I say 20 mins since nvidia graphics upgrades seem for some reason to take forever!)

    Fred

  8. #8
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,070

    Default Re: kmserver failure after graphics driver upgraded

    Quote Originally Posted by I_A View Post
    out of curiosity what nvidia driver do you use I'm on G03 as I have an old card but never had any real issues
    I'm using the G04 driver. Happened yesterday (20171123) on a 42.3 system when I updated to 384.98-29.1

    Quote Originally Posted by fredsie View Post
    So this means I can issue a shutdown/reboot with say a 20 minute delay before kicking off the upgrade, and then walk away and leave it to sort itself out. I'll do this next time.
    Hm... I don't know that's an approach I'd personally want to take... but... as long as the delay is adequate...

    (I say 20 mins since nvidia graphics upgrades seem for some reason to take forever!)
    That's because the kernel has to be rebuilt.
    Regards, Paul

    Tumbleweed (Snapshot: 20190612) KDE Plasma 5
    Leap 15.0 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected]

Posting Permissions

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