Ubuntu
gnome-shell package

gnome-shell UI unresponsive

Bug #1787362 reported by Peter Hicks
16
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Whilst working normally, I was unable to interact with gnome-shell. The clock at the top of the screen continued to increment, and I could ssh in to the machine, but clicking anywhere on the screen resulted in nothing. Changing to another VTY and back again had no effect.

I logged in via ssh, killed gnome-shell and re-ran it using 'DISPLAY=:0.0 gnome-shell' which resolved the problem enough for me to save work and reboot.

The following appeared in syslog - the crash was possibly around 1001:

Aug 16 10:02:17 angel gnome-shell[2530]: pushModal: invocation of begin_modal failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: message repeated 2 times: [ g_array_unref: assertion 'array' failed]
Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it.
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it.
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:59 (0x7f1d3c555b38 @ 212)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:60 (0x7f1d3c555b38 @ 274)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:65 (0x7f1d3c555b38 @ 365)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7f1cc1869ab0 @ 84)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StBin 0x55efdec45f10.
Aug 16 10:11:43 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 ==
Aug 16 10:11:43 angel org.gnome.Shell.desktop[2530]: message repeated 50 times: [ == Stack trace for context 0x55efd9792340 ==]
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StBin 0x55efdec34860.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StBin 0x55efda389920.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StBin 0x55efe24c3860.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StButton 0x55efdcbaed40.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StButton 0x55efdcbaed40.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was actor-removed on ShellGenericContainer 0x55efdb998850.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StBin 0x55efde75e500.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StButton 0x55efdf295080.
Aug 16 10:11:43 angel gnome-shell[2530]: 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.
Aug 16 10:11:43 angel gnome-shell[2530]: The offending signal was destroy on StButton 0x55efdf295080.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 10:17:23 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 18.20-606296, 4.15.0-30-generic, x86_64: installed
 amdgpu, 18.20-606296, 4.15.0-32-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-30-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d]
InstallationDate: Installed on 2018-08-04 (11 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=45683c84-9181-434c-8c1c-7054f51356f5 ro quiet splash amdgpu.dc=0 vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X299-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/21/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
Peter Hicks (poggs) wrote :
Daniel van Vugt (vanvugt)
summary: - gnome-shell crash, UI unresponsive
+ gnome-shell UI unresponsive
affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
tags: added: no-click
tags: added: noclick
removed: no-click
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

1. Please try removing all extensions you have installed. Gnome Shell extensions are a major cause of bugs.

2. Do you find that it's only clicking on app windows that is affected? When the problem happens can you still click on the shell panel/docks?

3. Is the problem confined to only Wayland sessions, or only Xorg sessions? Does it occur in both?

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Nikolay Petrov (nikilp) wrote :
Download full text (22.0 KiB)

I experience very similar situation.

1. I have only one active Gnome Shell extension: "Disable Gestures" which gives me a desirable feature - to disable all multi-finger touch screen gestures.
I just disabled it to see if that will resolve the issue.

2. Indeed, I found that sometimes clicking on app windows is affected, but the shell panel - not.

3. I have not tried Xorg sessions while this occurs. I will on next occasion.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

$ uname -a
Linux teabreak-3 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linu

From /var/log/syslog:
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #1 0x564764c1e828 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fba380b5de0 @ 71)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #2 0x564764c1e7a8 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7fb9f2e6c340 @ 59)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #3 0x564764c1e700 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fba380b5de0 @ 71)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #4 0x564764c1e640 i self-hosted:916 (0x7fba380f12b8 @ 367)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: == Stack trace for context 0x564764791330 ==
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #0 0x564764c1e7a8 i resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7fb9f2e6c340 @ 84)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #1 0x564764c1e700 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fba380b5de0 @ 71)
Aug 30 17:53:31 ubuntu18 org.gnome.Shell.desktop[1166]: #2 0x564764c1e640 i self-hosted:916 (0x7fba380f12b8 @ 367)
Aug 30 17:53:31 ubuntu18 gnome-shell[1166]: Object St.Bin (0x5647680732a0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 30 17:53:31 ubuntu18 gnome-shell[1166]: Object St.Bin (0x5647680732a0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 30 17:54:40 ubuntu18 vnstatd[894]: Error: Unable to create database backup "/var/lib/vnstat/.enp2s0".
Aug 30 17:54:40 ubuntu18 vnstatd[894]: Error: Unable to create database backup "/var/lib/vnstat/.wlx503eaa5fe4b0".
Aug 30 17:59:40 ubuntu18 vnstatd[894]: Error: Unable to create database backup "/var/lib/vnstat/.enp2s0".
Aug 30 17:59:40 ubuntu18 vnstatd[894]: Error: Unable to create database backup "/var/lib/vnstat/.wlx503eaa5fe4b0".
Aug 30 17:59:47 ubuntu18 dbus-daemon[1016]: [session uid=1000 pid=1016] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.33' (uid=1000 pid=1166 comm="/usr/bin/gnome-shell " label="unconfined")
Aug 30 17:59:48 ubuntu18 dbus-daemon[1016]: [session uid=1000 pid=1016] Activating service name='org.gnome.Nautilus' requested by ':1.33' (uid=10...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. #2 suggests this is a duplicate of bug 1181666.

Revision history for this message
Nikolay Petrov (nikilp) wrote :

Update:
1. Disabling the Gnome Shell extensions all together didn't resolve the issue
3. Xorg sessions also are not responsive

I'm now testing cinnamon and so far the system is behaving stable.

Revision history for this message
Noam Manos (n.manos) wrote :

This "Gnome freeze" bug happens on my RHEL 7.6 with gnome-shell-3.28.3-6.el7.x86_64.

It happens once in a while (daily), that gnome freezes for couple of minutes (!). I can move the mouse, and I see the seconds of the clock changing, but the mouse or keyboard clicks has no response.

- I've also tried to disable all extensions, but it was not fixed.

- Interesting to note that it sometimes (not always) happens when WiFi has bad connection. Then, when gnome is back to normal, I see "Activation of Network Connection failed" message on top.

Here's some of the common journal errors/failures I see right after gnome freeze:

- pushModal: invocation of begin_modal failed
- g_array_unref: assertion 'array' failed
- GoaAlarm: failed to read from timer fd: Error reading from file descriptor: Operation canceled
- kernel: usb 2-3: Disable of device-initiated U1 failed.
- kernel: usb 2-3: Disable of device-initiated U2 failed.
- kernel: usb 2-3: usb_reset_and_verify_device Failed to disable LTM
- g_simple_action_set_enabled: assertion 'G_IS_SIMPLE_ACTION (simple)' failed
- JS ERROR: TypeError: connectionSettings is null
- clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
- g_object_set: assertion 'G_IS_OBJECT (object)' failed

Attaching journal logs I took right after such gnome freezes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.