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 398044 - crash in gThumb Image Viewer:
crash in gThumb Image Viewer:
Status: RESOLVED DUPLICATE of bug 356623
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-01-18 15:44 UTC by kjetil
Modified: 2007-01-18 15:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kjetil 2007-01-18 15:44:31 UTC
What were you doing when the application crashed?



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.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors ---------------------
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
(evolution:3546): e-data-server-WARNING **: e_source_get_uri () called on source with no absolute URI!
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
in emp_apps_open_in
--------------------------------------------------

Memory status: size: 351133696 vsize: 0 resident: 351133696 share: 0 rss: 32555008 rss_rlim: 0
CPU usage: start_time: 1169130755 rtime: 0 utime: 1176 stime: 0 cutime:1083 cstime: 0 timeout: 93 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208846640 (LWP 24184)]
[New Thread -1443902576 (LWP 24195)]
[New Thread -1433412720 (LWP 24194)]
[New Thread -1422922864 (LWP 24193)]
[New Thread -1412433008 (LWP 24192)]
[New Thread -1379644528 (LWP 24188)]
[New Thread -1263453296 (LWP 24187)]
(no debugging symbols found)
0x008e4402 in __kernel_vsyscall ()

Thread 1 (Thread -1208846640 (LWP 24184))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gth_location_new
  • #5 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 g_signal_override_class_closure
    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 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #11 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib/libgnomevfs-2.so.0
  • #12 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #13 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #14 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #0 __kernel_vsyscall

Comment 1 Michael Chudobiak 2007-01-18 15:50:18 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 ***