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 457353 - crash in gThumb Image Viewer: I unmount and unplug the...
crash in gThumb Image Viewer: I unmount and unplug the...
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-07-16 13:37 UTC by henryl
Modified: 2007-07-16 14:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description henryl 2007-07-16 13:37:55 UTC 
What were you doing when the application crashed?
I unmount and unplug the CF card from the card reader and then gthumb crashed


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: 479563776 vsize: 0 resident: 479563776 share: 0 rss: 112840704 rss_rlim: 0
CPU usage: start_time: 1184587930 rtime: 0 utime: 7218 stime: 0 cutime:6509 cstime: 0 timeout: 709 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 -1208531248 (LWP 4771)]
[New Thread -1510954096 (LWP 4786)]
[New Thread -1500464240 (LWP 4785)]
[New Thread -1489974384 (LWP 4784)]
[New Thread -1479484528 (LWP 4783)]
[New Thread -1406047344 (LWP 4775)]
[New Thread -1266242672 (LWP 4774)]
(no debugging symbols found)
0x008d5402 in __kernel_vsyscall ()

+ Trace 148352

Thread 1 (Thread -1208531248 (LWP 4771))

  • #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 (10 sec old) ---------------------
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
closing
closing
** (bug-buddy:5265): WARNING **: 無法載入 開啟資料夾 的圖示
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-07-16 14:37:48 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 ***