Bug 638534 - [abrt] at-spi2-core-0.3.91-1.fc14: raise: Process /usr/libexec/at-spi2-registryd was killed by signal 6 (SIGABRT)
Summary: [abrt] at-spi2-core-0.3.91-1.fc14: raise: Process /usr/libexec/at-spi2-regist...
Keywords:
Status: CLOSED DUPLICATE of bug 657967
Alias: None
Product: Fedora
Classification: Fedora
Component: at-spi2-core
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:17668a32ee64ddaef31091a9459...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-29 09:47 UTC by GhostMan.227
Modified: 2018-04-11 10:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:01:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.42 KB, text/plain)
2010-09-29 09:47 UTC, GhostMan.227
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.