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 392234 - crash in gThumb Image Viewer: Adjusting brightness/con...
crash in gThumb Image Viewer: Adjusting brightness/con...
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
: 402665 406331 415066 423715 439964 468333 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-03 10:21 UTC by snelting
Modified: 2007-08-19 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description snelting 2007-01-03 10:21:21 UTC
What were you doing when the application crashed?
Adjusting brightness/contrast of an image I had just cropped (but not saved)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 244727808 vsize: 0 resident: 244727808 share: 0 rss: 47919104 rss_rlim: 0
CPU usage: start_time: 1167819575 rtime: 0 utime: 927 stime: 0 cutime:891 cstime: 0 timeout: 36 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227618640 (LWP 13540)]
[New Thread -1461724256 (LWP 13558)]
[New Thread -1453331552 (LWP 13557)]
[New Thread -1444938848 (LWP 13556)]
[New Thread -1350874208 (LWP 13545)]
[New Thread -1267287136 (LWP 13542)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227618640 (LWP 13540))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_widget_queue_draw
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 dlg_brightness_contrast
  • #6 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gth_pixbuf_op_set_single_step
    from /usr/lib/libgthumb.so
  • #12 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 main
  • #0 __kernel_vsyscall

Comment 1 snelting 2007-01-03 12:04:15 UTC
Had the same crash happening a few times -- Crash only happens when I type values in the boxes directly, instead of using the slider.
Comment 2 Michael Chudobiak 2007-01-31 12:31:19 UTC
*** Bug 402665 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2007-02-10 15:35:06 UTC
*** Bug 406331 has been marked as a duplicate of this bug. ***
Comment 4 Michael Chudobiak 2007-03-05 21:07:53 UTC
*** Bug 415066 has been marked as a duplicate of this bug. ***
Comment 5 Michael Chudobiak 2007-03-28 13:23:16 UTC
*** Bug 423715 has been marked as a duplicate of this bug. ***
Comment 6 Michael Chudobiak 2007-03-28 14:41:14 UTC
Can anyone reproduce this bug reliably? I can't reproduce it with gThumb 2.10.1.

- Mike
Comment 7 Michael Chudobiak 2007-04-09 18:26:46 UTC
This problem has been fixed in the development version (svn rev 1527-1529). The fix will be available in the next major software release (2.10.2). Thank you for your bug report.
Comment 8 Michael Chudobiak 2007-05-20 17:07:38 UTC
*** Bug 439964 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2007-08-19 22:53:33 UTC
*** Bug 468333 has been marked as a duplicate of this bug. ***