375153 - toolbar button configuration does not save for non-admin user

Status: RESOLVED INCOMPLETE

(Thunderbird :: Mail Window Front End, defect)

Description

[Shaheen Tonse]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: Thunderbird 1.5.0.10

I have Thunderbird on my new Vista PC. When logged in as the non-sysadmin user,
if I change the buttons, say , adding "File" and removing "Print", whatever I do is lost if I quit Tbird and restart it.
However if I do this as sysadmin then it is saved and next session comes up as I had reconfigured it. 
Some file access/protection problem somewhere? I could not find it.

Reproducible: Always

Steps to Reproduce:
1. Start Tbird.
2.Click button toolbar, customize. Change buttons. Quit Tbird. Restart Tbird
3. Repeat "2" but as sysadmin.


Expected Results:  
Should have saved button configuration and reproduced it next session

Comment 1

[Magnus Melin [:mkmelin]]

Vista should work a lot better on 2.0. Can you try a recent nightly? <http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8/>

Comment 2

[Shaheen Tonse]

I upgraded to Thunderbird 2.0pre (20070324) but the problem is still there. I suspect that it is because of some settings file that I as a non-sysadmin user do not have privilege to write to. As I mentioned before, when I did this as sysadmin, then the settings were saved properly. After doing it as sysyadmin I looked for files that had been updated in the last few minutes but could not find any. 

Comment 3

[Magnus Melin [:mkmelin]]

Don't know what happened, but make sure all files in your profile are writable without admin right. <http://kb.mozillazine.org/Profile_folder>

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.16)

Comment 5

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to previous comment. If you feel this change was made in error, please respond to the bug with your reasons why.