Bug 606423 - [abrt] crash in gthumb-2.10.11-9.fc12: update_thumbs_stopped: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gthumb-2.10.11-9.fc12: update_thumbs_stopped: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 579523
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb (Show other bugs)
(Show other bugs)
Version: 12
Hardware: i686 Linux
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:4f1de4c89acced8d47f718475c4...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-21 15:15 UTC by alextazy0
Modified: 2010-08-02 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-02 22:10:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (21.50 KB, text/plain)
2010-06-21 15:15 UTC, alextazy0
no flags Details

Description alextazy0 2010-06-21 15:15:19 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb '/home/alex/T\xc3\xa9l\xc3\xa9chargement/jdownloader_incomming/088 - Kitty at the COHF Condo!/1079.jpg'
component: gthumb
crash_function: update_thumbs_stopped
executable: /usr/bin/gthumb
global_uuid: 4f1de4c89acced8d47f718475c42bd993cad6e4e
package: gthumb-2.10.11-9.fc12
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 alextazy0 2010-06-21 15:15:23 UTC
Created attachment 425660 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2010-07-17 22:11:26 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:10:49 UTC

Fedora Bugzappers volunteer triage team

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

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