[tor-bugs] #17140 [Tor Browser]: When Tor Browser updater runs, prefs don't get updated
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Sep 24 19:01:23 UTC 2015
#17140: When Tor Browser updater runs, prefs don't get updated
---------------------------------+----------------------
Reporter: arthuredelstein | Owner: tbb-team
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Browser | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
---------------------------------+----------------------
Changes (by arthuredelstein):
* cc: mrphs (added)
Comment:
Replying to [comment:2 mcs]:
> I am not sure what is going on. Only one restart should be required. How
did mrphs fix the whitelist problem? Can someone provide a reproducible
test case?
mrphs fixed the whitelist problem by restarting Tor Browser (on OS X). So
far I'm not able to reproduce the problem I described, which makes me
wonder if my diagnosis is incorrect. mrphs, I remember you mentioning that
your auto-update failed in some way. Can you give more details -- what
error did you see and how did you finally get update to work? Did you ever
press "Restart later"?
> While discussing this ticket with me, Kathy pointed out that changes
made to Linux the start up script will not go in effect until that script
is re-run, which does not happen during a "restart after update." I am not
sure how to easily fix that, but it will prevent the
FONTCONFIG_PATH/FONTCONFIG_FILE env variable changes made for #16672 from
taking effect until a full "exit/start again" kind of restart is done.
This is a good point -- if possible I would like to move that FONTCONFIG
stuff out of environment variables and into a new Linux whitelisting
patch, but I haven't figured out if that's possible yet.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17140#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list