GNOME Bugzilla – Bug 461055
crash in Computer: I was renaming a folder ...
Last modified: 2007-09-11 14:54:31 UTC
Version: 2.18.3 What were you doing when the application crashed? I was renaming a folder (over ssh) 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.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 115990528 vsize: 115990528 resident: 45436928 share: 27996160 rss: 45436928 rss_rlim: 4294967295 CPU usage: start_time: 1185558926 rtime: 2565 utime: 2455 stime: 110 cutime:23 cstime: 5 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208949024 (LWP 2776)] [New Thread -1211565168 (LWP 4090)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151034
Thread 1 (Thread -1208949024 (LWP 2776))
----------- .xsession-errors --------------------- *** WARNING *** The programme 'pidgin' uses the HOWL compatiblity layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=howl&e=pidgin> ** (nm-applet:2797): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.NetworkNotFound) The requested network does not exist for this device. ** (nm-applet:2797): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.NetworkNotFound) The requested network does not exist for this device. ** (nautilus:2776): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 465145 has been marked as a duplicate of this bug. ***
bug 465786 has a more complete trace
*** This bug has been marked as a duplicate of 465786 ***