unity-greeter crashed with SIGSEGV in g_closure_invoke()

Bug #954255 reported by Stéphane Graber
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This is happening when logging out of the live session on any current media.

See bug 943037 for the initial description but without the stack trace.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.307
Date: Tue Mar 13 17:26:02 2012
ExecutablePath: /usr/sbin/unity-greeter
LiveMediaBuild: Edubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120313)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x41ca56: cmpq $0x0,0x18(%rdx)
 PC (0x0041ca56) ok
 source "$0x0" ok
 destination "0x18(%rdx)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-greeter crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Stéphane Graber (stgraber) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-greeter (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : 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 #952557, 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.

tags: removed: need-amd64-retrace
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.