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 439964 - crash in gThumb Image Viewer: changing hue -color leve...
crash in gThumb Image Viewer: changing hue -color leve...
Status: RESOLVED DUPLICATE of bug 392234
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-05-20 16:05 UTC by joel
Modified: 2007-05-20 17:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description joel 2007-05-20 16:05:42 UTC 
What were you doing when the application crashed?
changing hue -color level Cyan-red,
after also changing bright-Contrast & Hue-saturation



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 388026368 vsize: 0 resident: 388026368 share: 0 rss: 98529280 rss_rlim: 0
CPU usage: start_time: 1178499867 rtime: 0 utime: 12222 stime: 0 cutime:11505 cstime: 0 timeout: 717 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208604976 (LWP 14369)]
[New Thread -1564386416 (LWP 19280)]
[New Thread -1553896560 (LWP 19279)]
[New Thread -1543406704 (LWP 19278)]
[New Thread -1532916848 (LWP 19277)]
[New Thread -1424323696 (LWP 19267)]
[New Thread -1437381744 (LWP 19266)]
[New Thread -1380111472 (LWP 14441)]
[New Thread -1369621616 (LWP 14440)]
[New Thread -1359131760 (LWP 14439)]
[New Thread -1348641904 (LWP 14438)]
[New Thread -1235199088 (LWP 14435)]
[New Thread -1245688944 (LWP 14434)]
(no debugging symbols found)
0x001fb402 in __kernel_vsyscall ()

+ Trace 135180

Thread 1 (Thread -1208604976 (LWP 14369))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/gthumb/libgthumb.so
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 __kernel_vsyscall 






Comment 1


Michael Chudobiak





          2007-05-20 17:07:38 UTC
        



Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade (use 2.10.2 or later).


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