Bug #1622
[iceweasel] toolkit.telemetry.enabled is true and is locked in about:config, cannot be disabled by user
100%
Description
Steps to reproduce:
1. In running Iceweasel, open about:config from the address bar (agree to void warranty if requested :) )
2. Enter toolkit.telemetry.enabled into a search bar on the page.
Expected result: toolkit.telemetry.enabled preference is false, and web browser doesn't send any telemetry by default.
Actual result: toolkit.telemetry.enabled is true. I didn't debug it or monitor network traffic, so it's unknown if this preference affects anything, as other preferences related to telemetry / calling home are mostly disabled.
History
Updated by oaken-source over 6 years ago
telemetry is disabled on the source level, so even if this setting is enabled (which it shouldn't be since we explicitly disable it in vendor.js), it should not affect anything. But I will take another look at it.
Updated by nRoof over 6 years ago
Not sure if that's useful info, but I just tested this under VM with Live CD of Ubuntu, and they have this preference as false (also locked). Seems this is something that's determined at build time, as I've read that it's 'true' on Nightly and 'false' on Release channel.
Updated by oaken-source over 6 years ago
I found the offending setting, and made the change. We accidentally labeled our build as a pre-release build and not a release build, which caused iceweasel to decide to want to collect more data. Hower, upload of said data was still disabled, so no harm was done.
new builds will arrive later today.
Updated by oaken-source over 6 years ago
- % Done changed from 0 to 100
- Assignee set to oaken-source
- Status changed from open to fixed
fixed in iceweasel-1:58.0-2. thanks for reporting.