Bug 597006 - [abrt] crash in gthumb-2.11.3-1.fc13: notify_files_delete: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
[abrt] crash in gthumb-2.11.3-1.fc13: notify_files_delete: Process /usr/bin/g...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gthumb (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
Fedora Extras Quality Assurance
abrt_hash:7f45479f0f1b91b47d4b7b29263...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-27 18:14 EDT by Tim Jackson
Modified: 2010-06-08 08:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-08 08:58:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (34.63 KB, text/plain)
2010-05-27 18:14 EDT, Tim Jackson
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 608717 None None None Never

  None (edit)
Description Tim Jackson 2010-05-27 18:14:27 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gthumb '/home/tim/Desktop/for silvia/Pictures/2009-08-Sweden/p8150008.jpg'
component: gthumb
crash_function: notify_files_delete
executable: /usr/bin/gthumb
global_uuid: 7f45479f0f1b91b47d4b7b2926334d3bd851e558
kernel: 2.6.33.4-95.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
-----
1. View directory full of images
2. Press "delete" key lots of times in quick succession, so that gthumb "gets ahead" of itself
Comment 1 Tim Jackson 2010-05-27 18:14:30 EDT
Created attachment 417404 [details]
File: backtrace
Comment 2 Michael J. Chudobiak 2010-06-08 08:58:25 EDT
http://bugzilla.gnome.org/show_bug.cgi?id=608717

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