Bug 705874 - [abrt] at-spi2-core-0.4.0-1.fc14: spi_get_bus: Process /usr/libexec/at-spi2-registryd was killed by signal 6 (SIGABRT)
Summary: [abrt] at-spi2-core-0.4.0-1.fc14: spi_get_bus: Process /usr/libexec/at-spi2-r...
Keywords:
Status: CLOSED DUPLICATE of bug 657967
Alias: None
Product: Fedora
Classification: Fedora
Component: at-spi2-core
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6c42943f74a5090ae5d23f7f46c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 18:27 UTC by igoborkos@mail.ru
Modified: 2012-03-20 18:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:00:50 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (4.94 KB, text/plain)
2011-05-18 18:27 UTC, igoborkos@mail.ru
no flags Details

Description igoborkos@mail.ru 2011-05-18 18:27:09 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 5061 bytes
cmdline: /usr/libexec/at-spi2-registryd --use-gnome-session
component: at-spi2-core
Attached file: coredump, 581632 bytes
crash_function: spi_get_bus
executable: /usr/libexec/at-spi2-registryd
kernel: 2.6.35.11-83.fc14.i686
package: at-spi2-core-0.4.0-1.fc14
rating: 4
reason: Process /usr/libexec/at-spi2-registryd was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300048576
uid: 500

How to reproduce
-----
1.yum install
2.
3.

Comment 1 igoborkos@mail.ru 2011-05-18 18:27:11 UTC
Created attachment 499656 [details]
File: backtrace

Comment 2 igoborkos@mail.ru 2011-05-18 18:33:42 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.yum install
2.
3.

Comment 3 igoborkos@mail.ru 2011-05-26 18:06:40 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Do not remember.
2.
3.

Comment 4 David 2011-05-28 20:57:09 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
Unsure the cause of this bug.

Comment 5 Alex Bartl 2011-09-04 17:22:22 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----

added 4GB RAM (total 12)

Comment 6 Alex Bartl 2011-09-04 17:23:00 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
no clue

Comment 7 Alex Bartl 2011-09-05 01:41:14 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. no clue
2.
3.

Comment 8 Alex Bartl 2011-09-05 20:05:35 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. no clue
2.
3.

Comment 9 Alex Bartl 2011-09-06 15:25:51 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. no clue
2.
3.

Comment 10 Alex Bartl 2011-09-07 19:07:40 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. no clue
2.
3.

Comment 11 Pichan 2011-11-08 09:09:46 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Don't know

Comment 12 Vedran 2012-01-18 11:51:05 UTC
Package: at-spi2-core-0.4.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I do not know
2.I do not know
3.I do not know

Comment 13 abrt-bot 2012-03-20 18:00:50 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 #638534, bug #639967, bug #645325, bug #648282, bug #657967

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.