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 370878 - crash in gThumb Image Viewer: Resizing one of gthumb's...
crash in gThumb Image Viewer: Resizing one of gthumb's...
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: 2006-11-05 05:51 UTC by normpritchett
Modified: 2006-11-05 10:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description normpritchett 2006-11-05 05:51:31 UTC
What were you doing when the application crashed?
Resizing one of gthumb's panes while viewing a high-res image taken on my Canon EOS Digital SLR camera.


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

Memory status: size: 366145536 vsize: 0 resident: 366145536 share: 0 rss: 86831104 rss_rlim: 0
CPU usage: start_time: 1162703294 rtime: 0 utime: 58034 stime: 0 cutime:48028 cstime: 0 timeout: 10006 it_real_value: 0 frequency: 13

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 -1208199472 (LWP 3348)]
[New Thread -1464407152 (LWP 3365)]
[New Thread -1453917296 (LWP 3364)]
[New Thread -1443427440 (LWP 3363)]
[New Thread -1432937584 (LWP 3362)]
[New Thread -1349018736 (LWP 3354)]
[New Thread -1252811888 (LWP 3353)]
(no debugging symbols found)
0x0025d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208199472 (LWP 3348))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/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 2006-11-05 10:18:31 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 bug has been marked as a duplicate of 356623 ***