Bug 620440 - [abrt] crash in telepathy-mission-control-1:5.4.3-1.fc13: _mcd_build_error_string: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in telepathy-mission-control-1:5.4.3-1.fc13: _mcd_build_error_st...
Keywords:
Status: CLOSED DUPLICATE of bug 607863
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-mission-control
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:da1a1c53d3536fc689acac8ff10...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-02 14:26 UTC by Kvikende
Modified: 2010-08-24 08:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-02 14:30:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (10.19 KB, text/plain)
2010-08-02 14:26 UTC, Kvikende 		no flags Details
View All

Description Kvikende 2010-08-02 14:26:29 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/mission-control-5
comment: I opened a conversation to a MSN contact. I only have MSN connection enabled. I've gotten this one before.
component: telepathy-mission-control
crash_function: _mcd_build_error_string
executable: /usr/libexec/mission-control-5
global_uuid: da1a1c53d3536fc689acac8ff10777740eece9cb
kernel: 2.6.33.6-147.fc13.x86_64
package: telepathy-mission-control-1:5.4.3-1.fc13
rating: 4
reason: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: 1. I opened a conversation to a MSN contact.
Comment 1 Kvikende 2010-08-02 14:26:31 UTC 
Created attachment 436038 [details]
File: backtrace
Comment 2 Kvikende 2010-08-02 14:30:15 UTC 

*** This bug has been marked as a duplicate of bug 619463 ***
Comment 3 Peter Robinson 2010-08-24 08:05:04 UTC 

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