Bug 846776
| Summary: | [abrt] twinkle-1.4.2-17.fc17: __GI___open_catalog: Process /usr/bin/twinkle was killed by signal 6 (SIGABRT) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Russell Harrison <fedora> | ||||||||||
| Component: | twinkle | Assignee: | Kevin Fenzi <kevin> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | 130228, kevin, manuel.wolfshant | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:a42c87cb34ea5028b685fa38794620979253b1d9 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-08-01 17:31:22 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
Russell Harrison
2012-08-08 16:27:26 UTC
Created attachment 603075 [details]
File: backtrace
Created attachment 603076 [details]
File: maps
Created attachment 603077 [details]
File: dso_list
rpm -q ucommon ? Should be fixed by: https://admin.fedoraproject.org/updates/FEDORA-2012-10013/ucommon-5.2.3-1.fc17 (In reply to comment #4) > rpm -q ucommon > > ? > > Should be fixed by: > https://admin.fedoraproject.org/updates/FEDORA-2012-10013/ucommon-5.2.3-1. > fc17 I have already updated ucommon and I'm still seeing this problem. $ rpm -q ucommon ucommon-5.2.3-1.fc17.x86_64 ok. Would you be willing to try and get a better backtrace here? debuginfo-install twinkle ucommon and then gdb twinkle run thread apply all bt full https://fedoraproject.org/wiki/StackTraces Created attachment 619895 [details]
gdb twinkle output
Here is the gdb output requested.
Strange. This really looks like the same crash. ;( Does: rpm -V ucommon have any output? Are there any multiple versions installed? (In reply to comment #8) > Strange. This really looks like the same crash. ;( > > Does: > > rpm -V ucommon > > have any output? Are there any multiple versions installed? No output for ucommon or twinkle. One version installed for each. I'll check the other deps as well... While this is a bug that should be fixed upstream, I found a workaround that allows end users to use twinkle as long as there's not real fix: make sure your hostname can be resolved through dns. Having your hostname listed in /etc/hosts is not enough. Only if the command "host $(hostname)" gives a valid answer, I can start twinkle. So I fixed this by putting my hostname in my routers DNS server. Hope this helps you guys. Btw, I'm running FC18. 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. |