at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()

Bug #813490 reported by Mmicoe
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
New
Undecided
Unassigned

Bug Description

Error at-spi register

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: at-spi 1.32.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Jul 15 11:53:08 2011
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
SegvAnalysis:
 Segfault happened at: 0x7f3b49: mov 0xc(%eax),%eax
 PC (0x007f3b49) 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: at-spi
StacktraceTop:
 ?? () from /usr/lib/libgconf-2.so.4
 gconf_client_get_default () from /usr/lib/libgconf-2.so.4
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
UpgradeStatus: Upgraded to oneiric on 2011-07-16 (3 days ago)
UserGroups:

Revision history for this message
Mmicoe (mmicoe) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #810721, 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
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.