Bug 783905
| Summary: | [abrt] ghex-3.0.0-1.fc16: __GI_raise: Process /usr/bin/ghex was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zachary Hardesty <zachary.hardesty> | ||||||||
| Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | adel.gadllah, dodji, kalevlember, mclasen | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:57d9ad992eac7f47fbac7d891cfe5c0cedd5f0ca | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 17:47:37 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Zachary Hardesty
2012-01-23 07:38:39 UTC
Created attachment 556863 [details]
File: dso_list
Created attachment 556864 [details]
File: maps
Created attachment 556865 [details]
File: backtrace
Zachary, thanks for reporting this issue! From the backtrace the crash appears to be in GTK+ filechooser code. Do you have a way to reproduce it? It happened only once after a fresh install of F16 from the DVD, an upgrade to the latest packages using the PackageKit GUI at the time of the bug report, and installing GHex through the Add/Remove Programs application in the menu. On first load up, I did File->Open and opened a 10MB binary file. It was there that it crashed. As stated, GHex started working thereafter. gtk3-3.2.3 (in F16 by now) fixed some crashes in the file chooser code. My guess is that this is why you can't reproduce it any more. Reassigning to gtk3 and closing as fixed; please reopen if you find a way to reproduce it. Thanks! Rhythmbox 2.97 crash on Fedora 17 sent me here: --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Bug is already reported: 783905 Logging out Status: CLOSED ERRATA https://bugzilla.redhat.com/show_bug.cgi?id=783905 Error happened when I tried to import music from directory on mounted flash disc. 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. Changing fedora version to 17 because of: Rhythmbox 2.97 crash on Fedora 17 sent me here: --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Bug is already reported: 783905 Logging out Status: CLOSED ERRATA https://bugzilla.redhat.com/show_bug.cgi?id=783905 Error happened when I tried to import music from directory on mounted flash disc. 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. |