Bug 400449 – crash in gThumb Image Viewer: Attempting to view a jpe...

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 400449 - crash in gThumb Image Viewer: Attempting to view a jpe...


Summary:	crash in gThumb Image Viewer: Attempting to view a jpe...


Status:	RESOLVED DUPLICATE of bug 356623

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-01-25 01:03 UTC by Dave Mann
Modified:	2007-01-25 10:51 UTC

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

Description Dave Mann 2007-01-25 01:03:46 UTC

What were you doing when the application crashed?
Attempting to view a jpeg image


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2869.fc6xen #1 SMP Wed Dec 20 15:08:52 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (636135 sec old) ---------------------
  Resource id:  0x64
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1446558
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  155
  Minor opcode:  6
  Resource id:  0x1446558
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  155
  Minor opcode:  6
  Resource id:  0x64
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 763535360 vsize: 763535360 resident: 95449088 share: 15200256 rss: 95449088 rss_rlim: -1
CPU usage: start_time: 1169686420 rtime: 958 utime: 837 stime: 121 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496367968 (LWP 14946)]
[New Thread 1136679232 (LWP 14956)]
[New Thread 1126189376 (LWP 14955)]
[New Thread 1115699520 (LWP 14952)]
[New Thread 1105209664 (LWP 14951)]
[New Thread 1094719808 (LWP 14950)]
[New Thread 1084229952 (LWP 14949)]
(no debugging symbols found)
0x00000032c120d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 105025

Thread 1 (Thread 46912496367968 (LWP 14946))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gth_location_new
#4 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#5 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /lib64/libgobject-2.0.so.0
#8 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib64/libgnomevfs-2.so.0
#9 gnome_vfs_volume_monitor_client_shutdown_private
from /usr/lib64/libgnomevfs-2.so.0
#10 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#11 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#12 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#13 g_main_context_check
from /lib64/libglib-2.0.so.0
#14 g_main_loop_run
from /lib64/libglib-2.0.so.0
#15 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#16 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Michael Chudobiak 2007-01-25 10:51:25 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This is fixed in 2.8.x and 2.9.x, available at
http://ftp.gnome.org/pub/gnome/sources/gthumb/2.8/ and
http://ftp.gnome.org/pub/gnome/sources/gthumb/2.9/.

This is fixed in the FC7 development repo ("rawhide").

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