Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#56764 - [mesa] Plasma freezes when displaying logout screen
Attached to Project:
Arch Linux
Opened by Pierre Choffet (Peuc) - Monday, 18 December 2017, 17:03 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 15 January 2018, 16:46 GMT
Opened by Pierre Choffet (Peuc) - Monday, 18 December 2017, 17:03 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 15 January 2018, 16:46 GMT
|
DetailsDescription:
Plasma crashes when the logout screen of KDE is displayed. The X display is frozen (with mouse cursor still movable), the system must be restarted through ssh or hardware reset. According to system updates logs, the problem has been introduced in non-testing packages between Nov. 27th and Dec. 10th. Additional info: * package version(s) Up to date ArchLinux, with plasma-workspace 5.11.4-2 * Trace # coredumpctl info 4526 PID: 4526 (ksmserver-logou) UID: 1000 (charles) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Mon 2017-12-18 00:22:14 CET (17h ago) Command Line: /usr/lib/ksmserver-logout-greeter --shutdown-allowed --mode shutdown --mode-fd 40 Executable: /usr/lib/ksmserver-logout-greeter Control Group: /user.slice/user-1000.slice/session-c2.scope Unit: session-c2.scope Slice: user-1000.slice Session: c2 Owner UID: 1000 (charles) Boot ID: a39b83ac61d1490eb840daa269b38b1b Machine ID: 021010923b614b0a89df4a0cb50411e6 Hostname: charles_pc Storage: /var/lib/systemd/coredump/core.ksmserver-logou.1000.a39b83ac61d1490eb840daa269b38b1b.4526.1513552934000000.lz4 Message: Process 4526 (ksmserver-logou) of user 1000 dumped core. Stack trace of thread 4526: #0 0x00007fd347301860 raise (libc.so.6) #1 0x00007fd346391f9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x00007fd3473018e0 __restore_rt (libc.so.6) #3 0x00007fd32d23e1be n/a (i915_dri.so) #4 0x00007fd34a43a783 _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5) #5 0x00007fd34a4401de _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #6 0x00007fd34a430632 _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #7 0x00007fd34a430afc _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #8 0x00007fd34a46ac60 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #9 0x00007fd34a4cf110 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #10 0x00007fd34a45cfb8 n/a (libQt5Quick.so.5) #11 0x00007fd34a45dfea n/a (libQt5Quick.so.5) #12 0x00007fd348225a35 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5) #13 0x00007fd34a4da626 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5) #14 0x000055f580b7eaf4 n/a (ksmserver-logout-greeter) #15 0x00007fd348eb1e3c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #16 0x00007fd348eb9816 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #17 0x00007fd347ca81e0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #18 0x00007fd34821a583 _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5) #19 0x00007fd34821b1fe _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gui.so.5) #20 0x00007fd3481f2bbc _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5) #21 0x00007fd33799c15d n/a (libQt5XcbQpa.so.5) #22 0x00007fd347ca682b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #23 0x00007fd347cafb18 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #24 0x000055f580b7b73a n/a (ksmserver-logout-greeter) #25 0x00007fd3472edf4a __libc_start_main (libc.so.6) #26 0x000055f580b7b88a _start (ksmserver-logout-greeter) Stack trace of thread 4529: #0 0x00007fd3473b4a48 __read (libc.so.6) #1 0x00007fd33fcbe521 n/a (libglib-2.0.so.0) #2 0x00007fd33fc9590b g_main_context_check (libglib-2.0.so.0) #3 0x00007fd33fc96e76 n/a (libglib-2.0.so.0) #4 0x00007fd33fc96fae g_main_context_iteration (libglib-2.0.so.0) #5 0x00007fd347d046b4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #6 0x00007fd347ca682b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #7 0x00007fd347ab678e _ZN7QThread4execEv (libQt5Core.so.5) #8 0x00007fd349d7ca19 n/a (libQt5Qml.so.5) #9 0x00007fd347abbb2d n/a (libQt5Core.so.5) #10 0x00007fd341e9508a start_thread (libpthread.so.0) #11 0x00007fd3473c342f __clone (libc.so.6) Stack trace of thread 4528: #0 0x00007fd3473b8f2b __poll (libc.so.6) #1 0x00007fd33fc96ed3 n/a (libglib-2.0.so.0) #2 0x00007fd33fc96fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fd347d046b4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fd347ca682b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fd347ab678e _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fd3488e5416 n/a (libQt5DBus.so.5) #7 0x00007fd347abbb2d n/a (libQt5Core.so.5) #8 0x00007fd341e9508a start_thread (libpthread.so.0) #9 0x00007fd3473c342f __clone (libc.so.6) Steps to reproduce: - In KDE menu, click the button to trigger Shutdown of the computer. - When the confirmation screen appears, the system freezes |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 15 January 2018, 16:46 GMT
Reason for closing: Not a bug
Additional comments about closing: Config issue
Monday, 15 January 2018, 16:46 GMT
Reason for closing: Not a bug
Additional comments about closing: Config issue
Having a problem directly in Intel driver explains why plasmashell also started to randomly crash too.
If that doesn't help, ensure that all of mesa is build with debug symbols - the new "n/a (i915_dri.so)" line will contain very important information.
By digging, I noticed the X conf was forcing the "uxa" method. After removing this line, it looks like everything works for 2 weeks.
Problem solved, thank you for your help!