Bug 387606 - Exit dialog is unavailable after videodriver update
Summary: Exit dialog is unavailable after videodriver update
Status: RESOLVED DUPLICATE of bug 345563
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.11.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-04 22:03 UTC by Yan
Modified: 2017-12-05 21:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yan 2017-12-04 22:03:35 UTC
STR:
1. Uninstall or update you video driver
2. Press Start -> Exit
Fullscreen menu with transparent background should appear, but nothing happens

I'm using arch and nvidia proprietary driver
Comment 1 Yan 2017-12-04 22:10:32 UTC
Reboot from classical menu is unavailable too:

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd60ee7acc0 (LWP 14104))]

Thread 3 (Thread 0x7fd5f1a51700 (LWP 14107)):
#0  0x00007fd60a739f7b in poll () from /usr/lib/libc.so.6
#1  0x00007fd603016ed3 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007fd603016fae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007fd60b078204 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007fd60b01b99b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007fd60ae3427e in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007fd60d063cf9 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x00007fd60ae391cb in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007fd60521408a in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007fd60a74447f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fd5f2792700 (LWP 14106)):
#0  0x00007fd60a735a98 in read () from /usr/lib/libc.so.6
#1  0x00007fd60303e521 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007fd60301590b in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3  0x00007fd603016e76 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007fd603016fae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5  0x00007fd60b078204 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#6  0x00007fd60b01b99b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#7  0x00007fd60ae3427e in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x00007fd60bc03376 in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x00007fd60ae391cb in ?? () from /usr/lib/libQt5Core.so.5
#10 0x00007fd60521408a in start_thread () from /usr/lib/libpthread.so.0
#11 0x00007fd60a74447f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fd60ee7acc0 (LWP 14104)):
[KCrash Handler]
#5  0x00007fd60a6828a0 in raise () from /usr/lib/libc.so.6
#6  0x00007fd60a683f09 in abort () from /usr/lib/libc.so.6
#7  0x00007fd60ae23858 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5
#8  0x00007fd60d7334ab in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/libQt5Quick.so.5
#9  0x00007fd60d7344f2 in ?? () from /usr/lib/libQt5Quick.so.5
#10 0x00007fd60d73514a in ?? () from /usr/lib/libQt5Quick.so.5
#11 0x00007fd60b588715 in QWindow::event(QEvent*) () from /usr/lib/libQt5Gui.so.5
#12 0x00007fd60d7aaed6 in QQuickWindow::event(QEvent*) () from /usr/lib/libQt5Quick.so.5
#13 0x0000564713a87af4 in ?? ()
#14 0x00007fd60c1c8f5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#15 0x00007fd60c1d0a36 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#16 0x00007fd60b01d570 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#17 0x00007fd60b57d333 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/libQt5Gui.so.5
#18 0x00007fd60b57dfae in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5
#19 0x00007fd60b55548c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#20 0x00007fd5fad6d6b1 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#21 0x00007fd603015270 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x00007fd603016f69 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x00007fd603016fae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0x00007fd60b0781e1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#25 0x00007fd60b01b99b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#26 0x00007fd60b0249e8 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#27 0x0000564713a8473a in ?? ()
#28 0x00007fd60a66ef6a in __libc_start_main () from /usr/lib/libc.so.6
#29 0x0000564713a8488a in _start ()
Comment 2 David Edmundson 2017-12-05 07:24:39 UTC
>#8  0x00007fd60d7334ab in QSGRenderLoop::handleContextCreationFailure(

Your graphic driver setup is broken.
We can't do much about that.

You should have had a warning dialog when plasma started.

*** This bug has been marked as a duplicate of bug 345563 ***
Comment 3 Yan 2017-12-05 10:26:49 UTC
Why is this bug invalid? KDE doesn't provide fallback way to terminate session. Video driver updating is normal process of OS life cycle.
Comment 4 Kai Uwe Broulik 2017-12-05 12:14:53 UTC
The big issue here is that when you update the driver at runtime newly started opengl processes (like lockscreen (you better keep wiggling your mouse once in a while while doing an apt upgrade) or shutdown dialog) fail. Not sure if there's much we can do about it, perhaps we should look into software renderer fallbacks for critical parts like lockscreen and logout?
Comment 5 Yan 2017-12-05 21:29:58 UTC
Yes, simple cpu-rendered dropdown menu would be fine