Shutdown or reboot throws "ksmserver-logout-greeter Terminated unexpectedly" after Nvidia driver upd

Hi, today (2021-05-19) the “updater”(zypper?) urged me to update/install a new Nvidia-driver together with a kernel update of some sort (as it usually does when a new Nvidia driver is installed).
After that I’m supposed to restart the computer to get everything up n’running.

When selecting, in this order, Gecko-icon / Leave / Restart (or Shutdown) - I get:

ksmserver-logout-greeter terminated unexpectedly
ksmserver-logout-greeter PID: 1529 Signal: Aborted (6) Time: 2021-05-19 09:33:57

chosing debugger message gives:

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted
[KCrash Handler]
#4  0x00007f352971b420 in raise () from /lib64/libc.so.6
#5  0x00007f352971ca01 in abort () from /lib64/libc.so.6
#6  0x00007f3529f217fb in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#7  0x00007f352ca8bf9d in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib64/libQt5Quick.so.5
#8  0x00007f352ca8cd8d in ?? () from /usr/lib64/libQt5Quick.so.5
#9  0x00007f352ca8db2a in ?? () from /usr/lib64/libQt5Quick.so.5
#10 0x00007f352a732675 in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5
#11 0x00007f352cb0b525 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5
#12 0x0000555ad1d6fb81 in ?? ()
#13 0x00007f352b43cf2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#14 0x00007f352b444540 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#15 0x00007f352a120328 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#16 0x00007f352a7285ea in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5
#17 0x00007f352a72883d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5
#18 0x00007f352a70223b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5
#19 0x00007f351a6d51da in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#20 0x00007f3521ffd624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f3521ffd9c0 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f3521ffda4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f352a17d3af in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#24 0x00007f352a11e57a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#25 0x00007f352a127780 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#26 0x0000555ad1d6b195 in ?? ()
#27 0x00007f352970634a in __libc_start_main () from /lib64/libc.so.6
#28 0x0000555ad1d6b2ba in _start ()
[Inferior 1 (process 1529) detached]

Now it’s impossible to shut down the computer via the operating system!

This has somewhat occured in the past with 15.1 but then it was possible to at least choose Reboot/Shutdown from the “Gecko”-meny (se above).

I’m sure everything sort itself if I could reboot it, but how?

Use ctrl-alt-f2 to switch to a virtual terminal, login as your normal user, then issue:

sudo shutdown -r now

the machine will then shutdown and reboot.

Afterthought:

If that fails, (unlikely), then:

Depress and hold the alt and sysrq keys, then in sequence use the following key sequence, waiting a few seconds between each key press

r e i s u b

If that also fails, (very unlikely), then your only option is a hard reset or power off.

The “ctrl-alt-f2”, login as your normal user, then issue: “sudo shutdown -r now” worked for me.
@tannington: :good: Big thank you for your ultra fast reply!!!

Now the “only remaining question” is: why did the “ksmserver-logout-greeter” crash in the first place?

Addendum:

  • Information central / Memory
  • Information central / Energy information
  • Information central / File index supervisor
  • Graphical information / OpenGL
  • Discover (software central)

All of the above caused a crash respectively after the Nvidia driver update, but works now after a restart.

There seams to be something fishy about Nvidia versus the subsequent kernel update…

Should I report a bug somewhere?

I guess because it doesn’t like the video driver being replaced whilst it’s running.

I see the same thing on a Leap 15.2 system with the nvidia driver, as a matter of course I always drop to a virtual terminal and reboot after an nvidia driver update.

Should I report a bug somewhere?

https://bugs.kde.org/

though I don’t know it will be acted upon…

Welcome to the openSUSE forums, my bad, only just noticed you’re a new member :slight_smile:

Sooo, same ol’ same ol’ then? Linus vs Nvidia finger pointing exercises? :disapointed:
Ooh well, what’s a ball at the castle anyway? It could be free from graphics crashes or, or … it could just work, she said with something dreamy in her eyes …

And thanks for your heart warming and welcoming words!

It’s “an ongoing thing”… There are some bug reports about it already, didn’t have time to look for them earlier, but here’s a couple I’ve just found, I’m sure others exist also…

https://bugs.kde.org/show_bug.cgi?id=364593
https://bugreports.qt.io/browse/QTBUG-67535

Most are closed as “upstream” / “downstream” … not our bug, etc, etc … it’s kde, it’s qt, it’s the x server, it’s nvidia … to which we could add moon phase, day of week, or the colour of our underwear…