Bug 584878 - [abrt] crash in telepathy-mission-control-1:5.3.2-1.fc13: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in telepathy-mission-control-1:5.3.2-1.fc13: Process /usr/libexe...
Keywords:
Status: CLOSED ERRATA
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:fa78b12fd597329228e3b3c5765...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-22 16:01 UTC by Carl G.
Modified: 2010-05-04 06:05 UTC (History)
3 users (show)

Fixed In Version: telepathy-mission-control-5.4.0-1.fc13
Clone Of:
Environment:
Last Closed: 2010-05-03 07:19:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (10.06 KB, text/plain)
2010-04-22 16:01 UTC, Carl G. 		no flags Details
View All

Description Carl G. 2010-04-22 16:01:49 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/mission-control-5
component: telepathy-mission-control
executable: /usr/libexec/mission-control-5
global_uuid: fa78b12fd597329228e3b3c5765e44d8fab0feee
kernel: 2.6.33.2-57.fc13.x86_64
package: telepathy-mission-control-1:5.3.2-1.fc13
rating: 4
reason: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Carl G. 2010-04-22 16:01:51 UTC 
Created attachment 408364 [details]
File: backtrace
Comment 2 Fedora Update System 2010-04-28 21:47:40 UTC 
telepathy-mission-control-5.4.0-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/telepathy-mission-control-5.4.0-1.fc13
Comment 3 Peter Robinson 2010-05-03 07:19:56 UTC 
missing debuginfo
Comment 4 Fedora Update System 2010-05-04 06:05:25 UTC 
telepathy-mission-control-5.4.0-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.