Bug 630521 - [abrt] gthumb-2.11.91-1.fc14: g_file_get_path: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Summary: [abrt] gthumb-2.11.91-1.fc14: g_file_get_path: Process /usr/bin/gthumb was ki...
Keywords:
Status: CLOSED DUPLICATE of bug 603659
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:23ff57a58eb3bbbc89a35897021...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-06 05:30 UTC by Matěj Cepl
Modified: 2018-04-11 17:13 UTC (History)
2 users (show)

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


Attachments (Terms of Use)
File: backtrace (23.92 KB, text/plain)
2010-09-06 05:30 UTC, Matěj Cepl
no flags Details

Description Matěj Cepl 2010-09-06 05:30:38 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gthumb --import-photos /media/6287-6486
component: gthumb
crash_function: g_file_get_path
executable: /usr/bin/gthumb
kernel: 2.6.35.4-12.fc14.x86_64
package: gthumb-2.11.91-1.fc14
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1283750646
uid: 500

How to reproduce
-----
1.gthumb-importer got automatically started when N900 was connected as USB Mass Storage device
2. I haven't got even application window and it crashed
3. Later, when importing from the gthumb itself (which wasnt running before), I have imported pictures without a problem.

Comment 1 Matěj Cepl 2010-09-06 05:30:41 UTC
Created an attachment (id=443232)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 17:39:02 UTC

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

Comment 3 Karel Klíč 2010-11-08 17:39:02 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #603659.

Sorry for the inconvenience.


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