Bug 603854
| Summary: | [abrt] crash in pino-0.2.10-1.fc12: raise: Process /usr/bin/pino was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juan M. Lasca <juanmlasca> | ||||
| Component: | pino | Assignee: | Filipe Rosset <rosset.filipe> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | bperkins, dee_chie21, dekacy10, gabriel, gael.chamoulaud, giallu, icon, jk, jkrupka, jl.deloos, jwalden+brc, k.weiz, luzemail, metherid, redchernobil, rosset.filipe, santiago.lunar.m, supercyper1 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:cae7869b324cb4d34c48714722d00f7e0def2294 | ||||||
| Fixed In Version: | pino-0.2.11-1.fc12 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-07-13 07:53:13 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
Juan M. Lasca
2010-06-14 17:28:07 UTC
Created attachment 423917 [details]
File: backtrace
Package: pino-0.2.10-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start pino both from memu or terminal. 2. Pino crash. Comment ----- When started from terminal, pino outputs the following error messages: ** (pino:2859): WARNING **: Invalid GValue unboxing (wrong type or NULL) GLib-ERROR **: The thread system is not yet initialized. aborting... Aborted (core dumped) Package: pino-0.2.10-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. open pine 2. 3. Package: pino-0.2.10-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- I just updated my F12 and now pino crashes at startup Package: pino-0.2.10-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. After a reboot tried to launch pino. Comment ----- Did nothing beyond pino & pino-0.2.11-1.fc12.x86_64 in updates-testing seems to fix the issue. I suggest everyone here install it and fedora-easy-karma so we can push to stable sooner *** Bug 613294 has been marked as a duplicate of this bug. *** *** Bug 610331 has been marked as a duplicate of this bug. *** *** Bug 608228 has been marked as a duplicate of this bug. *** *** Bug 581226 has been marked as a duplicate of this bug. *** *** Bug 587300 has been marked as a duplicate of this bug. *** *** Bug 588823 has been marked as a duplicate of this bug. *** *** Bug 589249 has been marked as a duplicate of this bug. *** *** Bug 593208 has been marked as a duplicate of this bug. *** *** Bug 593153 has been marked as a duplicate of this bug. *** *** Bug 603470 has been marked as a duplicate of this bug. *** *** Bug 603341 has been marked as a duplicate of this bug. *** *** Bug 602950 has been marked as a duplicate of this bug. *** *** Bug 604015 has been marked as a duplicate of this bug. *** *** Bug 604166 has been marked as a duplicate of this bug. *** *** Bug 606686 has been marked as a duplicate of this bug. *** *** Bug 609376 has been marked as a duplicate of this bug. *** *** Bug 613006 has been marked as a duplicate of this bug. *** pino-0.2.11-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pino-0.2.11-1.fc12 Package: pino-0.2.10-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Tried to launch pino with 'pino &' Comment ----- Just rebooted and tried launching. pino-0.2.11-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |