372414 - localstore.rdf lose its R/O flag

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Edoardo Tirtarahardja]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10

I normally mark my localstore.rdf to R/O (Read Only) as I don't want my firefox layout dynamically change all the time. I notice that since version 1.5.0.10 (both FireFox & ThunderBird), my localstore.rdf loses its R/O flag everytime I start the application. Hence all my layout settings are can be dynamically changed.

What's wrong with the old implementation? Where one can mark localstore.rdf to R/O to get a static layout.

Reproducible: Always

Steps to Reproduce:
1. Set localstore.rdf to R/O.
2. Start FireFox (or ThunderBird) 1.5.0.10 and then close it.
3. Check the attribute of localstore.rdf.
Actual Results:  
The R/O attribute of localstore.rdf is resetted.

Expected Results:  
The file attribute should remain unchanged.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070301 Minefield/3.0a3pre
Yeah, I see this too. The read-only state unchecks itself while starting up.

Comment 2

[Edoardo Tirtarahardja]

Is any body from mozilla is taking care of this?
This is quite annoying! I'm too don't want my firefox & thunderbird dynamically change the layout all the time. I prefer a static localstore.rdf.

I found a workaround that by setting the ACL (need a Windows NTFS file system) to read only, it will prevent mozilla to remove the R/O flag.

However start in firefox & thunderbird 2.0.0.6, if they fail to remove the R/O flag, they rename the protexted localstore.rdf to localstore.rdf.moztmp and create another one. This is really bump me.

Is there any reason why the user are not allowed to protect their localstore.rdf?

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.