Ubuntu
gnome-shell package

gnome-shell crashed with signal 5 in meta_clutter_init()

Bug #1421953 reported by tom on 2015-02-14

This bug report is a duplicate of: Bug #1426533: gnome-shell crashed with signal 5 in meta_clutter_init(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	New	Undecided	Unassigned

Bug Description

not sure...

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-shell 3.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Sat Feb 14 13:31:39 2015
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2015-02-07 (6 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150120.1)
ProcCmdline: gnome-shell --display 0:0
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
meta_clutter_init () from /usr/lib/libmutter.so.0
meta_init () from /usr/lib/libmutter.so.0
?? ()
__libc_start_main (main=0x401cd0, argc=3, argv=0x7fffcec25be8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fffcec25bd8) at libc-start.c:287
?? ()
Title: gnome-shell crashed with signal 5 in meta_clutter_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

tom (jkt-nocrack) wrote on 2015-02-14:

Dependencies.txt Edit (24.7 KiB, text/plain; charset="utf-8")

Revision history for this message

tom (jkt-nocrack) wrote on 2015-02-14:

started when updated today

Revision history for this message

Apport retracing service (apport) wrote on 2015-02-14: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1416774, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.