Bug 598805 - [abrt] crash in telepathy-mission-control-1:5.2.6-1.fc12: raise: Process /usr/libexec/mission-control-5 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in telepathy-mission-control-1:5.2.6-1.fc12: raise: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 541045
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-mission-control
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2bc557c3c0c9ee6ce15453c1d34...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 04:52 UTC by Maruthi Seshidhar Inukonda
Modified: 2010-06-02 10:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-02 10:37:58 UTC

Attachments (Terms of Use)
File: backtrace (7.30 KB, text/plain)
2010-06-02 04:52 UTC, Maruthi Seshidhar Inukonda 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Maruthi Seshidhar Inukonda 2010-06-02 04:52:13 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/mission-control-5
comment: Is this a known issue? Please help.
component: telepathy-mission-control
crash_function: raise
executable: /usr/libexec/mission-control-5
global_uuid: 2bc557c3c0c9ee6ce15453c1d340adcaf5413058
kernel: 2.6.32.11-99.fc12.i686.PAE
package: telepathy-mission-control-1:5.2.6-1.fc12
rating: 3
reason: Process /usr/libexec/mission-control-5 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Start Empathy IM client for the very first time, it asked for import from Pidgin
2. started Import account setting (Jaber & AIM accounts)
3. Kaboom...
Comment 1 Maruthi Seshidhar Inukonda 2010-06-02 04:52:16 UTC 
Created attachment 418902 [details]
File: backtrace
Comment 2 Peter Robinson 2010-06-02 10:37:58 UTC 

*** This bug has been marked as a duplicate of bug 541045 ***
Note You need to log in before you can comment on or make changes to this bug.