GNOME Bugzilla – Bug 365624
crash in Computer: I was browsing a file sy...
Last modified: 2008-09-06 19:03:22 UTC
What were you doing when the application crashed? I was browsing a file system using nautilus. I used an ftp URI such as ftp://10.0.0.1 to connect and this worked. I browsed around and then nautilus crashed on a particular folder. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 133918720 vsize: 0 resident: 133918720 share: 0 rss: 29573120 rss_rlim: 0 CPU usage: start_time: 1161931623 rtime: 0 utime: 966 stime: 0 cutime:847 cstime: 0 timeout: 119 it_real_value: 0 frequency: 0 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 -1208501504 (LWP 2682)] [New Thread -1210606704 (LWP 5515)] (no debugging symbols found) 0x0021e402 in __kernel_vsyscall ()
+ Trace 78713
Thread 2 (Thread -1210606704 (LWP 5515))
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. Thanks in advance! Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 366025 ***
*** Bug 369174 has been marked as a duplicate of this bug. ***
Nope, not the same issue...
*** Bug 416345 has been marked as a duplicate of this bug. ***
*** Bug 416346 has been marked as a duplicate of this bug. ***
*** Bug 416348 has been marked as a duplicate of this bug. ***
*** Bug 422855 has been marked as a duplicate of this bug. ***
One duplicate from gnome-commander. Moving to gnome-vfs.
*** Bug 431460 has been marked as a duplicate of this bug. ***
*** Bug 431458 has been marked as a duplicate of this bug. ***
*** Bug 477646 has been marked as a duplicate of this bug. ***
*** Bug 493299 has been marked as a duplicate of this bug. ***
*** Bug 493314 has been marked as a duplicate of this bug. ***
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 debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
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 11:56:20 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 471126016 vsize: 471126016 resident: 36773888 share: 20189184 rss: 36773888 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194556394 rtime: 118 utime: 100 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496380976 (LWP 4576)] [New Thread 1168148816 (LWP 4599)] 0x0000003dc4ec82e6 in poll () from /lib64/libc.so.6
+ Trace 176433
Thread 2 (Thread 1168148816 (LWP 4599))
----------- .xsession-errors (640 sec old) --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now report junk?? [bestuur] Happy Diwali --------------------------------------------------
The most relevant part from my remarks on bug 493299: ----------------------------------------------------- This bug is caused by the link on the remote ftp server pointing to the parent directory (which isn't accessible because of the chroot). I have made a test setup with a anonymous chrooted ftp server with only one link in the root pointing to the chrooted parent. This link triggers the crash (i have tested other links and files as well). The directory listing on the node: # pwd /home/ftp # ls -la total 8 dr-xr-xr-x 2 ftp ftp 4096 Nov 4 11:22 . drwxr-xr-x 8 root root 4096 Nov 4 11:21 .. lrwxrwxrwx 1 root root 2 Nov 4 11:21 p -> .. Through "lftp": $ lftp paard lftp paard:~> ls lrwxrwxrwx 1 0 0 2 Nov 04 10:21 p -> .. With this information you should be able to reproduce the problem in the lab as well. Besides that the ftp server "ftp://ftp.nluug.nl" has that problem but the sysadmin promised me to correct that.
*** Bug 452093 has been marked as a duplicate of this bug. ***
thanks for the good trace! so the crash seems to happen in if (strcmp (gnome_vfs_uri_get_host_name (uri), gnome_vfs_uri_get_host_name (link_uri)) != 0) would be interesting to know whether this has been fixed by bug 435823 (the fix should be included in gnome-vfs 2.18.3). note to myself: bug 367521 could be another duplicate of this bug.
<pbor> it should probably check that link_uri returned by gnome_vfs_uri_resolve_relative is not NULL
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together. General further information: http://en.wikipedia.org/wiki/GVFS Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html