You are not logged in.
I am experiencing lately on KDE the compositor crashing on system wake-up from sleep. It doesn't happen all the time but is happening more particularly after prolonged sleep.
The time this happens, the system wakes up OK and I'm greeted with the login screen but then there is a quick flicker that happens and after logging in, plasma is all messed up - conky and latte-dock not rendering properly. I then go to KDE settings and I get flagged that the compositor has crashed. I restart the compositor and all is back to normal.
Here is a log of the crash:
Jul 12 11:13:34 taichi-z270 systemd-coredump[542734]: Process 542499 (kwin_x11) of user 1000 dumped core.
Stack trace of thread 542499:
#0 0x00007f2484412355 raise (libc.so.6 + 0x3c355)
#1 0x00007f24844123e0 __restore_rt (libc.so.6 + 0x3c3e0)
#2 0x00007f2484412355 raise (libc.so.6 + 0x3c355)
#3 0x00007f24843fb853 abort (libc.so.6 + 0x25853)
#4 0x00007f2483be8061 n/a (libepoxy.so.0 + 0x5e061)
#5 0x00007f2483c4be25 n/a (libepoxy.so.0 + 0xc1e25)
#6 0x00007f247d61fd75 n/a (KWinX11Platform.so + 0x3bd75)
#7 0x00007f247d6202cc n/a (KWinX11Platform.so + 0x3c2cc)
#8 0x00007f247c125cde _ZN4KWin11SceneOpenGL11createSceneEP7QObject (KWinSceneOpenGL.so + 0x13cde)
#9 0x00007f247c1265cb _ZNK4KWin13OpenGLFactory6createEP7QObject (KWinSceneOpenGL.so + 0x145cb)
#10 0x00007f2485da741d n/a (libkwin.so.5 + 0x10741d)
#11 0x00007f2485da82f4 _ZN4KWin13X11Compositor5startEv (libkwin.so.5 + 0x1082f4)
#12 0x00007f2484a861d2 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e01d2)
#13 0x00007f2485527702 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c702)
#14 0x00007f2484a597ba _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b37ba)
#15 0x00007f2484a5c2a3 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b62a3)
#16 0x00007f2484aaf78c _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30978c)
#17 0x00007f247ec1305f n/a (libQt5XcbQpa.so.5 + 0x5f05f)
#18 0x00007f2484a5813c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#19 0x00007f2484a605c4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ba5c4)
#20 0x00005617979c2412 n/a (kwin_x11 + 0x7412)
#21 0x00007f24843fd002 __libc_start_main (libc.so.6 + 0x27002)
#22 0x00005617979c294e _start (kwin_x11 + 0x794e)
Stack trace of thread 542563:
Stack trace of thread 542563:
#0 0x00007f2483d3c158 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x10158)
#1 0x00007f248487ae08 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e08)
#2 0x00007f2484879084 n/a (libQt5Core.so.5 + 0xd3084)
#3 0x00007f2484874e0f n/a (libQt5Core.so.5 + 0xcee0f)
#4 0x00007f2483d35422 start_thread (libpthread.so.0 + 0x9422)
#5 0x00007f24844d5bf3 __clone (libc.so.6 + 0xffbf3)
Stack trace of thread 542594:
#0 0x00007f24844cb15e ppoll (libc.so.6 + 0xf515e)
#1 0x00007f2484aae29b _Z12qt_safe_pollP6pollfdmPK8timespec (libQt5Core.so.5 + 0x30829b)
#2 0x00007f2484aaf9dd _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3099dd)
#3 0x00007f2484a5813c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#4 0x00007f2484873c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
#5 0x00007f2483365789 n/a (libQt5Qml.so.5 + 0x30b789)
#6 0x00007f2484874e0f n/a (libQt5Core.so.5 + 0xcee0f)
#7 0x00007f2483d35422 start_thread (libpthread.so.0 + 0x9422)
#8 0x00007f24844d5bf3 __clone (libc.so.6 + 0xffbf3)
Stack trace of thread 542638:
#0 0x00007f24844cb15e ppoll (libc.so.6 + 0xf515e)
#1 0x00007f2484aae1b1 _Z12qt_safe_pollP6pollfdmPK8timespec (libQt5Core.so.5 + 0x3081b1)
#2 0x00007f2484aaf9dd _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3099dd)
#3 0x00007f2484a5813c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#4 0x00007f2484873c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
#5 0x00007f2484874e0f n/a (libQt5Core.so.5 + 0xcee0f)
#6 0x00007f2483d35422 start_thread (libpthread.so.0 + 0x9422)
#7 0x00007f24844d5bf3 __clone (libc.so.6 + 0xffbf3)
Stack trace of thread 542561:
#0 0x00007f24844cb15e ppoll (libc.so.6 + 0xf515e)
#1 0x00007f2484aae1b1 _Z12qt_safe_pollP6pollfdmPK8timespec (libQt5Core.so.5 + 0x3081b1)
#2 0x00007f2484aaf9dd _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3099dd)
#3 0x00007f2484a5813c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#4 0x00007f2484873c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
#5 0x00007f2485b62098 n/a (libQt5DBus.so.5 + 0x17098)
#6 0x00007f2484874e0f n/a (libQt5Core.so.5 + 0xcee0f)
#7 0x00007f2483d35422 start_thread (libpthread.so.0 + 0x9422)
#8 0x00007f24844d5bf3 __clone (libc.so.6 + 0xffbf3)I must say there has been a recent nvidia update and the problem might have a bearing on this. My question is, is this KDE, nvidia or possible hardware problem? Is there something I can do or do I just sit it out (it doesn't happen consistently) until an update that fixes it? Any test I can do?
I use OpenGL 3.1 for rendering. I will test using 2.0 if I get the same problem but I prefer not to use XREnder. Nvidia is current at 450.57-1. Everything is up-to-date.
Last edited by d_fajardo (2020-07-14 06:28:04)
Offline
I can confirm OpenGL 2.0 crashes as well.
Offline
I have traced the problem and my other problem to the new nvidia driver nvidia 450. I downgraded nvidia, nvidia-utils and nvidia-settings and everything is back to normal.
Others in the forum seem to have issues as well with nvidia 450. For now I have marked to ignore these packages on update.
Question is what do you do when there's a new kernel upgrade? Another thread mentions using nvidia-dkms but as also mentioned in that thread, nvidia-dkms is already in 450. Is this a bug worth reporting?
Offline
The recent update to linux 5.7.8 and nvidia 450.57-2 seem to fixed the problems. I will mark this as solved but will continue to monitor the situation.
Offline