Bug 606195 - [abrt] crash in telepathy-mission-control-1:5.4.0-1.fc13: raise: Process /usr/libexec/mission-control-5 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in telepathy-mission-control-1:5.4.0-1.fc13: raise: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 591613
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:418c09b896dbf4ac323dab39df8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-21 05:15 UTC by Allen Zhu
Modified: 2010-06-30 07:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-30 07:31:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (9.41 KB, text/plain)
2010-06-21 05:15 UTC, Allen Zhu 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 605759 0 low CLOSED Moblin Crashes on Start 2021-02-22 00:41:40 UTC

Internal Links: 605759

Description Allen Zhu 2010-06-21 05:15:35 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/mission-control-5
comment: See bug 605759 (https://bugzilla.redhat.com/show_bug.cgi?id=605759).
component: telepathy-mission-control
crash_function: raise
executable: /usr/libexec/mission-control-5
global_uuid: 418c09b896dbf4ac323dab39df85c36782bfb789
kernel: 2.6.33.5-124.fc13.x86_64
package: telepathy-mission-control-1:5.4.0-1.fc13
rating: 4
reason: Process /usr/libexec/mission-control-5 was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: See bug 605759 (https://bugzilla.redhat.com/show_bug.cgi?id=605759).
Comment 1 Allen Zhu 2010-06-21 05:15:37 UTC 
Created attachment 425527 [details]
File: backtrace
Comment 2 Peter Robinson 2010-06-30 07:31:16 UTC 

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