Bug 638534

Summary: [abrt] at-spi2-core-0.3.91-1.fc14: raise: Process /usr/libexec/at-spi2-registryd was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: GhostMan.227
Component: at-spi2-coreAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: gavin42, mcepl, mcepl, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:17668a32ee64ddaef31091a94596c66f5e8df802
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 18:01:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description GhostMan.227 2010-09-29 09:47:36 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/at-spi2-registryd --use-gnome-session
component: at-spi2-core
crash_function: raise
executable: /usr/libexec/at-spi2-registryd
kernel: 2.6.35.4-28.fc14.x86_64
package: at-spi2-core-0.3.91-1.fc14
rating: 4
reason: Process /usr/libexec/at-spi2-registryd was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1285717775
uid: 500
Comment 1 GhostMan.227 2010-09-29 09:47:38 UTC 
Created attachment 450426 [details]
File: backtrace
Comment 2 Nivag 2010-09-29 11:08:57 UTC 
Package: at-spi2-core-0.3.91-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.?
2.
3.


Comment
-----
Not sure.
Comment 3 abrt-bot 2012-03-20 18:01:01 UTC 
Backtrace analysis found this bug to be similar to bug #657967, closing as duplicate.

Bugs which were found to be similar to this bug: bug #639967, bug #645325, bug #648282, bug #657967, bug #705874

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 657967 ***