[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=364593

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[phd]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #26 from phd  ---
@Johannes Claesson
I have noticed ksmserver crashing again recently after nvidia drivers update.

What is more, trying to run drkonqi for that crash makes drkonqi crash as well.
This implies there might be a different reason for those crashes than the one
originally solved for this bug report.
But I need to reproduce it and actually get the backtrace to confirm it.

I think:
1. we should have a default shortcut assigned to "Logout without confirmation"
action: Ctrl+Alt+Shift+Del
2. DrKonqi probably should not use QtQuick, because user is left with a crash
handler that itself crashes in such situations...
It's a pity that QtQuick can't handle fallback to software rendering by itself
when it cannot initialize OpenGL context internally.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Johannes Claesson]

https://bugs.kde.org/show_bug.cgi?id=364593

Johannes Claesson  changed:

   What|Removed |Added

 CC||johannes.claes...@gmail.com

--- Comment #25 from Johannes Claesson  ---
Why is this marked as fixed? Still an issue as of 5.24.90

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[phd]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #24 from phd  ---
Fixed in KDE Frameworks 5.78.
See bug #366156

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[phd]

https://bugs.kde.org/show_bug.cgi?id=364593

phd  changed:

   What|Removed |Added

   Assignee|l.lu...@kde.org |p...@phd.re
 CC||p...@phd.re
   Version Fixed In||KDE Frameworks 5.78
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=366156

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=375913

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Arthur Huillet]

https://bugs.kde.org/show_bug.cgi?id=364593

Arthur Huillet  changed:

   What|Removed |Added

 CC||arthur.huillet+kdebugs@free
   ||.fr

--- Comment #23 from Arthur Huillet  ---
I am not sure what is being referred to as "the driver announcing that it
supports OpenGL". I assume this is from interpreting the values of some
glGetString queries.
Note that GL context creation can legally fail for various reasons, regardless
of what glGetString returns. It not valid to assume that because glGetString
returns anything specific, then context creation will or must not fail.
The application therefore ought to handle the context creation error
gracefully, and it seems invalid - at least with the evidence on this thread -
to call that a NVIDIA driver bug.
It is certainly less than optimal behavior that the context creation fails, but
that is not a bug, and, unfortunately, unlikely to change in the near future.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||hep30...@gmail.com

--- Comment #22 from Christoph Feck  ---
*** Bug 418601 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Tony]

https://bugs.kde.org/show_bug.cgi?id=364593

Tony  changed:

   What|Removed |Added

 CC|jodr...@live.com|

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #21 from Christoph Feck  ---
It was marked as resolved, because there is no more work to be done by KDE
developers. The fix needs to be made in the NVIDIA drivers, or a workaround
added in QtQuick to detect a broken OpenGL driver and fall back to software
rendering.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Liam Dawe]

https://bugs.kde.org/show_bug.cgi?id=364593

Liam Dawe  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DOWNSTREAM  |---

--- Comment #20 from Liam Dawe  ---
Not sure why this was set as resolved, it's clearly not. I would also like to
track this, as it's such a crazy issue to have. Forcing people to use terminal
to shut down, after updating NVIDIA is not going to win us over an users.

Something really needs to be done about this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Liam Dawe]

https://bugs.kde.org/show_bug.cgi?id=364593

Liam Dawe  changed:

   What|Removed |Added

 CC||liamd...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||emanu@gmail.com

--- Comment #19 from Christoph Feck  ---
*** Bug 414446 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #18 from Christoph Feck  ---
*** Bug 408482 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||ernestopereslo...@yahoo.es

--- Comment #17 from Christoph Feck  ---
*** Bug 379935 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||crgla...@gmail.com

--- Comment #16 from Christoph Feck  ---
*** Bug 366325 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 CC||eridanired...@yahoo.com.mx

--- Comment #15 from Christoph Feck  ---
*** Bug 401447 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Alex Barrero]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #14 from Alex Barrero  ---
anything new about this issue? update after update is always happening this. Is
it so difficult to find a solution?

