Bug 1897063

Summary: gnome-shell killed by SIGSEGV - Execution of main.js threw exception: Script <main> terminated with an uncatchable exception [rhel-7.9.z]
Product: Red Hat Enterprise Linux 7 Reporter: amit yadav <ayadav>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.9CC: bugreports2005, dazo, fmuellner, jadahl, jkoten, jreznik, jrfuller, jwboyer, lersek, lszubowi, mboisver, modehnal, nixuser, rodney.mckee, rstrode, sbarcomb, skpaul, tpopela
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gnome-shell-3.28.3-32.el7 gdm-3.28.2-26.el7 mutter-3.28.3-30.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-18 18:24:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gnome-shell in gdb none

Description amit yadav 2020-11-12 08:24:30 UTC 
Description of problem:

gnome-shell killed by SIGSEGV after RHEL7.9.z update. Getting blank screen on system console and in the vnc session.

rhel7.9 ~]# abrt-cli list --since 1604892202
id 9edb177c3072e68cc202942d0338bce0fa750f5f
reason:         gnome-shell killed by SIGSEGV
time:           Thu 12 Nov 2020 11:28:17 AM IST
cmdline:        /usr/bin/gnome-shell
package:        gnome-shell-3.28.3-31.el7
uid:            1000 (testadmin)
count:          2
Directory:      /var/spool/abrt/ccpp-2020-11-12-11:28:17-31393
Run 'abrt-cli report /var/spool/abrt/ccpp-2020-11-12-11:28:17-31393' for creating a case in Red Hat Customer Portal

Getting following errors in the logs:

Nov 12 11:28:17 rhel7.9 kernel: traps: gnome-shell[31393] general protection ip:7f88d467fa5d sp:7ffdac4bd108 error:0 in libgobject-2.0.so.0.5600.1[7f88d464d000+4f000]
Nov 12 11:28:17 rhel7.9 systemd[1]: Started Flexible Branding Service.
Nov 12 11:28:17 rhel7.9 abrt-hook-ccpp[31713]: Process 31393 (gnome-shell) of user 1000 killed by SIGSEGV - dumping core
Nov 12 11:28:18 rhel7.9 systemd[1]: Reloading.
Nov 12 11:28:18 rhel7.9 polkitd[701]: Unregistered Authentication Agent for unix-session:282 (system bus name :1.1047, object path /org/freedesktop/PolicyKit1/AuthenticationAge
Nov 12 11:28:18 rhel7.9 gnome-session-binary[31184]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Nov 12 11:28:18 rhel7.9 gnome-session[31184]: gnome-session-binary[31184]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Nov 12 11:28:18 rhel7.9 systemd[1]: Started Flexible Branding Service.
Nov 12 11:28:18 rhel7.9 org.gnome.Shell.desktop[31751]: Xlib:  extension "DPMS" missing on display ":0".
Nov 12 11:28:18 rhel7.9 org.gnome.Shell.desktop[31751]: Xlib:  extension "DPMS" missing on display ":0".
Nov 12 11:28:20 rhel7.9 polkitd[701]: Registered Authentication Agent for unix-session:282 (system bus name :1.1059 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyK
Nov 12 11:28:20 rhel7.9 gnome-shell[31751]: Script <main> terminated with an uncatchable exception
Nov 12 11:28:20 rhel7.9 gnome-shell[31751]: Execution of main.js threw exception: Script <main> terminated with an uncatchable exception
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.

Nov 12 11:28:21 rhel7.9 org.gnome.Shell.desktop[31751]: == Stack trace for context 0xee40a0 ==
Nov 12 11:28:21 rhel7.9 org.gnome.Shell.desktop[31751]: == Stack trace for context 0xee40a0 ==
Nov 12 11:28:21 rhel7.9 org.gnome.Shell.desktop[31751]: == Stack trace for context 0xee40a0 ==
Nov 12 11:28:21 rhel7.9 org.gnome.Shell.desktop[31751]: == Stack trace for context 0xee40a0 ==
Nov 12 11:28:21 rhel7.9 org.gnome.Shell.desktop[31751]: == Stack trace for context 0xee40a0 ==
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: The offending signal was destroy on StBoxLayout 0x2319670.
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
 
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: The offending signal was destroy on Gjs_ShowAppsIcon 0x231a930.
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
 
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: The offending signal was destroy on StBin 0x2320260.
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
 
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: The offending signal was destroy on StButton 0x231d7d0.
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
 
Nov 12 11:28:21 rhel7.9 gnome-shell[31751]: The offending signal was destroy on StBin 0x269f340.

Nov 12 11:28:21 rhel7.9 kernel: traps: gnome-shell[31751] general protection ip:7f6beae13a5d sp:7ffea1a08508 error:0 in libgobject-2.0.so.0.5600.1[7f6beade1000+4f000]
Nov 12 11:28:21 rhel7.9 abrt-hook-ccpp[31840]: Process 31751 (gnome-shell) of user 1000 killed by SIGSEGV - ignoring (repeated crash)
Nov 12 11:28:21 rhel7.9 abrt-hook-ccpp[31840]: Saved core dump of pid 31751 to core.31751 at /home/testadmin (10240000 bytes)
Nov 12 11:28:21 rhel7.9 polkitd[701]: Unregistered Authentication Agent for unix-session:282 (system bus name :1.1059, object path /org/freedesktop/PolicyKit1/AuthenticationAge
Nov 12 11:28:21 rhel7.9 gnome-session-binary[31184]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Nov 12 11:28:21 rhel7.9 gnome-session-binary[31184]: Unrecoverable failure in required component org.gnome.Shell.desktop
Nov 12 11:28:21 rhel7.9 gnome-session[31184]: gnome-session-binary[31184]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Nov 12 11:28:21 rhel7.9 gnome-session[31184]: gnome-session-binary[31184]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Nov 12 11:28:21 rhel7.9 gnome-session-binary[31184]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Nov 12 11:28:21 rhel7.9 gnome-session-f[31842]: Cannot open display: 


Version-Release number of selected component (if applicable):
gnome-shell-3.28.3-31.el7

How reproducible:
Always

Steps to Reproduce:
1. Update system with the latest RHEL7.9.z update. 
2. Check the system console or try to access the system via vnc.

Actual results:
gnome-shell crashed, getting blank screen

Expected results:

gnome-shell should not crash

Additional info:

The issue is easily reproducible. 

Workaround:

Downgrade the gnome-shell package to previous version gnome-shell-3.28.3-30.el7.x86_64 to fix the issue.

Optionally, launch GUI using startx command.
Comment 4 Michal Odehnal 2020-11-12 09:04:15 UTC 
Created attachment 1728655 [details]
gnome-shell in gdb

Tried starting gnome-shell in gdb.
Comment 6 Skip Paul 2020-11-12 13:47:11 UTC 
I can replicate this issue as well.  I can also confirm that downgrading to gnome-shell-3.28.3-30.el7.x86_64 fixes things.
Comment 7 Ray Strode [halfline] 2020-11-12 15:04:47 UTC 
*** Bug 1897045 has been marked as a duplicate of this bug. ***
Comment 32 David Sommerseth 2020-11-13 19:43:18 UTC 
I am having the exact same issue on both a ThinkPad T460 (Scientific Linux 7.9) and T450s (Red Hat Enterprise Server 7.9).  Downgrading from gnome-shell-3.28.3-31.el7.x86_64 to gnome-shell-3.28.3-30.el7.x86_64 resolved the issue.
Comment 33 Tomas Pelka 2020-11-16 09:41:16 UTC 
*** Bug 1898050 has been marked as a duplicate of this bug. ***
Comment 36 bugreports2005 2020-11-17 09:47:49 UTC 
Same here. Had to downgrade.
gnome classic worked, though.
Comment 38 Jonas Ådahl 2020-11-18 10:04:50 UTC 
*** Bug 1898658 has been marked as a duplicate of this bug. ***
Comment 44 errata-xmlrpc 2020-11-18 18:24:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (GNOME bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5154