gnome-shell crashed with signal 5 in g_wakeup_new()

Bug #1182714 reported by Tim Lunn
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Happened while I was away from the computer.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.2-0ubuntu1~raring1.1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
CrashDB: ubuntu
Date: Wed May 22 01:45:42 2013
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1368582904
InstallationDate: Installed on 2012-09-23 (241 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
MarkForUpload: True
ProcCmdline: gnome-shell --replace
ProcCwd: /home/darkness
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 g_wakeup_new () at /build/buildd/glib2.0-2.37.0/./glib/gwakeup.c:163
 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x11a1e540, pollfd=pollfd@entry=0x11a49a50) at /build/buildd/glib2.0-2.37.0/./gio/gcancellable.c:406
 socket_source_new (cancellable=0x11a1e540, condition=(G_IO_OUT | G_IO_ERR | G_IO_HUP), socket=0x11a12280) at /build/buildd/glib2.0-2.37.0/./gio/gsocket.c:3265
 g_socket_create_source (socket=0x11a12280, condition=condition@entry=G_IO_OUT, cancellable=cancellable@entry=0x11a1e540) at /build/buildd/glib2.0-2.37.0/./gio/gsocket.c:3330
 g_socket_connection_connect_async (connection=0x119e6360, address=address@entry=0x11a22c20, cancellable=cancellable@entry=0x11a1e540, callback=callback@entry=0x7fd572a3fb90 <g_socket_client_connected_callback>, user_data=user_data@entry=0x119f38a0) at /build/buildd/glib2.0-2.37.0/./gio/gsocketconnection.c:208
Title: gnome-shell crashed with signal 5 in g_wakeup_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Tim Lunn (darkxst) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? () from /tmp/apport_sandbox__HChDN/lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

package libmutter0 does not exist, ignoring

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Tim Lunn (darkxst)
Changed in gnome-shell (Ubuntu):
status: Invalid → Confirmed
Tim Lunn (darkxst)
information type: Private → Public
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. I apologize that we are not always to respond to bug reports promptly. Ubuntu 13.10 reached End of Life in 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still
reproducible, increase the verbosity of the steps to recreate it so we
can try again.

Do feel free to report any other bugs you may find.

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