Ubuntu
unity-greeter package

unity-greeter crashed with SIGSEGV in g_cancellable_is_cancelled()

Bug #852178 reported by Jean-Baptiste Mazon on 2011-09-16

This bug report is a duplicate of: Bug #851088: unity-greeter crashed with SIGSEGV in g_cancellable_is_cancelled(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity-greeter (Ubuntu)	New	Undecided	Unassigned

Bug Description

Ouch.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-greeter 0.0.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Fri Sep 16 22:44:45 2011
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: unity-greeter
SegvAnalysis:
Segfault happened at: 0x7f9cdb17fbbb <g_cancellable_is_cancelled+11>: testb $0x1,(%rax)
PC (0x7f9cdb17fbbb) ok
source "$0x1" ok
destination "(%rax)" (0x0000002f) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
g_cancellable_is_cancelled () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-greeter crashed with SIGSEGV in g_cancellable_is_cancelled()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (3 days ago)
UserGroups:

Tags:

Revision history for this message

Jean-Baptiste Mazon (jmazon) wrote on 2011-09-16:

ProcEnviron.txt Edit (139 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-16: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #851088, 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.