Bug 579099
Summary: | [abrt] crash in ristretto-0.0.22-2.fc12: IA__g_object_unref: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Semitsoglou-Tsiapos Dimitri <madcatmk254> | ||||
Component: | ristretto | Assignee: | Christoph Wickert <christoph.wickert> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | christoph.wickert, projects.rg | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:e3c58d9c169f2921b2c77e69d4c570b0106168b9 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-07-16 14:21:20 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
Semitsoglou-Tsiapos Dimitri
2010-04-02 16:03:10 UTC
Created attachment 404205 [details]
File: backtrace
What did you do when ristretto crashed? Can you reproduce the crash? I have forwarded your report to the upstream developer at http://bugzilla.xfce.org/show_bug.cgi?id=6365 Feel free to subscribe there in order to be notified about changes. Dimitri, can you please answer my questions? 1. Do you still recall what you did when ristretto crashed? 2. Can you reproduce the crash? I'm sorry, I'm afraid I can't remember what exactly happened and even though I still have the images that caused it I can't reproduce it. *** Bug 600675 has been marked as a duplicate of this bug. *** I'm now closing the bug UPSTREAM because this is where further investigation should take place. You will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you. Thanks for reporting this bug. *** This bug has been marked as a duplicate of bug 542141 *** |