Bug 552226

Summary: [abrt] crash detected in ristretto-0.0.22-2.fc12
Product: [Fedora] Fedora Reporter: Rasmus Dall <Rasmus>
Component: ristrettoAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:c22e9e5fc8e031681c97ee0b1e91c510abf5d329
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-04 12:37:33 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 Rasmus Dall 2010-01-04 12:26:45 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Open Ristretto by double clicking an image
2. Full screen
3. View images

Comment: I did not notice that anything happened with Ristretto, to me it seemed to work perfectly. But since the ABRT detected a crash I decided to report it.
Attached file: backtrace
cmdline: ristretto /home/Rasmus/Pictures/Gordons/voergaard/voergaard_2/DSC_0041.JPG
component: ristretto
executable: /usr/bin/ristretto
kernel: 2.6.31.9-174.fc12.i686
package: ristretto-0.0.22-2.fc12
rating: 3
reason: Process was terminated by signal 11
Comment 1 Rasmus Dall 2010-01-04 12:26:48 UTC 
Created attachment 381531 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-01-04 12:37:33 UTC 
Hi Rasmus,

thanks for your report. Unfortunately the backtrace is incomplete because ABRT, the automatic bug reporting tool fails to install the necessary debuginfo packages. When ristretto crashes again, please run

$ debuginfo-install ristretto

before letting abrt generate the bug report. Hopefully abrt-1.0.2 will fix this, so that you don't need to install the debuginfo manually.

From what I can see and from your description your crash looks similar to bug 542141, which has a better backtrace.

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