** Description changed:

+ Impact:
+ copies from/to samba share often end up hanging
+ 
+ Test case:
+ - visit a smb location in nautilus
+ - copies data from/to it (some non trivial directories makes the issues 
easier to trigger)
+ - the copy should complete without hanging
+ 
+ Regression potentiel:
+ Check that nautilus is still working correctly and than you don't have issues 
copies data from/to remote locations
+ 
+ ---
+ 
  Problem
  =======
  Copying files to and from samba shares (this includes Windows shares) is 
unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated 
samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB.
  
  Workaround
  ==========
  Until gvfs-smb is fixed, use the kernel samba client (cifs) that works 
reliably, is faster, but needs some terminal commands to get going:
  # sudo -s
  # mkdir /mnt/cifs
  # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER 
"//SAMBA_SERVER/SAMBA_SHARE" /mnt/cifs
  It will ask for you password, you can then access the shared files at 
/mnt/cifs.

** Description changed:

  Impact:
  copies from/to samba share often end up hanging
  
  Test case:
  - visit a smb location in nautilus
  - copies data from/to it (some non trivial directories makes the issues 
easier to trigger)
  - the copy should complete without hanging
  
  Regression potentiel:
- Check that nautilus is still working correctly and than you don't have issues 
copies data from/to remote locations
+ Check that nautilus is still working correctly and than you don't have issues 
copying data from/to remote locations
  
  ---
  
  Problem
  =======
  Copying files to and from samba shares (this includes Windows shares) is 
unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated 
samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB.
  
  Workaround
  ==========
  Until gvfs-smb is fixed, use the kernel samba client (cifs) that works 
reliably, is faster, but needs some terminal commands to get going:
  # sudo -s
  # mkdir /mnt/cifs
  # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER 
"//SAMBA_SERVER/SAMBA_SHARE" /mnt/cifs
  It will ask for you password, you can then access the shared files at 
/mnt/cifs.

-- 
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/1075923

Title:
  nautilus hangs copying large directories from a samba share

Status in GVFS:
  Fix Released
Status in “gvfs” package in Ubuntu:
  Fix Released
Status in “gvfs” source package in Precise:
  In Progress
Status in “gvfs” source package in Raring:
  In Progress

Bug description:
  Impact:
  copies from/to samba share often end up hanging

  Test case:
  - visit a smb location in nautilus
  - copies data from/to it (some non trivial directories makes the issues 
easier to trigger)
  - the copy should complete without hanging

  Regression potentiel:
  Check that nautilus is still working correctly and than you don't have issues 
copying data from/to remote locations

  ---

  Problem
  =======
  Copying files to and from samba shares (this includes Windows shares) is 
unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated 
samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB.

  Workaround
  ==========
  Until gvfs-smb is fixed, use the kernel samba client (cifs) that works 
reliably, is faster, but needs some terminal commands to get going:
  # sudo -s
  # mkdir /mnt/cifs
  # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER 
"//SAMBA_SERVER/SAMBA_SHARE" /mnt/cifs
  It will ask for you password, you can then access the shared files at 
/mnt/cifs.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to