Public bug reported:
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787362
Title:
gnome-shell crash, UI unresponsive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1787362/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
