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 381832 - crash in gThumb Image Viewer: Plugged my Minolta A200 ...
crash in gThumb Image Viewer: Plugged my Minolta A200 ...
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-12-03 09:57 UTC by Paul-Erik Törrönen
Modified: 2006-12-03 14:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Paul-Erik Törrönen 2006-12-03 09:57:18 UTC 
What were you doing when the application crashed?
Plugged my Minolta A200 to a USB port


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.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 442277888 vsize: 0 resident: 442277888 share: 0 rss: 90624000 rss_rlim: 0
CPU usage: start_time: 1164648438 rtime: 0 utime: 9604 stime: 0 cutime:8702 cstime: 0 timeout: 902 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 -1208817968 (LWP 17144)]
[New Thread -1517327472 (LWP 17159)]
[New Thread -1506837616 (LWP 17158)]
[New Thread -1496347760 (LWP 17157)]
[New Thread -1485857904 (LWP 17156)]
[New Thread -1401939056 (LWP 17148)]
[New Thread -1271059568 (LWP 17147)]
(no debugging symbols found)
0x00a69402 in __kernel_vsyscall ()

+ Trace 91235

Thread 1 (Thread -1208817968 (LWP 17144))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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





          2006-12-03 14:32:37 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 gThumb 2.8.0.

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