Closed
Bug 322794
Opened 19 years ago
Closed 8 years ago
On Win32 deleting a profile that contains filesystem objects with the read-only attribute set
Categories
(Core Graveyard :: Profile: BackEnd, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: robert.strong.bugs, Unassigned)
References
(Blocks 1 open bug)
Details
If you select delete profile from the profile manager the profile's files are not deleted since we respect the read-only attribute and the user does not receive any indication that the files have not been deleted. See bug 322426 for more information.
Comment 1•13 years ago
|
||
nsIFile supports a permissions attribute by the way which can be called to remove the read only flag (simply specify any kind of write flag). If we keep the suggested patch in Bug 322426 though this task will probably be auto fixed.
Updated•13 years ago
|
Assignee: nobody → netzen
Updated•11 years ago
|
Assignee: netzen → nobody
Blocks: 1243899
Comment 2•8 years ago
|
||
This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE. If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.
Reporter | ||
Comment 3•8 years ago
|
||
This shouldn't be an issue that is seen all that often now that we no longer support older versions of windows that set the read only attribute under several different circumstances.
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•