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

Bug #418743 reported by Andy Duffell
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: at-spi

Crashed at login

ProblemType: Crash
Architecture: amd64
Date: Tue Aug 25 16:00:18 2009
Disassembly: 0x0:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
NonfreeKernelModules: nvidia
Package: at-spi 1.27.91-0ubuntu1
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0x0:
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: at-spi
StacktraceTop:
 ?? ()
 _SmcProcessMessage () from /usr/lib/libSM.so.6
 IceProcessMessages () from /usr/lib/libICE.so.6
 ?? ()
 g_main_context_dispatch ()
Title: at-spi-registryd crashed with SIGSEGV in _SmcProcessMessage()
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Andy Duffell (andy-duffell) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
_SmcProcessMessage (iceConn=0x1f62e00,
IceProcessMessages (iceConn=0x1f62e00,
process_ice_messages (
IA__g_main_context_dispatch (context=0x1f2d420)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: removed: need-amd64-retrace
visibility: private → public
Changed in at-spi (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
tags: added: a11y
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in at-spi (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.