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 463231 - crash in gThumb Image Viewer: It MIGHT have been when ...
crash in gThumb Image Viewer: It MIGHT have been when ...
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-08-03 19:16 UTC by eleanorsf
Modified: 2007-08-03 20:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description eleanorsf 2007-08-03 19:16:31 UTC 
What were you doing when the application crashed?
It MIGHT have been when I automounted a USB ntfs-3g disk that has pictures in a volume top level directory called photos. ntfs-3g correctly read/write mounted the disk.


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.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 248180736 vsize: 0 resident: 248180736 share: 0 rss: 5877760 rss_rlim: 0
CPU usage: start_time: 1186007772 rtime: 0 utime: 7403 stime: 0 cutime:7038 cstime: 0 timeout: 365 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 -1208703280 (LWP 27540)]
[New Thread -1339245680 (LWP 27551)]
[New Thread -1328755824 (LWP 27550)]
[New Thread -1318265968 (LWP 27549)]
[New Thread -1307776112 (LWP 27548)]
[New Thread -1276306544 (LWP 27544)]
[New Thread -1228874864 (LWP 27543)]
(no debugging symbols found)
0x004fc402 in __kernel_vsyscall ()

+ Trace 152619

Thread 1 (Thread -1208703280 (LWP 27540))

  • #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 ---------------------
ScimInputContextPlugin()
WARNING: please edit ~/.scim/global and change /DefaultConfigModule to kconfig
DCOP: unregister 'kpdf-6120'
~ScimInputContextPlugin()
Loading "installonlyn" plugin
/home/me/Desktop/flash-plugin-9.0.48.0-release.i386.rpm is already installed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x107a368 ().
** (nautilus:2982): WARNING **: unknown sort column id: -1
** (nautilus:2982): WARNING **: unknown sort column id: 135000251
** (nautilus:2982): WARNING **: unknown sort column id: -1
** (bug-buddy:10154): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-08-03 20:26:38 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 ***