at-spi2-registryd crashed with SIGSEGV in __libc_start_main()

Bug #1235930 reported by Dennj Osele
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

it's crashed alone on startup pc

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: at-spi2-core 2.10.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sun Oct 6 12:44:40 2013
ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
InstallationDate: Installed on 2012-10-23 (347 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
SegvAnalysis:
 Segfault happened at: 0x7f0271defa77: mov 0x8(%rax),%rcx
 PC (0x7f0271defa77) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: at-spi2-core
StacktraceTop:
 ?? ()
 __libc_start_main (main=0x7f0271def7a0, argc=2, ubp_av=0x7fff17a49868, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff17a49858) at libc-start.c:260
 ?? ()
Title: at-spi2-registryd crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-10-05 (1 days ago)
UserGroups:

Revision history for this message
Dennj Osele (dennj-osele) wrote :
information type: Private → Public
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceSource:
 #0 0x00007f0271defa77 in ?? ()
 #1 0x00007fff17a49758 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-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.