Bug 610475 - [abrt] crash in gthumb-2.11.3-1.fc13: IA__g_file_get_path: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gthumb-2.11.3-1.fc13: IA__g_file_get_path: Process /usr/bin/g...
Keywords:
Status: CLOSED DUPLICATE of bug 603659
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8dd12f79aed30811936414b943b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-02 08:14 UTC by Jan Debertshäuser
Modified: 2010-08-02 22:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-02 22:17:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.81 KB, text/plain)
2010-07-02 08:14 UTC, Jan Debertshäuser
no flags Details

Description Jan Debertshäuser 2010-07-02 08:14:29 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gthumb /home/jade/Photos/2010_07_01_Fruehs/P1130736.JPG
comment: I just right-clicked on a picture in nautilus file browser and clicked on "Open with..." -> "gThumb"
component: gthumb
crash_function: IA__g_file_get_path
executable: /usr/bin/gthumb
global_uuid: 8dd12f79aed30811936414b943b0c9ad30fbc5f3
kernel: 2.6.33.5-124.fc13.x86_64
package: gthumb-2.11.3-1.fc13
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: Open gThumb

Comment 1 Jan Debertshäuser 2010-07-02 08:14:32 UTC
Created attachment 428757 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2010-07-17 22:08:35 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Benjamín Valero Espinosa 2010-08-02 22:17:48 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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


Note You need to log in before you can comment on or make changes to this bug.