gnome-shell crashed with SIGSEGV in clutter_actor_is_visible()

Bug #1726827 reported by Kyle Gracey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crashed during resume from suspend.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Oct 24 06:50:44 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-11-15 (343 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f8b26803c46 <clutter_actor_is_visible+22>: cmp %rax,(%rdx)
 PC (0x7f8b26803c46) ok
 source "%rax" ok
 destination "(%rdx)" (0x4455e9fdf6e410) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 clutter_actor_is_visible () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 ?? () from /usr/lib/gnome-shell/libst-1.0.so
 ?? () from /usr/lib/gnome-shell/libst-1.0.so
Title: gnome-shell crashed with SIGSEGV in clutter_actor_is_visible()
UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Kyle Gracey (kylegracey) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clutter_actor_is_visible (self=0x55e9feb86870) at clutter-actor.c:1791
 count_expand_children (layout=layout@entry=0x55e9feb6a270, container=container@entry=0x55e9feb80050, visible_children=visible_children@entry=0x7ffe08d4f270, expand_children=expand_children@entry=0x7ffe08d4f274) at clutter-box-layout.c:822
 clutter_box_layout_allocate (layout=0x55e9feb6a270, container=0x55e9feb80050, box=0x7ffe08d4f300, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at clutter-box-layout.c:968
 st_widget_allocate (actor=0x55e9feb80050, box=<optimized out>, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at ../src/st/st-widget.c:426
 st_box_layout_allocate (actor=0x55e9feb80050, box=0x55e9ff1f7db0, flags=<optimized out>) at ../src/st/st-box-layout.c:288

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
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
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.