I confirm this bug. And it is not a duplicate of #1069255.

To reproduce:
1) Share the drive from Windows where your pagefile resides (ie c:)
2) Browse it and mount it with Thunar. 
3) Try to list the contents of directory with Thunar, you will receive an error 
that pagefile.sys resource busy. You won't be able to see folder contents.
normal ls  on the /run/user/username/gvfs/mounted_location/ works.


** This bug is no longer a duplicate of bug 1069255
   gvfs fuse mounts moved from .gvfs to /run/user/<user>/gvfs is confusing users

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1070652

Title:
  [regression] [Quantal] can't browse to gvfs share

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  When running Precise, I used the ~/.gvfs directory to access a file or
  directory on a windows share from applications (primarily Thunderbird)
  that didn't support network browsing.  Now, with Quantal, although the
  mounted directory appears in /run/user/<username>/gvfs, it isn't
  browsable, either from a file browser (I tried thunar and dolphin) or
  from the Thunderbird file browser window.  When I mount the C drive
  and try to browse it, I get a message in Thunar that pagefile.sys is
  not available.  When I mount a subdirectory under C and try to browse
  it, nothing happens.

  Also, when I try to browse the share, Thunar and Thunderbird go into
  zombie state.

  I can browse the share in Thunar using smb:// but that doesn't work
  from Thunderbird file browser.

  Attached is a file showing the readout in kernel log when I try to
  browse the share in the gvfs directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1070652/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to