gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from st_widget_allocate()

Bug #1724334 reported by Brian Murray
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I was trying to unlock my screen which took a while and then I received this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
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
CurrentDesktop: GNOME
Date: Tue Oct 17 11:18:13 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2013-01-16 (1735 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
ProcCmdline: gnome-shell --sm-client-id 10aeea5677451824be15003363904125100000082680000
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 () at /usr/lib/gnome-shell/libst-1.0.so
 () at /usr/lib/gnome-shell/libst-1.0.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
Title: gnome-shell crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clutter_box_layout_allocate (layout=0x7f0fa809bb30, container=<optimized out>, box=<optimized out>, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at clutter-box-layout.c:1010
 st_widget_allocate (actor=0x5634bf180650, box=<optimized out>, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at ../src/st/st-widget.c:426
 st_box_layout_allocate (actor=0x5634bf180650, box=0x5634b12e3c60, flags=<optimized out>) at ../src/st/st-box-layout.c:288
 clutter_actor_allocate_internal (flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED, allocation=<optimized out>, self=0x5634bf180650) at clutter-actor.c:9973
 clutter_actor_set_animatable_property (actor=actor@entry=0x5634bf180650, prop_id=<optimized out>, value=value@entry=0x7ffc055ccfc0, pspec=pspec@entry=0x5634b0600d70) at clutter-actor.c:14988

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
summary: - gnome-shell crashed with signal 5
+ gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from
+ st_widget_allocate()
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 :

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: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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