KDE Neon 5.14
Nvidia Driver 410.57

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Alex Barrero]

https://bugs.kde.org/show_bug.cgi?id=364593

Alex Barrero  changed:

   What|Removed |Added

 CC||alex.brrsc...@gmail.com

--- Comment #13 from Alex Barrero  ---
Created attachment 114216
  --> https://bugs.kde.org/attachment.cgi?id=114216=edit
ksmserver crash log on Neon 5.13

Still affected in KDE Neon 5.13

Qt: 5.11.1
Kernel: 4.15.0-29-generic

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #12 from Lastique  ---
I've created a Qt bug: https://bugreports.qt.io/browse/QTBUG-67535

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #11 from Christoph Feck  ---
It is not a crash. Qt simply aborts if an OpenGL driver fails to create an
OpenGL context. You can report this to Qt developers, but they will tell you it
is a driver bug. An OpenGL driver that doesn't allow to access the OpenGL API
is simply broken.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #10 from Lastique  ---
I've created this thread:

https://devtalk.nvidia.com/default/topic/1031836/linux/opengl-context-cannot-be-created-after-nvidia-driver-update-cannot-reboot-the-system/

Please, feel free to add any technical details.

I still think this is a bug in KDE as well, even if the driver behaves not as
you'd expect. A crash is always a bug in the application.

I will reopen this bug if I get the response from Nvidia indicating that the
fix should be done in the application.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #9 from Christoph Feck  ---
It still needs to be fixed in the NVIDIA driver. Plasma works completely fine
on my system without OpenGL support, because Qt has a software fallback
renderer, see
http://blog.qt.io/blog/2015/01/22/introducing-the-qt-quick-2d-renderer/

As I wrote in comment #7, the issue is that NVIDIA says it does support OpenGL
_before_ checking if there is kernel version mismatch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=364593

Lastique  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DOWNSTREAM  |---
 Ever confirmed|0   |1

--- Comment #8 from Lastique  ---
I understand the source of the problem - the updated OpenGL part of the driver
may not be binary compatible with the loaded kernel module or X11 driver or
something and therefore refuses to load. But "reboot after updating the driver"
is not a resolution because *I cannot reboot* except by killing X server. This
bug requests a better solution than killing X server. For example, cache OpenGL
context on boot or draw the logout/reboot UI in software.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=364593

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Christoph Feck  ---
If you are updating nvidia drivers, you must reboot your system. This is
because every driver version comes with its own kernel module.

If the driver cannot find the matching kernel module, Qt is not able to create
OpenGL contexts, despite the driver announcing that it supports OpenGL.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #6 from Lastique  ---
Created attachment 109792
  --> https://bugs.kde.org/attachment.cgi?id=109792=edit
Crash log on Kubuntu 17.10.

Still crashes on Kubuntu 17.10. Plasma 5.10.5.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=364593

floux...@gmail.com changed:

   What|Removed |Added

 CC||floux...@gmail.com

--- Comment #5 from floux...@gmail.com ---
Created attachment 109024
  --> https://bugs.kde.org/attachment.cgi?id=109024=edit
stacktrace

Still occurs in KDE 5.8.7

OS : openSUSE Leap 42.3
Qt : 5.6.2
Kernel : 4.4.92-31-default x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #4 from Lastique  ---
I've found one workaround to this crash. You can invoke the
logout/reboot/shutdown dialog once *before* the driver update, cancel it, then
update the driver and then invoke the dialog again. ksmserver won't crash in
that case.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Aleksey Samoilov]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #3 from Aleksey Samoilov  ---
Affected me in KDE Neon 5.9.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Aleksey Samoilov]

https://bugs.kde.org/show_bug.cgi?id=364593

Aleksey Samoilov  changed:

   What|Removed |Added

 CC||samoilov@gmail.com

