Bug 468333 – crash in gThumb Image Viewer: Modifying the brightness...

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 468333 - crash in gThumb Image Viewer: Modifying the brightness...


Summary:	crash in gThumb Image Viewer: Modifying the brightness...


Status:	RESOLVED DUPLICATE of bug 392234

Product:	gthumb
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-19 22:33 UTC by sarahandjoel
Modified:	2007-08-19 22:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description sarahandjoel 2007-08-19 22:33:59 UTC

What were you doing when the application crashed?
Modifying the brightness/contrast of a photo. I had clicked "OK" when it crashed.


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

Memory status: size: 173027328 vsize: 0 resident: 173027328 share: 0 rss: 55357440 rss_rlim: 0
CPU usage: start_time: 1187549863 rtime: 0 utime: 10268 stime: 0 cutime:9785 cstime: 0 timeout: 483 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 -1226959184 (LWP 5344)]
[New Thread -1322665056 (LWP 5358)]
[New Thread -1314272352 (LWP 5357)]
[New Thread -1305879648 (LWP 5356)]
[New Thread -1263842400 (LWP 5351)]
[New Thread -1237054560 (LWP 5347)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 156440

Thread 1 (Thread -1226959184 (LWP 5344))

#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 André Klapper 2007-08-19 22:53:33 UTC

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.


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