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

Bug #447494 reported by Nick Messick
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: at-spi

1) Ubuntu karmic (development branch) 9.10

2) Honestly, can't remember what I was doing. Crash happened a couple days ago.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Oct 7 19:24:05 2009
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
Package: at-spi 1.28.0-0ubuntu2
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: at-spi
StacktraceTop:
 ?? ()
 IceProcessMessages () from /usr/lib/libICE.so.6
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
Title: at-spi-registryd crashed with SIGSEGV in IceProcessMessages()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Nick Messick (nmessick) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
IceProcessMessages (iceConn=0x0, replyWait=0x0,
process_ice_messages (channel=0x951e560, condition=G_IO_IN,
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in at-spi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Nick Messick (nmessick)
visibility: private → public
Revision history for this message
Brian Murray (brian-murray) wrote : Marking as a duplicate

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 437315, so it 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.

Changed in at-spi (Ubuntu):
status: New → Confirmed
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.