10/24/2016 · Bug 1388252 – [abrt] gnome-session: gnome- session-check-accelerated -helper killed by SIGSEGV . Summary: [abrt] gnome-session: gnome- session-check-accelerated -helper killed by SIGSEGV.
1/28/2020 · gnome – session – check – accelerated: GLES Helper exited with code 256. gnome – session – binary [10890]: WARNING: Using null backend for session tracking. _IceTransmkdir: Owner of / tmp /..
6/8/2017 · Jun 07 13:54:11 archlap gnome-session[824]: gnome- session-check-accelerated: GL Helper exited with code 256 Jun 07 13:54:11 archlap gnome-session[824]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/4.11.3-1-ARCH Jun 07 13:54:16 archlap gnome-session[824]: gnome- session-check-accelerated : GLES Helper exited with code 256, 17 rows · 0014898: [abrt] gnome-session: _g_log_abort(): gnome- session-check-accelerated killed .
10/22/2017 · After installing 17.10, ubuntu restricted extras, lowlatency kernel, and applying all updates and rebooting, GDM fails to start. Here are some relevant log entries: Oct 21 14:27:24 olympia gnome-session [2984]: gnome- session-check-accelerated: GL Helper exited with code 256 Oct 21 14:27:24 olympia gnome-session-c [3030]: eglGetDisplay () failed Oct …
3/21/2014 · Script for default started at run_im. gnome-session-is-accelerated: GL_MAX_{TEXTURE,RENDERBUFFER}_SIZE is too small. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: GL_MAX_{TEXTURE,RENDERBUFFER}_SIZE is too small. gnome-session-check-accelerated: Helper exited with code 256 ** (process:2338): WARNING **: software acceleration check failed: Child process exited with code 1 ** (x-session-manager:2338): CRITICAL **: We failed, but the fail whale is dead .
reason: gnome-shell killed by SIGSEGV time: Thu 30 May 2019 07:45:09 AM MDT cmdline: /usr/bin/gnome-shell package: gnome-shell-3.28.3-6.el7 uid: 42 (gdm) count: 8 Directory: /var/spool/abrt/ccpp-2019-05-30-07:45:09-8074, 5/16/2017 · reason: gnome-settings-daemon killed by SIGTRAP time: Mon 08 May 2017 09:00:28 AM CDT cmdline: /usr/libexec/gnome-settings-daemon package: gnome-settings-daemon-3.14.4-9.el7 uid: 640 (dke987) count: 1 Directory: /var/spool/abrt/ccpp-2017-05-08-09:00:28-5194 Here’s what journalctl -b /usr/bin/gnome-session shows:, ????? reason: gnome- session-check-accelerated-gl -helper killed by SIGSEGV time: Thu 24 Jan 2019 11:59:12 AM CST cmdline: /usr/libexec/gnome- session-check-accelerated-gl -helper –print-renderer package: gnome-session-3.28.1-6.el7 ?????? /usr/libexec/gnome- session-check-accelerated-gl -helper –print-renderer ??????, It only showed the output prompt. Turns out it was due to the terminal settings. For some reasons, after logging out of kubectl exec, the next exec would get 0 rows and 0 columns as if someone had run stty rows 0 on the terminal. And of course, this wasn’t reliably reproducible, but happened often enough.
