Bug 600675

Summary: [abrt] crash in ristretto-0.0.22-3.fc13: IA__g_object_unref: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Raphael Groner <projects.rg>
Component: ristrettoAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:9f1de8584452c3c69760cd62dc71234ca3c691a4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-05 15:41:15 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 Flags
File: backtrace none

Description Raphael Groner 2010-06-05 15:11:38 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: ristretto '/home/raphael/studium-pm/Logistik/Pr\xc3\xa4si/pics Pr\xc3\xa4si/CargoLogistik.jpg'
comment: Random occurances.
component: ristretto
crash_function: IA__g_object_unref
executable: /usr/bin/ristretto
global_uuid: 9f1de8584452c3c69760cd62dc71234ca3c691a4
kernel: 2.6.33.5-112.fc13.x86_64
package: ristretto-0.0.22-3.fc13
rating: 4
reason: Process /usr/bin/ristretto was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Watch images with ristretto
2. Dunno what exactly done to cause the crash ...
3.
Comment 1 Raphael Groner 2010-06-05 15:11:40 UTC 
Created attachment 421439 [details]
File: backtrace
Comment 2 Raphael Groner 2010-06-05 15:24:42 UTC 
Package: ristretto-0.0.22-3.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Watch images with ristretto
2. Dunno what exactly done to cause the crash ...
3.


Comment
-----
Random occurances.
Comment 3 Christoph Wickert 2010-06-05 15:41:15 UTC 
This is a known bug that I have already reported to upstream.

*** This bug has been marked as a duplicate of bug 579099 ***