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

Bug #565333 reported by cekabe on 2010-04-17
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: at-spi

it happened when i started laptop !

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: at-spi 1.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sat Apr 17 13:50:38 2010
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=pl_PL.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x783041: mov 0xc(%eax),%eax
 PC (0x00783041) 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/tls/i686/cmov/libc.so.6
 ?? ()
Title: at-spi-registryd crashed with SIGSEGV in gconf_client_get_default()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1431): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

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 #508156, 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  Edit
Everyone can see this information.

Other bug subscribers