Bug 696297 - [abrt] geeqie-1.0-9.fc14: file_data_unref_debug: Process /usr/bin/geeqie was killed by signal 6 (SIGABRT)
Summary: [abrt] geeqie-1.0-9.fc14: file_data_unref_debug: Process /usr/bin/geeqie was ...
Keywords:
Status: CLOSED DUPLICATE of bug 655610
Alias: None
Product: Fedora
Classification: Fedora
Component: geeqie
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8e386c8218a4909e727eb02053b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 19:24 UTC by Peter Hanecak
Modified: 2011-04-13 20:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-13 20:26:55 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (12.35 KB, text/plain)
2011-04-13 19:24 UTC, Peter Hanecak 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Peter Hanecak 2011-04-13 19:24:55 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 12645 bytes
cmdline: geeqie
comment: After picture removal, Geeqie crashed.
component: geeqie
Attached file: coredump, 201187328 bytes
crash_function: file_data_unref_debug
executable: /usr/bin/geeqie
kernel: 2.6.35.12-88.fc14.x86_64
package: geeqie-1.0-9.fc14
rating: 4
reason: Process /usr/bin/geeqie was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302722323
uid: 500

How to reproduce
-----
1. run geeqie
2. browse to directory with some pictures, so that one is displayed
3. remove all the pictures from the displayed directory from another application (shell)
Comment 1 Peter Hanecak 2011-04-13 19:24:58 UTC 
Created attachment 491874 [details]
File: backtrace
Comment 2 Michael Schwendt 2011-04-13 20:26:55 UTC 
> How to reproduce

No, that's not a sufficient test-case but just what you did prior to the crash. It doesn't crash always.

[reopening bug 655610]

*** This bug has been marked as a duplicate of bug 655610 ***
Note You need to log in before you can comment on or make changes to this bug.