unity-greeter crashed with SIGSEGV in indicator_object_get_entries()

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

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

unity-greeter:
  Installato: 0.2.0-0ubuntu5
  Candidato: 0.2.0-0ubuntu5
  Tabella versione:
 *** 0.2.0-0ubuntu5 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
Uname: Linux 3.2.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Wed Jan 25 20:36:54 2012
ExecutablePath: /usr/sbin/unity-greeter
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xd75090 <indicator_object_get_entries+64>: mov 0xc(%eax),%eax
 PC (0x00d75090) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" 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/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/i386-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-22 (3 days ago)
UserGroups:

Revision history for this message
Davide Belloni (dbelloni) 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-i386-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.