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 475643 - crash in gThumb Image Viewer: I took out the usb port ...
crash in gThumb Image Viewer: I took out the usb port ...
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-09-10 22:34 UTC by debcu2
Modified: 2007-09-10 23:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description debcu2 2007-09-10 22:34:22 UTC 
What were you doing when the application crashed?
I took out the usb port from my camera to take another picture.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2962.fc6 #1 SMP Tue Jun 19 18:24:12 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 265502720 vsize: 0 resident: 265502720 share: 0 rss: 115740672 rss_rlim: 0
CPU usage: start_time: 1189463650 rtime: 0 utime: 2186 stime: 0 cutime:2074 cstime: 0 timeout: 112 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 -1208662320 (LWP 25863)]
[New Thread -1436820592 (LWP 25882)]
[New Thread -1426330736 (LWP 25881)]
[New Thread -1415840880 (LWP 25880)]
[New Thread -1405351024 (LWP 25879)]
[New Thread -1289962608 (LWP 25867)]
[New Thread -1233486960 (LWP 25866)]
(no debugging symbols found)
0x00fdd402 in __kernel_vsyscall ()

+ Trace 161909

Thread 1 (Thread -1208662320 (LWP 25863))

  • #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_chain_from_overridden
    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 


----------- .xsession-errors (76 sec old) ---------------------
localuser:deb being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/19172
** Message: <information>	You are now connected to the wireless network 'coconet'.
** Message: <information>	You are now connected to the wireless network 'coconet'.
** Message: <information>	You are now connected to the wireless network 'coconet'.
** Message: <information>	You are now connected to the wireless network 'coconet'.
** Message: <information>	You are now connected to the wireless network 'coconet'.
save exif data
save exif data
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-09-10 23:36:23 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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