Open Bug 1444057 Opened 8 years ago Updated 3 years ago

Thunderbird loads always the default max cache space value. Works with lockPref("browser.cache.disk.capacity", <my_value>)

Categories

(Thunderbird :: Preferences, defect)

52 Branch
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: salvi.loris, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20180123215146 Steps to reproduce: I tried to change thunderbird max cache's value via GUI (Preferences > Advanced > Disk Space > Max cache space) and via terminal (editing the config file when thunderbird was close. Actual results: When i launch thunderbird he ignore my change about max cache space and set it to 350MB. Expected results: It must use the previously set value and not reset it with its default value. I was forced to add lockPref("browser.cache.disk.capacity", <my_value>); in mozilla.cfg to lock it and to prevent thunderbird any changes. Sorry for my bad english Cheers, Loris
Is prefs.js file read-only? Are you sure the thunderbird process was gone after shutdown when editing with thunderbird "closed"?
Component: Untriaged → Preferences
Flags: needinfo?(salvi.loris)
Summary: Thunderbird loads always the default max cache space value) → Thunderbird loads always the default max cache space value. Works with lockPref("browser.cache.disk.capacity", <my_value>)
(In reply to Wayne Mery (:wsmwk) from comment #1) > Is prefs.js file read-only? > Are you sure the thunderbird process was gone after shutdown when editing > with thunderbird "closed"? prefs.js and user.js has 700 and the owner is the user logged in in that moment, like all files in that folder. Yes, i'm sure thunderbird's process was over.
Flags: needinfo?(salvi.loris)
I can't reproduce this. I set the value to 343MB and it was still set after a restart. TB does not set the value. If anything, this would be an M-C bug.
(In reply to Jorg K (GMT+1) from comment #3) > I can't reproduce this. I set the value to 343MB and it was still set after > a restart. TB does not set the value. If anything, this would be an M-C bug. Using the lockPref trick it works, maybe it is trying to read the default value from another config file? I checked the user.js and there is nothing about browser.cache.disk.capacity. That's very weird...
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.