unity-greeter crashed with SIGSEGV in indicator_object_get_entries()

Bug #922058 reported by Andre Tomt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just did a dist-upgrade in Precise and now lightdm segfaults. GDM works fine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.0-0ubuntu5
Uname: Linux 3.1.0-1-desktop x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Thu Jan 26 13:28:29 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007.1)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f5e02df2f6c <indicator_object_get_entries+44>: mov 0x18(%rax),%rax
 PC (0x7f5e02df2f6c) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 indicator_object_get_entries () from /usr/lib/libindicator3.so.7
 ?? ()
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-greeter crashed with SIGSEGV in indicator_object_get_entries()
UpgradeStatus: Upgraded to precise on 2012-01-05 (21 days ago)
UserGroups:

Revision history for this message
Andre Tomt (andre-tomt) wrote :
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 #921998, 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.

visibility: private → public
visibility: private → public
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.