| Summary: | [abrt] gnome-shell-3.3.92-1.fc17: __pthread_disable_asynccancel: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gordon <swedishelk> | ||||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 17 | CC: | maxamillion, otaylor, samkraju, walters | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:0ce308ab47d4e15f87e202e2fca2d776b6bfc48e | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2013-08-01 06:28:16 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Gordon
2012-03-27 12:45:37 UTC
Created attachment 573046 [details]
File: backtrace
Created attachment 573047 [details]
File: xsession_errors
Created attachment 573048 [details]
File: maps
Created attachment 573049 [details]
File: dso_list
Created attachment 573050 [details]
File: build_ids
Created attachment 573051 [details]
File: var_log_messages
This is very similar to the crashes in bug 807293 and bug 808307 that you also reported. Which is interesting - I don't know if this is because of something specific about your hardware, or something about the set of packages that you have installed. The crash doesn't seem to be triggered directly by any code in GNOME ... it could perhaps be code corrupting the internal state of libc, however. (If you know of anything unusual about your system - unusual hardware, local changes to the C library, custom kernel, etc, that would definitely be useful information.) Nothing unusual that I know of. It's a fresh install from the Alpha Live ISO, then just yum update. No wierd hardware, it's a default Esprimo E with 4 GB RAM. I have not changed anything but the normal update. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. |