Try setting the preference toolkit.telemetry.prompted to "true" in about:config

1. type about:config in the URL/Location/Address bar and press the Enter key
2. if you see a warning, accept it (promise to be careful)
3. Filter = toolkit.telemetry.prompted
4. double click the preference in the lower pane to toggle it to true (or right-click the preference in the lower pane and choose "Toggle")
5. preference in lower pane should now be bold, show "user set" and value should be "true"
6. close the about:config tab
7. See --> http://kb.mozillazine.org/Editing_configuration

If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

If you create a new profile with each test run then you can use a file user.js to initialize pref and add a line with the above mentioned pref in it.

Create a default template folder \defaults\profile in the Firefox program folder and place the user.js file in it.

• http://kb.mozillazine.org/user.js_file user.js

user_pref("toolkit.telemetry.prompted", true);

Here's my solution; hope it will be helpful to you:

1. Create a file called 'user.js' with the following:

user_pref("toolkit.telemetry.enabled", false); user_pref("toolkit.telemetry.prompted", 2); user_pref("toolkit.telemetry.rejected", true);

Note: the first line isn't necessary for Firefox 9, seems like Mozilla have changed things around in the new version (I'm using FF9 Beta 3).

2. Open up your prefs.js and make sure there's nothing about "toolkit.telemetry" in that file.

3. Deploy your Firefox profile with the user.js file inside.

That should be it! This is our solution with our public Firefox deployment.

In Firefox 8 the toolkit.telemetry.prompted pref is still a Boolean, so your solution is only for Firefox 9+ versions where it has been changed to an Integer (Number).

• http://mxr.mozilla.org/mozilla-central/source/browser/components/nsBrowserGlue.js

Hi guys! Thanks to all of you for cooperation and willing to help. I've summarized all your advices, so the following 3 steps sort the problem out for FF8 and make my tests to run fine:

1. Create and configure a new FF profile, using these instruction and suggestions . Don't switch your FF to default profile at the end.
2. Then perform the first 6 steps by SafeBrowser (see above) for the new profile. Switch to default profile (in firefox -p).
3. Don't forget to use your new profile when running Selenium Server (-firefoxProfileTemplate command line parameter) or set Selenium to use this profile when starting a browser from Salenece.

@cor-el: thanks for pointing it out; would be great if Mozilla can inform System Admins about changes like these!