Bug 607098

Summary: [abrt] crash in gthumb-2.11.3-1.fc13: scale_line: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kirill <aukcyon>
Component: gthumbAssignee: Christian Krause <chkr>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: behdad, el_gallo_azul, fmolina, ma3x_smith, marbolangos, nuno.dias, paduparchy
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:03319c036864b1ed1257453c2c1fa223915134f5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-05 23:20:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description Kirill 2010-06-23 08:25:22 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb /home/anabena/Desktop/Zzz/103.100.301-1.jpg
component: gthumb
crash_function: scale_line
executable: /usr/bin/gthumb
global_uuid: 03319c036864b1ed1257453c2c1fa223915134f5
kernel: 2.6.33.5-124.fc13.i686
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)

Comment 1 Kirill 2010-06-23 08:25:25 UTC
Created attachment 426196 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2010-07-17 22:08:21 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:23:36 UTC
*** Bug 613406 has been marked as a duplicate of this bug. ***

Comment 4 Benjamín Valero Espinosa 2010-08-02 22:24:50 UTC
*** Bug 613408 has been marked as a duplicate of this bug. ***

Comment 5 Benjamín Valero Espinosa 2010-08-02 22:26:10 UTC
*** Bug 616565 has been marked as a duplicate of this bug. ***

Comment 6 Benjamín Valero Espinosa 2010-08-02 22:27:21 UTC
*** Bug 620229 has been marked as a duplicate of this bug. ***

Comment 7 Fermin Molina 2010-08-02 23:03:18 UTC
Anything new about this bug?

Comment 8 Greg Flint 2010-08-18 08:07:24 UTC
Package: gthumb-2.11.5-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Resize photos using Tools -> Resize images
2. Choose "Overwrite all files"
3. 


Comment
-----
Tried to resize photos as described above. Everything looked like it worked until the last file selected, however all the files except the first one were the original size.

Comment 9 Greg Flint 2010-08-18 08:14:00 UTC
Package: gthumb-2.11.5-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. See previous
2.
3.


Comment
-----
See previous

Comment 10 Christian Krause 2010-08-18 19:42:08 UTC
*** Bug 624946 has been marked as a duplicate of this bug. ***

Comment 11 Christian Krause 2010-08-18 19:43:26 UTC
*** Bug 624953 has been marked as a duplicate of this bug. ***

Comment 12 Fabien Archambault 2010-08-19 10:14:34 UTC
I think this is reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=623071

Comment 13 Greg Flint 2010-08-20 07:22:57 UTC
Yep. Thanks Fabien.

Comment 14 Christian Krause 2010-08-29 16:49:45 UTC
Unfortunately I can't reproduce the problem.

1. Can anyone of the reporters of this bug reproduce it? If yes, please report the exact steps. If it happens only with some specific pictures, please provide them as well (if possible).

2. Please test, whether the problem can be still reproduced with the newest version in updates-testing:
https://admin.fedoraproject.org/updates/gthumb-2.11.90-3.fc13
It can be installed with:
su -c 'yum --enablerepo=updates-testing update gthumb'

Comment 15 Christian Krause 2010-11-05 23:20:06 UTC
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.