Bug 509080 - Can not clear Read-only attribute
Can not clear Read-only attribute
Product: Fedora
Classification: Fedora
Component: samba (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Simo Sorce
Fedora Extras Quality Assurance
Depends On:
Blocks: 516996
  Show dependency treegraph
Reported: 2009-07-01 05:06 EDT by Jérôme Audu
Modified: 2009-09-10 04:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-10 04:20:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
rpmdev-diff of samba-3.3.2-0.33.fc11.src.rpm with Jeremy Allison fix (4.42 KB, patch)
2009-07-01 05:06 EDT, Jérôme Audu
no flags Details | Diff

  None (edit)
Description Jérôme Audu 2009-07-01 05:06:26 EDT
Created attachment 350073 [details]
rpmdev-diff of samba-3.3.2-0.33.fc11.src.rpm with Jeremy Allison fix

Description of problem:

Unable to change the attribute of a Samba shared file from WinXP client
from "Read-only" to "Writable"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Setup a shared Samba directory, and access it from WinXP client.
2. From WinXP, Select a file and set it as ReadOnly:
  Properties => Attributes => Read-Only  [X] (Then apply)
3. From WinXP, Select the same file and uncheck Read-Only flags:
  Properties => Attributes => Read-Only  [ ] (Then apply)

Actual results:

Step 3 failed on WinXP client with "An error occurred applying attributes to the file"

Expected results:

Read-Only flags on selected file removed. 

Additional info:

Bug already raised on samba ML:

And a fix here:

I've tested this patch and it fix my issue.
I've attached my modification to samba-3.3.2-0.33.fc11.src.rpm (.SPEC + patch)
Comment 1 Jérôme Audu 2009-09-10 04:20:08 EDT
I've just checked with the new released "samba-3.4.1-0.41.fc11" (from testing-update) and it seem to fix this problem.

Note You need to log in before you can comment on or make changes to this bug.