"nfs shares are usually local" We have a lot of ambiguity with the word local here, which is the entire problem. I'm not sure what local means in "nfs shares are usually local" - on the local host? On the same subnet? In the same location? In the same organization? In the same city? Furthermore, on what basis are these assumptions being made, I've seen plenty of NFS shares from machines in say, Tokyo or London to machines in New York. The basis for making this bug invalid is ambiguous, and where it is not ambiguous I don't know on what basis someone would say NFS shares are usually local. And even if NFS shares were local 75% of the time, whatever local means, what would that have to do with the failure rate the other 25% of the time.
I assume local in this specific context means whatever GIO/GVFS for Nautilus considers local. Upstream did implement it this way, but I think they should be alerted to this ambiguity. I had the same problem myself today before I came across this bug report. Even if they do choose to let it remain, I think there should be thought into changing this locally. Isn't the entire point of the Ubuntu desktop, as opposed to say Debian or Gentoo or whatever, to be user- friendly? I've been a professional Unix systems administrator since the mid-1990s, and I can't make heads or tails by what Nautilus means by local, even looking over the code and documentation. So what hope has the average Ubuntu user? I will be reporting this upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/293311 Title: nautilus thumbnails files on a mounted NFS share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/293311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs