RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1743913 - gnome-shell crashes with signal 11
Summary: gnome-shell crashes with signal 11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jonas Ådahl
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-21 01:08 UTC by Johnray Fuller
Modified: 2020-03-31 19:40 UTC (History)
3 users (show)

Fixed In Version: gnome-shell-3.28.3-15.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:39:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screencast from reproducing the bug before component update (2.51 MB, application/octet-stream)
2019-09-05 14:52 UTC, Pavlin Georgiev 		no flags Details
System journal from automated testing under RHEL 7.7 (6.36 MB, text/plain)
2019-09-07 07:48 UTC, Pavlin Georgiev 		no flags Details
monitors.xml file (37.04 KB, text/plain)
2019-09-10 13:45 UTC, Johnray Fuller 		no flags Details
Tweak Tool screenshots (645.61 KB, application/x-xz)
2019-09-10 13:53 UTC, Johnray Fuller 		no flags Details
Automatic start of applications in GNOME session under RHEL 8.0.0 (107.14 KB, image/png)
2019-09-12 13:17 UTC, Pavlin Georgiev 		no flags Details
Moving app windows to between screens (4.48 MB, application/octet-stream)
2019-09-12 13:19 UTC, Pavlin Georgiev 		no flags Details
System journal from reproducing the bug under RHEL 8.0.0 (5.87 MB, text/plain)
2019-09-12 13:55 UTC, Pavlin Georgiev 		no flags Details
System journal from reproducing the bug under RHEL 7.6 (2.22 MB, text/plain)
2019-09-12 16:58 UTC, Pavlin Georgiev 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-shell/issues/539 0 None None None 2019-09-05 08:06:14 UTC
Red Hat Product Errata RHSA-2020:1021 0 None None None 2020-03-31 19:40:19 UTC

Description Johnray Fuller 2019-08-21 01:08:45 UTC 
Description of problem:

Periodically, gnome-shell crashes with a sig 11. This happens once or twice per day.


Version-Release number of selected component (if applicable):

# rpm -q gnome-shell
gnome-shell-3.28.3-11.el7.x86_64


How reproducible:

I have not linked the crashes to a particular action. It *may* happen when switching to a different work space or maybe a different window?h


Steps to Reproduce:
1. Working on my desktop
2. gnome-shell crashes with a sig 11, then comes back.
3. <repeat>

Actual results:
gnome-shell crashes with a sig 11.

Expected results:

Shouldn't crash...


Additional info:

The following is a backtrace on a recent incident.

(gdb) bt
#0  0x00007f1113711d10 in meta_window_actor_is_destroyed (self=0x0) at compositor/meta-window-actor.c:936
#1  0x00007f110ffc5dcc in ffi_call_unix64 () at ../src/x86/unix64.S:76
#2  0x00007f110ffc56f5 in ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=0x7ffed5d7c540, avalue=0x7ffed5d7c420) at ../src/x86/ffi64.c:522
#3  0x00007f11141d4920 in gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) (context=context@entry=0x1811000, function=function@entry=0x7f1088030920, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1088
#4  0x00007f11141d613b in function_call(JSContext*, unsigned int, JS::Value*) (context=context@entry=0x1811000, js_argc=0, vp=0x1962c68) at gi/function.cpp:1408
#5  0x00007f110bae3527 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (args=..., native=
    0x7f11141d5fd0 <function_call(JSContext*, unsigned int, JS::Value*)>, cx=0x1811000) at /usr/src/debug/firefox-52.9.0esr/js/src/jscntxtinlines.h:239
#6  0x00007f110bae3527 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x1811000, args=..., construct=js::NO_CONSTRUCT)
    at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:447
#7  0x00007f110bad6ea5 in Interpret(JSContext*, js::RunState&) (args=..., cx=<optimized out>) at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:510
#8  0x00007f110bad6ea5 in Interpret(JSContext*, js::RunState&) (cx=0x1811000, state=...) at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:2922
#9  0x00007f110bae3059 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x1811000, state=...) at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:405
#10 0x00007f110bae32c0 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=cx@entry=0x1811000, args=..., construct=construct@entry=js::NO_CONSTRUCT)
    at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:477
