GNOME Bugzilla – Bug 495647
crash in Open Folder: searching for a file
Last modified: 2007-11-15 09:01:08 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for a file Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 121442304 vsize: 121442304 resident: 55590912 share: 31490048 rss: 55590912 rss_rlim: 4294967295 CPU usage: start_time: 1194498937 rtime: 6540 utime: 5624 stime: 916 cutime:24 cstime: 37 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209010464 (LWP 2677)] [New Thread -1346286704 (LWP 21673)] (no debugging symbols found) 0x00f18402 in __kernel_vsyscall ()
+ Trace 176841
Thread 2 (Thread -1346286704 (LWP 21673))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libXxf86vm.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpoppler-glib.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpoppler.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, eel2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
I narrowed it down to a particular path that triggers it everytime. Looks like the special character in the path name is a possible culprit. This directory was created across a SMB share by a Windows Box. It's being searched by a Linux box (obviously) across a nfs mount. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 92274688 vsize: 92274688 resident: 29089792 share: 20254720 rss: 29089792 rss_rlim: 4294967295 CPU usage: start_time: 1195099971 rtime: 678 utime: 604 stime: 74 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208887584 (LWP 31216)] [New Thread -1307030640 (LWP 31416)] 0x0057e402 in __kernel_vsyscall ()
+ Trace 177806
Thread 2 (Thread -1307030640 (LWP 31416))
----------- .xsession-errors --------------------- d['amount'] TypeError: GtkEntry.set_text() argument 1 must be string, not None (gourmet:30886): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (gourmet:30886): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gourmet:30886): Gtk-CRITICAL **: gtk_accel_group_disconnect: assertion `GTK_IS_ACCEL_GROUP (accel_group)' failed (nautilus:30705): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x20efa)! (nautilus:31216): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Cannot access memory at address 0xf Cannot access memory at address 0xf --------------------------------------------------
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 454799 ***