Bug 750367
Summary: | [abrt] telepathy-mission-control-5.9.3-1.fc16: __GI_raise: Process /usr/libexec/mission-control-5 was killed by signal 6 (SIGABRT) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomasz Sterna <tomek> |
Component: | telepathy-glib | Assignee: | Brian Pepple <bdpepple> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | bdpepple, johnp, joshua.rich, pbrobinson |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:90727ff9ba8b8ad7bf556091013cf8de1b765380 | ||
Fixed In Version: | telepathy-mission-control-5.10.1-1.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-14 00:54:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomasz Sterna
2011-10-31 20:20:02 UTC
Package: telepathy-mission-control-5.9.3-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I logged back from suspend and mission-control crashed. telepathy-mission-control-5.10.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/telepathy-mission-control-5.10.1-1.fc16 Package telepathy-mission-control-5.10.1-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing telepathy-mission-control-5.10.1-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15669 then log in and leave karma (feedback). Package: telepathy-mission-control-5.10.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- mission-control aborted right after starting Unfortunately telepathy-mission-control-5.10.1-1.fc16 didn't help. ABRT submitted another crash report for this version of package. Package: telepathy-mission-control-5.10.1-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- After starting Empathy, telepathy-mission-control crashed. telepathy-mission-control-5.10.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. $ rpm -q telepathy-mission-control telepathy-mission-control-5.10.1-1.fc16.x86_64 It just crashed right after starting Empathy. ABRT reported the crash as a duplicate of this bug. Backtrace analysis of bugs across components suggests the actual bug is in component telepathy-glib instead of component telepathy-mission-control, reassigning to telepathy-glib. Bug #770479 from component telepathy-logger was found to be similar to this bug. This comment is automatically generated. *** Bug 770479 has been marked as a duplicate of this bug. *** I've opened jabber-conference and crash backtrace_rating: 4 Package: telepathy-logger-0.4.0-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) Error occurred on login after restart of machine. backtrace_rating: 4 Package: telepathy-logger-0.4.0-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |