| Summary: | [abrt] pino-0.2.11-1.fc14: Process /usr/bin/pino was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joel James Adamson <adamsonj> | ||||
| Component: | pino | Assignee: | Filipe Rosset <rosset.filipe> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | bperkins, metherid, rosset.filipe, supercyper1 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:b541b10300c4b798f730cb98f3bd44a26e5a3160 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-21 17:44:35 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
Joel James Adamson
2011-02-09 01:24:38 UTC
Created attachment 477720 [details]
File: backtrace
Package: pino-0.2.11-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Quit Pino because it was running high on memory usage. 2. Waited for the process to quit. 3. pino & Comment ----- Nothing odd, it just crashed on re-launch. Backtrace analysis found this bug to be similar to bug #683928, closing as duplicate. Bugs which were found to be similar to this bug: empathy: bug #678998 epiphany: bug #677204, bug #704914, bug #710665 gnucash: bug #707870 gwibber: bug #677380, bug #678631, bug #716650 midori: bug #673730 rednotebook: bug #677178 seed: bug #672351 webkitgtk: bug #683928, bug #700236 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 683928 *** |