#11 0x00007f110bae35c8 in InternalCall(JSContext*, js::AnyInvokeArgs const&) (cx=cx@entry=0x1811000, args=...) at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:504
#12 0x00007f110bae3629 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) (cx=cx@entry=0x1811000, fval=..., 
    fval@entry=..., thisv=..., args=..., rval=..., rval@entry=...) at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:523
#13 0x00007f110b8d1c4d in js::jit::InvokeFunction(JSContext*, JS::Handle<JSObject*>, bool, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>) (cx=0x1811000, obj=..., constructing=<optimized out>, argc=<optimized out>, argv=0x7ffed5d7d6f0, rval=...) at /usr/src/debug/firefox-52.9.0esr/js/src/jit/VMFunctions.cpp:114
#14 0x000012768e0ad99c in  ()
#15 0x00007ffed5d7d6a0 in  ()
#16 0x00007ffed5d7d6a0 in  ()
Python Exception <type 'exceptions.OverflowError'> long too big to convert: 
#17 0xffffffffffffffff in  ()#18 0x00007f110cbf5be0 in js::jit::InvokeFunctionInfo () at /usr/lib64/libmozjs-52.so.0.0.0
#19 0x00007f10e04739a0 in  ()
#20 0x000012768e45d8a6 in  ()
#21 0x0000000000006820 in  ()
#22 0x00007f10c49188d0 in  ()
#23 0x0000000000000000 in  ()
Comment 2 Johnray Fuller 2019-08-21 01:10:54 UTC 
This is similar to the following centos bug: 

https://bugs.centos.org/view.php?id=16220
Comment 3 Jonas Ådahl 2019-09-05 08:06:14 UTC 
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/539
Upstream fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/223
Comment 5 Pavlin Georgiev 2019-09-05 11:48:09 UTC 
TEST SETUP
Hardware:
  Laptop Lenovo T580
  Docking station
  2 monitors NEC 23" connected to the docking station via DisplayPort
  Graphics card: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)

  
Distro: RHEL 7.6 CSB
Component version: gnome-shell-3.28.3-8.el7_6
I use 3 workspaces in the GNOME session.


TEST PROCEDURE
1. Start several applications:
  - firefox
  - gnome-terminal
  - gedit
  - gnote
  - evince
  
2. For each application:
  Move and align the window to the left of 1st monitor.
  Move and align the window to the right of the 1st monitor.
  Move and align the window to the left of 2nd monitor.
  Move and align the window to the right of 2nd monitor.
  Minimize
  Maximize

3. Change the screen resolution on both monitors:
  from: 1920x1080
    to: 1280x720
    
4. Repeat step 2.
5. Close all applications.


RESULT
I cannot reproduce the bug on that testing system.
Comment 6 Pavlin Georgiev 2019-09-05 14:52:02 UTC 
Created attachment 1612013 [details]
Screencast from reproducing the bug before component update

TEST SETUP 2
Hardware: HP Z200 Workstation
Distro: RHEL 7.7
Component version: gnome-shell-3.28.3-11.el7

Graphics card: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02)


TEST PROCEDURE 2
1. Start several applications:
  - firefox
  - gnome-terminal
  - gedit
  - gnote
  - evince
  
2. For each application:
  Move and align the window to the left of the screen.
  Move and align the window to the right of the screen.
  Minimize
  Maximize
  Drag the window to lower workspace with CTRL+ALT+SHIFT+DOWN
  until the bottom workspace is reached.
  Drag the window to upper workspace with CTRL+ALT+SHIFT+UP
  until the top workspace is reached.
  Close the tested application.


RESULT 2
I cannot reproduce the bug on that system.
Comment 7 Pavlin Georgiev 2019-09-05 14:55:15 UTC 
TEST SETUP 3
Hardware: HP Z400 Workstation
Distro: RHEL 7.7
Component version: gnome-shell-3.28.3-11.el7

Graphics card: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)


TEST PROCEDURE 3
Repeat the last testing procedure.


RESULT 3
I cannot reproduce the bug on that system.
Comment 8 Pavlin Georgiev 2019-09-05 14:57:09 UTC 
TEST SETUP 4
Hardware: Dell Precision T5400
Distro: RHEL 7.7
Component version: gnome-shell-3.28.3-11.el7

Graphics card: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)


TEST PROCEDURE 4
Repeat the last testing procedure.


RESULT 4
I cannot reproduce the bug on that system.
Comment 9 Pavlin Georgiev 2019-09-05 14:59:55 UTC 
TEST SETUP 5
Hardware: HP xw4600 Workstation
Distro: RHEL 7.7
Component version: gnome-shell-3.28.3-11.el7

Graphics card: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2)


TEST PROCEDURE 5
Repeat the last testing procedure.


RESULT 5
I cannot reproduce the bug on that system.
Comment 10 Pavlin Georgiev 2019-09-07 07:48:13 UTC 
Created attachment 1612605 [details]
System journal from automated testing under RHEL 7.7

TEST SETUP 6
Hardware: PC HP xw4600 Workstation
Distro: RHEL 7.7
Component version: gnome-shell-3.28.3-11.el7

Graphics card: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2)


TEST PROCEDURE 6
1. Start automating testing of component control-center:
   https://gitlab.cee.redhat.com/desktopqe/control-center
2. Start a Beaker job which executes more than 100 tests.
   Before each test, GDM is started, GNOME session is started.
   At the end of the test, GDM is stopped.
   Thus, multiple start/stop of GNOME session is tested together with gnome-shell.
3. Collect the system journal.
4. Check the journal for the bug.
The bug does NOT appear.


RESULT 6
I cannot reproduce the bug on that system.
Comment 11 Pavlin Georgiev 2019-09-07 07:48:39 UTC 
Beaker job for automated testing:
https://beaker.engineering.redhat.com/jobs/3768699
Comment 12 Pavlin Georgiev 2019-09-07 08:38:57 UTC 
TEST SETUP 7
Hardware: PC HP Z400 Workstation
Distro: RHEL-7.8-20190905.0
Component version: gnome-shell-3.28.3-14.el7

Graphics card: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1)

TEST PROCEDURE 7
Repeat the first testing procedure (from comment #5).


RESULT 7
I cannot reproduce the bug on that system.
Comment 13 Pavlin Georgiev 2019-09-09 06:33:02 UTC 
I cannot reproduce the bug on the new RPM packages.
So, I set status VERIFIED.
Comment 14 Johnray Fuller 2019-09-10 13:43:45 UTC 
Hello,

I was asked the following regarding this issue:

Questions:

    What model is your PC or laptop?

> I have a T470s Lenovo with the latest BIOS.

    If laptop do you have docking station?

> Yes. I can get the model tomorrow, but it's the standard base station.

    How many external monitor do you use?

> I use one external monitor (from Dell) connected via the docking station.

Send me the config of monitors in GNOME:

$HOME/.config/monitors.xml

> I will attach this.

Install gnome-tweaks.
Start gnome-tweaks.
Send me screenshots of each section.

> I will upload them as well.

Thus, I will set up the testing system in the same way.
Comment 15 Johnray Fuller 2019-09-10 13:45:40 UTC 
Created attachment 1613599 [details]
monitors.xml file

Attaching monitors.xml file
Comment 17 Johnray Fuller 2019-09-10 13:53:49 UTC 
Created attachment 1613601 [details]
Tweak Tool screenshots

Tweak Tool screenshots
Comment 18 Johnray Fuller 2019-09-11 02:18:26 UTC 
Hello,

I wanted to add a few details.

1) This issue happens whether or not my system is using the external monitor.
2) I can't predict when it will happen *BUT* it seems to happen whenever Gnome switches work spaces.
   - I have four work spaces
   - If an alert comes up in the alert box and the application issuing the alert is in another workspace (e.g. a private message in hexchat or calendar event), then the crash sometimes occurs when I click the alert and it switches work spaces.

I don't recall it happening if I *don't* switch work spaces, but will monitor this and let you know.

