gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension

Bug #1813173 reported by Kostadin Stoilov
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gpaste (Ubuntu)
Confirmed
High
Unassigned

Bug Description

https://errors.ubuntu.com/problem/ced4a4eb6e94763756d8b463a6135c31dd711619

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 24 16:34:05 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-04-29 (999 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7fa4603b6021 <clutter_container_get_child_meta+17>: mov (%rbx),%rdi
 PC (0x7fa4603b6021) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 clutter_container_get_child_meta () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/libgjs.so.0
 () at /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
UpgradeStatus: Upgraded to bionic on 2018-08-04 (173 days ago)
UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Kostadin Stoilov (kmstoilov) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clutter_container_get_child_meta (container=0x0, actor=0x55db499c7480) at clutter-container.c:973
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55db41f47eb8, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7fff6837ecf8, avalue=avalue@entry=0x7fff6837ebe0) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=context@entry=0x55db41795240, function=function@entry=0x55db41f47ea0, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1088
 function_call (context=context@entry=0x55db41795240, js_argc=1, vp=0x7fff6837f278) at gi/function.cpp:1406

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
tags: added: cosmic
Revision history for this message
Kostadin Stoilov (kmstoilov) wrote :

Hi,
This crash is still present in the latest gnome-shell version 3.28.4-0ubuntu18.04.1

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

It appears this crash is not very common, suggesting it might be related to some extension(s).

You seem to have installed:

'<email address hidden>'
'<email address hidden>'
'<email address hidden>'

so please try uninstalling those completely, and tell us if the crash still occurs.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Download full text (4.6 KiB)

The attached file JournalErrors.txt suggests the GPaste extension might be the most suspicious extension:

яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 ==
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837e650 I resource:///org/gnome/shell/ui/environment.js:41 (0x7fa438386d58 @ 20)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x7fff6837e740 b resource:///org/gnome/shell/ui/popupMenu.js:658 (0x7fa438123d58 @ 202)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #2 0x7fff6837e7b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa4383b5de0 @ 71)
яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #3 0x55db418d30d0 i /<email address hidden>/indicator.js:323 (0x7fa4180bf5e8 @ 48)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #4 0x7fff6837f3a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa4383b5de0 @ 71)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #5 0x55db418d3030 i /<email address hidden>/indicator.js:90 (0x7fa4180b75e8 @ 274)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 ==
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:41 (0x7fa438386d58 @ 20)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x55db418d3030 i /<email address hidden>/indicator.js:92 (0x7fa4180b75e8 @ 332)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 ==
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:32 (0x7fa438386cd0 @ 26)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:43 (0x7fa438386d58 @ 50)
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #2 0x55db418d3030 i /<email address hidden>/indicator.js:92 (0x7fa4180b75e8 @ 332)
яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_get_children: assertion 'CLUTTER_IS_CONTAINER (container)' failed
яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
яну 24 16:34:05 hostname gnome-shell[30607]:...

Read more...

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, that does seem to be the problem, most likely. The only calls to 'get_child_meta' in gnome-shell are in environment.js, which seems to be called from the GPaste extension per the above comment.

I recommend uninstalling the GPaste extension.

Revision history for this message
Kostadin Stoilov (kmstoilov) wrote :

Hi,
I've been running without the gpaste extension for a few weeks and gnome-shell no longer crashes.
So I guess this bug should be reassigned?

summary: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
+ when using the GPaste extension
description: updated
Changed in gnome-shell (Ubuntu):
importance: Medium → Low
status: Incomplete → Confirmed
Changed in gpaste (Ubuntu):
status: New → Confirmed
importance: Undecided → High
tags: removed: cosmic
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two crashes, one with emptying history and one with image support.

no longer affects: gnome-shell (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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