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

Bug #818575 reported by (J)Aloittelija
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
New
Medium
Unassigned

Bug Description

Updating..

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: at-spi 1.32.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Sat Jul 30 19:26:19 2011
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
ProcEnviron:
 LANG=fi_FI.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0xe29b49: mov 0xc(%eax),%eax
 PC (0x00e29b49) 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-15 (15 days ago)
UserGroups:

Revision history for this message
(J)Aloittelija (jari-aho) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 set_engine (client=0x0, engine=0x867f070) at gconf-client.c:277
 gconf_client_get_default () at gconf-client.c:471
 ?? ()
 __libc_start_main (main=0x804b290, argc=1, ubp_av=0xbfc200d4, init=0x8050f30, fini=0x8050f90, rtld_fini=0x4609f0, stack_end=0xbfc200cc) at libc-start.c:226
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in at-spi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.