#7260 HIGH Never A: Browse Activity Can't Read NFS Mounts

[Zarro Boogs per Child]

#7260: Browse Activity Can't Read NFS Mounts
-----------------------------+----------------------------------------------
 Reporter:  jcolag           |       Owner:  erikos        
     Type:  defect           |      Status:  new           
 Priority:  high             |   Milestone:  Never Assigned
Component:  browse-activity  |     Version:  Update.1      
 Keywords:                   |    Verified:  0             
 Blocking:                   |   Blockedby:                
-----------------------------+----------------------------------------------
 Reproduction is simple:  With nfs-utils installed and running, mount a
 remote drive as root.  From Terminal, everything works fine (provided the
 directory was properly shared, of course).  However, Browse does one of
 two weird things.

 If you started Browse before issuing the mount command, Browse doesn't see
 anything new; you can still see whatever files were placed (locally) at
 the mount point.

 By contrast, if you started Browse after mounting the directory,
 Browse...refuses to acknowledge the mounted directory at all.
 Specifically, if you type the directory into the address bar
 (file:///mnt/...) or click on it from the parent, you'll see a quick burst
 of network activity, followed by no effect whatsoever.  The action is
 ignored and the only evidence remaining is the change in address bar (but
 not the title bar that shares the screen space).

 The best point of reference I can give you is that this problem didn't
 exist in build 656, and still works fine when I revert.  Permissions
 (server- or client-side) don't appear to make any difference.

 Unfortunately, I don't know enough about NFS or how Browse/Mozilla caches
 and accesses shared directories to debug further than that.  I doubt that
 my setup is unique in any way (I ran the update the other day and then
 installed nfs-utils, for the most part), but if you need me to do any
 further testing on the issue, I'd be happy to give it a try.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7260>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system