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 431913 - crash in gThumb Image Viewer: I just umount the CF car...
crash in gThumb Image Viewer: I just umount the CF car...
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-04-21 06:32 UTC by henryl
Modified: 2007-04-21 13:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description henryl 2007-04-21 06:32:31 UTC 
What were you doing when the application crashed?
I just umount the CF card and remove it from the card reader. This is the second time I got this problem. I already applied the latest updates today.


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.2944.fc6 #1 SMP Tue Apr 10 17:27:49 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 292098048 vsize: 0 resident: 292098048 share: 0 rss: 72323072 rss_rlim: 0
CPU usage: start_time: 1177136406 rtime: 0 utime: 8753 stime: 0 cutime:8015 cstime: 0 timeout: 738 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 -1208596784 (LWP 5314)]
[New Thread -1374852208 (LWP 5325)]
[New Thread -1364362352 (LWP 5324)]
[New Thread -1353872496 (LWP 5323)]
[New Thread -1343382640 (LWP 5322)]
[New Thread -1311904880 (LWP 5318)]
[New Thread -1234883696 (LWP 5317)]
(no debugging symbols found)
0x00492402 in __kernel_vsyscall ()

+ Trace 129460

Thread 1 (Thread -1208596784 (LWP 5314))

  • #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 (16 sec old) ---------------------
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:3143): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
closing
** (bug-buddy:5658): WARNING **: 無法載入 開啟資料夾 的圖示
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-04-21 13:12:32 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 ***