--- Comment #2 from Aleksey Samoilov  ---
Created attachment 104024
  --> https://bugs.kde.org/attachment.cgi?id=104024=edit
Crash log

Crash log related

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364593

--- Comment #1 from Lastique  ---
Created attachment 99643
  --> https://bugs.kde.org/attachment.cgi?id=99643=edit
Crash log

Thread 1 (Thread 0x7f72a10ee900 (LWP 1970)):
[KCrash Handler]
#6  0x7f72a0af2418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f72a0af401a in __GI_abort () at abort.c:89
#8  0x7f729c3abff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=, msg=) at
global/qlogging.cpp:781
#10 0x7f729f426af1 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f729f42f332 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f729f42f733 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f729c8ea2e5 in QWindow::event (this=0x1b5a710, ev=)
at kernel/qwindow.cpp:2060
#14 0x7f729f462871 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f729ce9205c in QApplicationPrivate::notify_helper
(this=this@entry=0x1b15d00, receiver=receiver@entry=0x1b5a710,
e=e@entry=0x7fff647898e0) at kernel/qapplication.cpp:3716
#16 0x7f729ce97516 in QApplication::notify (this=0x1b17220,
receiver=0x1b5a710, e=0x7fff647898e0) at kernel/qapplication.cpp:3499
#17 0x7f729c59f62b in QCoreApplication::notifyInternal (this=0x1b17220,
receiver=receiver@entry=0x1b5a710, event=event@entry=0x7fff647898e0) at
kernel/qcoreapplication.cpp:965
#18 0x7f729c8e24ec in QCoreApplication::sendSpontaneousEvent
(event=0x7fff647898e0, receiver=0x1b5a710) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:227
#19 QGuiApplicationPrivate::processExposeEvent (e=0x2008ed0) at
kernel/qguiapplication.cpp:2663
#20 0x7f729c8e325d in QGuiApplicationPrivate::processWindowSystemEvent
(e=e@entry=0x2008ed0) at kernel/qguiapplication.cpp:1658
#21 0x7f729c8c6f38 in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:625
#22 0x7f728e5dbf10 in userEventSourceDispatch (source=) at
eventdispatchers/qeventdispatcher_glib.cpp:70
#23 0x7f7296686127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f7296686380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f729668642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f729c5f5a7f in QEventDispatcherGlib::processEvents (this=0x1b67590,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#27 0x7f729c59cdea in QEventLoop::exec (this=this@entry=0x7fff64789bb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#28 0x7f72a0ea25c9 in KSMShutdownDlg::exec (this=this@entry=0x1b5a710) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdowndlg.cpp:293
#29 0x7f72a0ea2698 in KSMShutdownDlg::confirmShutdown
(maysd=maysd@entry=true, choose=choose@entry=true, sdtype=@0x7fff64789cdc:
KWorkSpace::ShutdownTypeReboot, bootOption=..., theme=...) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdowndlg.cpp:308
#30 0x7f72a0eb1326 in KSMServer::shutdown (this=0x1ba2190,
confirm=, sdtype=KWorkSpace::ShutdownTypeReboot,
sdmode=KWorkSpace::ShutdownModeInteractive) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdown.cpp:164
#31 0x7f72a0470ad9 in _SmsProcessMessage () from
/usr/lib/x86_64-linux-gnu/libSM.so.6
#32 0x7f72a0261071 in IceProcessMessages () from
/usr/lib/x86_64-linux-gnu/libICE.so.6
#33 0x7f72a0e9a012 in KSMServer::processData (this=0x1ba2190) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/server.cpp:790
#34 0x7f729c5cde4f in QtPrivate::QSlotObjectBase::call (a=0x7fff64789fe0,
r=0x1ba2190, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#35 QMetaObject::activate (sender=sender@entry=0x1c44d80,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff64789fe0) at kernel/qobject.cpp:3698

-- 
You are receiving this mail because:
You are watching all bug changes.