Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nautilus (Ubuntu)
       Status: New => Confirmed

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

Title:
  Natilus should ignore read only attribute for folders in a windows
  share

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Windows uses the read-only attribute for folders solely to indicate
  that this folder should be rendered in a special way (e.g. Fonts
  folder, Desctop, Videos, ...). So a folder with the read-only
  attribute set is actually considered writeable. Nautilus however
  considers it actually read only and deactivates certain features like
  creating files and folders. This should not happen.

  A description of the Windows behaviour is at 
http://support.microsoft.com/kb/326549 . Also the underlying smb and gvfs do 
allow proper write access (e.g. via shell commands). 
  Nautilus however interprets the missing "w" flag and deactivates certain 
operations.

  Nautilus should recognise that a folder is a smb mount and still
  assume write access.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.4
  ProcVersionSignature: Ubuntu 2.6.35-30.60-generic 2.6.35.13
  Uname: Linux 2.6.35-30-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Oct 21 11:42:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_AU:en_GB:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/879180/+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