El 2012-03-26 a las 10:17 +0700, Ken Heard escribió: (sending back to the list)
> Camaleón wrote: > > > Something similar happened to me in Lenny when using Iceweasel (now still > > with Lenny but on Firefox 11), that some of the privacy settings did not > > stick despite I manually enabled the checkbox. As I finally removed the > > stock Iceweasel (3.0.x) I forgot about it. > > I suppose that if I wait long enough the problem will be resolved by use > of newer versions of Iceweasel. 3.6.26-1 from Lenny-backports is the > one I am using now; it is also the same one used for Squeeze. Wheezy > has 10.0.2-1; that version may some time be backported in Squeeze. > Experimental has 11.0-3, but I am afraid to use it. I could also do > what you do and use the latest version of Firefox. I finally realized this is the best approach and not just in Lenny but for the next Debian system I will have to install (wheezy), I'm planning to remove the stock Mozilla programs (Iceweasel/Icedove) and go for the upstream ones. Why? Because of the Mozilla upgrade policy, it's very difficult for distributions to follow their "bi-monthly?" set of updates :-/ > > What could you try to restore the functionality? > > > > - Manually set the value from "about:config" > > - Test with an empty profile > > As I mentioned in my post there seems to be a viable work-around. In > the meantime I can live with the work-around; I really do not have the > time now to see if there is something in about:config which will ensure > consistency among users. And most sure is that the setting in "about:config" are both identical, but by resetting it to the default it could restore its functionality. > Besides, if about:config settings are global, i.e., not user specific, > then the difference in behaviour among users would surely have to reside > in some user-specific user file, prefs.js perhaps? "about:config" should tweak the settings for the current user, not globally. > >> Does anybody have an explanation for this behaviour? > > > > Mmm... I'm not sure, but it could be due to a corrupted "*.sqlite" > > database file. > > I am not sure I want to go there either for reasons already explained. Yup, I also left as it was (broken) until I installed Firefox where this setting started working again, but I also wondered what could have caused the mess and after searching and digging in the web, I reached the conclusion it could be possibily due to a corruptued FF database file. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120326145157.ga6...@stt008.linux.site