Johnray
Comment 19 Jonas Ådahl 2019-09-11 06:37:27 UTC 
FWIW, the applied fix handles windows being destroyed during a workspace switch. It could be so that if you time closing a window to happen during a workspace switch, you might be able to reproduce it.
Comment 20 Pavlin Georgiev 2019-09-12 09:52:40 UTC 
I have borrowed laptop Lenovo T470s from our IT department in Brno.
I will test on that hardware to check for the bug.
Comment 21 Pavlin Georgiev 2019-09-12 12:53:02 UTC 
TEST SETUP 8
Hardware: laptop Lenovo T470s
Docking station
2 ext.monitors NEC 23" connected to the dock via DisplayPort
Graphics card: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)

Distro: RHEL 8.0.0 CSB
Component version: gnome-shell-3.28.3-10.el8


TEST PROCEDURE 8
1. Set automatic start of multiple applications via gnome-tweaks.
2. For each application:
  Move and align the window to the left of 1st monitor.
  Move and align the window to the right of the 1st monitor.
  Move and align the window to the left of 2nd monitor.
  Move and align the window to the right of 2nd monitor.
  Move the app windows to the 1st monitor.
  Minimize.
  Maximize.
  Move the app window down to the bottom (4th) workspace.
  Move the app window up to the top workspace.
  Close.


RESULT 8
I cannot reproduce the bug on that system.
Comment 22 Pavlin Georgiev 2019-09-12 13:17:12 UTC 
Created attachment 1614516 [details]
Automatic start of applications in GNOME session under RHEL 8.0.0
Comment 23 Pavlin Georgiev 2019-09-12 13:19:33 UTC 
Created attachment 1614517 [details]
Moving app windows to between screens

TEST SETUP 9
Hardware: laptop Lenovo T470s
Docking station
2 ext.monitors NEC 23" connected to the dock via DisplayPort
Graphics card: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)

Distro: RHEL 8.0.0 CSB
Component version: gnome-shell-3.28.3-10.el8


TEST PROCEDURE 9
1. After all startup applications run (attachment 1614516 [details]), press Super key.
2. Move all app windows from right to left monitor (primary -> secondary).
3. Move all app windows from left to right monitor (secondary -> primary).


RESULT 9
The is no hang, no freeze, no side effect.
Comment 24 Pavlin Georgiev 2019-09-12 13:55:13 UTC 
Created attachment 1614529 [details]
System journal from reproducing the bug under RHEL 8.0.0

TEST PROCEDURE 10
1. Install GNOME shell integration from https://extensions.gnome.org/
   by using Cmake installation:
 https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation#Cmake_installation

2. Install shell extensions:
    - Openweather
    - Removable driver menu
    - Show desktop button
    - System monitor
    - Systemmonitor
    - Workspace indicator
    - System-monitor

3. Set up the system via gnome-tweaks according to user's preferences listed in  attachment 1613601 [details].
4. Log out.
5. Log in a GNOME session.
6. Repeat the steps from TEST PROCEDURE 8 (comment 21).


RESULT 10
I cannot reproduce the bug on that system.
Comment 25 Pavlin Georgiev 2019-09-12 16:48:01 UTC 
TEST SETUP 11
Hardware: laptop Lenovo T470s
Docking station
1 ext.monitor DELL 19" connected to the dock via DVI port
Graphics card: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)

Distro: RHEL 7.6 CSB
Component version: gnome-shell-3.28.3-8.el7_6


TEST PROCEDURE 11
1. Install GNOME shell integration from https://extensions.gnome.org/
   by using Cmake installation:
   https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation#Cmake_installation
2. Install shell extensions:
    - Openweather
    - Removable driver menu
    - Show desktop button
    - System monitor
    - Systemmonitor
    - Workspace indicator
    - System-monitor

3. Set up the system via gnome-tweaks according to user's preferences listed in attachment 1613601 [details].
4. Log out.
5. Log in a GNOME session.
6. Repeat the steps on a single monitor from TEST PROCEDURE 2 (comment 6).


RESULT 11
I cannot reproduce the bug on that system.
Comment 26 Pavlin Georgiev 2019-09-12 16:58:40 UTC 
Created attachment 1614603 [details]
System journal from reproducing the bug under RHEL 7.6
Comment 28 errata-xmlrpc 2020-03-31 19:39:53 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, 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/RHSA-2020:1021
Note You need to log in before you can comment on or make changes to this bug.