After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 128508 - Subject: JPEG Lossless rotation dialog can crash gThumb
Subject: JPEG Lossless rotation dialog can crash gThumb
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other Linux
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2003-12-04 12:21 UTC by rngadam
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description rngadam 2003-12-04 12:21:15 UTC
Package: gthumb 2.0.2
Severity: major
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: JPEG Lossless rotation dialog can crash gThumb
Bugzilla-Product: gthumb
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

JPEG Lossless rotation dialog can crash gThumb, possibly because of
concurrency problem?

Steps to reproduce the crash:
1. Pick a file with a large size to rotate that will take a while to
apply
2. Click on the rotation you want and...
3. ...As quick as possible, click on the 'Revert to disk' icon
4. ...As quick as possible, click on OK

Expected Results:

The operation is cancelled, the image remain unchanged, the user is
returned to the prompt.
Or maybe the OK button should be disabled until all operations are
completed (rotation OR revert to disk)?

How often does this happen?

I can reproduce this bug reliably manually (repeating the sequence until
it crashes) with different source images.

Additional Information:

One of the test image is a ~600K.
Can't get the latest gthumb version to compile on my workstation install

Debugging Information:

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread -1084983616 (LWP 1994)]
[New Thread -1150514256 (LWP 2001)]
[New Thread -1139631184 (LWP 2000)]
[New Thread -1129141328 (LWP 1999)]
[New Thread -1118651472 (LWP 1998)]
[New Thread -1108161616 (LWP 1997)]
[New Thread -1097598032 (LWP 1996)]
[New Thread -1087108176 (LWP 1995)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x00b9dc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -1084983616 (LWP 1994))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 image_loader_set_pixbuf
  • #5 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #6 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2

Comment 1 Elijah Newren 2003-12-08 04:48:37 UTC
Looks like a duplicate of either bug 115730, bug 117401, or bug
127109, all of which have been marked as fixed.  I'm not sure if it's
a dupicate however, so I'll leave it open.
Comment 2 Alexander Kirillov 2004-01-23 16:32:35 UTC
Version 2.0.2 is quite old, and most crashes have been fixed since.
Closing. Please reopen if you can reproduce the crash with a recent
version (2.2.0 or 2.3.0 - RPMs for both of the are avaialble).