Closed Bug 1280512 Opened 9 years ago Closed 9 years ago

data choices tab in preferences is empty.

Categories

(Firefox :: Settings UI, defect)

49 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1284010

People

(Reporter: ht990332, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160530175444 Steps to reproduce: As of may 12, 2016, the data choices tab in preferences is empty. it only has the enable crash reporter option in my local build. The only patch I have is the system harfbuzz/graphite one and I doubt that is related. this is my mozconfig: . $topsrcdir/browser/config/mozconfig ac_add_options --prefix=/usr ac_add_options --enable-release ac_add_options --enable-gold ac_add_options --enable-pie ac_add_options --enable-official-branding ac_add_options --enable-default-toolkit=cairo-gtk3 ac_add_options --disable-tree-freetype #ac_add_options --with-system-nspr #ac_add_options --with-system-nss ac_add_options --with-system-jpeg ac_add_options --with-system-zlib ac_add_options --with-system-bz2 ac_add_options --with-system-png ac_add_options --with-system-libevent ac_add_options --with-system-libvpx ac_add_options --with-system-icu ac_add_options --enable-system-hunspell ac_add_options --enable-system-sqlite ac_add_options --enable-system-ffi ac_add_options --enable-system-cairo ac_add_options --enable-system-pixman ac_add_options --enable-ffmpeg ac_add_options --with-system-harfbuzz ac_add_options --with-system-graphite2 ac_add_options --enable-startup-notification ac_add_options --enable-pulseaudio ac_add_options --enable-eme ac_add_options --disable-gconf ac_add_options --disable-updater ac_add_options --disable-tests ac_add_options --disable-dbus --disable-necko-wifi ac_add_options --disable-startupcache
by the way, if I disable crash reporter, the tab is still there but empty. perhaps the tab should not appear if empty. As per irc channel, this is also an issue in Arch Linux firefox package. I think this (or another check-in that day) broke it https://github.com/mozilla/gecko-dev/commit/037e519e6854d4a15525001559acc4cf15931516
I have Fedora 23 and Firefox 47.0 and I am having the same issue. Also there is a old bug for it: https://bugzilla.mozilla.org/show_bug.cgi?id=831369
Closing per duplicate of 831369.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Not a duplicate. bug 831869 was fixed in 2013. This bug happened this year.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
(In reply to Hussam Al-Tayeb from comment #4) > Not a duplicate. bug 831869 was fixed in 2013. > This bug happened this year. To be clear, this was working before May 12, 2016 so the other bug is due to a different issue.
Hi Hussam, Can you provide precise steps on how to access the data choices tab? A screenshot of the issue will also help as well. I will test with the information you provide on the newest version of Nightly. Thanks!
Flags: needinfo?(me)
Component: Untriaged → Preferences
FYI:In case this helps, I just go: Menu button -> Preferences -> Advanced -> Data Choices Not even CPU is used to display the content of the tab. It just does nothing.
Unable to reproduce with the following specs: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Will check on Linux-specific OS when I can.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Screenshots: http://imgur.com/a/VyZTk If I click on "change" in the first screenshot, I am taken to the data choices preferences tab which doesn't contain health reporting options. Maybe the "check" whether to show them is broken now? That may be a good point to start investigating. Where is the check done? Perhaps this? https://github.com/mozilla/gecko-dev/blob/233f30f2377f3df0f3388721901681f432b813fb/browser/components/preferences/in-content/advanced.xul#L199
Hello Hussam, I tried duplicating this issue on Version 50.0a1 Build ID 20160621030208 User Agent Mozilla/5.0 (X11; Linux i686; rv:50.0) Gecko/20100101 Firefox/50.0 I couldn't reproduce the issue. I do see all three options:Enable Nightly Health Report, Share additional data (i.e., Telemetry)and Enable Crash Reporter. I duplicated steps mentioned in comment#9 too but unable to see the issue.
(In reply to Kanchan Kumari QA from comment #10) > Hello Hussam, I tried duplicating this issue on > > Version 50.0a1 > Build ID 20160621030208 > User Agent Mozilla/5.0 (X11; Linux i686; rv:50.0) Gecko/20100101 > Firefox/50.0 > > I couldn't reproduce the issue. I do see all three options:Enable Nightly > Health Report, Share additional data (i.e., Telemetry)and Enable Crash > Reporter. > I duplicated steps mentioned in comment#9 too but unable to see the issue. This is because you are running an official nightly build. Only unofficial/distribution builds are affected. That means firefox compiled on Fedora, Arch Linux, etc... I just finished a build with no patches at all and the following mozconfig http://pastebin.com/raw/j3QQ9Tkc and the issue appears there.
(In reply to Hussam Al-Tayeb from comment #11) > This is because you are running an official nightly build. Only > unofficial/distribution builds are affected. That means firefox compiled on > Fedora, Arch Linux, etc... Hi, Hussam, since this is not an official build, this should be addressed by the maintainer of the build you are using. I'm going to close this as incomplete, and you'll need to pursue this with the Arc Linux distro folks.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → INCOMPLETE
I am not using a distribution package (I have been compiling my own firefox builds since firebird days). There is no maintainer for the builds I use and there are no patches. I compile from scratch using this mozconfig. http://pastebin.com/raw/j3QQ9Tkc I even specified the regression window.
Flags: needinfo?(me)
Emma, I compile my own builds so firefox uses gtk+ 3.20 themeing instead pre gtk+ 3.20 themeing. Official builds link against an older version of gtk+ and so don't look well under gtk+ 3.20. Please consider reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: INCOMPLETE → ---
(In reply to Hussam Al-Tayeb from comment #14) > Emma, I compile my own builds so firefox uses gtk+ 3.20 themeing instead pre > gtk+ 3.20 themeing. > Official builds link against an older version of gtk+ and so don't look well > under gtk+ 3.20. This sounds like a separate issue than what you originally reported, and should be in a separate ticket. Again, since what you described was happening in your own build or a third-party build, I'm closing the ticket. It may be useful for you to connect with the #introduction or #developers channel on irc.mozilla.org.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → INCOMPLETE
(In reply to Emma Humphries ☕️ [:emceeaich] (UTC-8) NEEDINFO? me from comment #15) > (In reply to Hussam Al-Tayeb from comment #14) > > Emma, I compile my own builds so firefox uses gtk+ 3.20 themeing instead pre > > gtk+ 3.20 themeing. > > Official builds link against an older version of gtk+ and so don't look well > > under gtk+ 3.20. > > This sounds like a separate issue than what you originally reported, and > should be in a separate ticket. > I wasn't discussing the other issue (it is already reported and a Red Hat developer is actively working on it and submitting patches to mozilla). > Again, since what you described was happening in your own build or a > third-party build, I'm closing the ticket. It may be useful for you to > connect with the #introduction or #developers channel on irc.mozilla.org. I meant that due to the fact that official linux builds don't operate correctly under modern Linux distributions, it is normal for people and distributions to compile their own firefox packages. If you are not going to support the ability to compile firefox from source, why not simply make it firefox closed source? I already reported this on irc.mozilla.org and was asked to file this bug report. In turn, you closed it and suggested I ask on irc.mozilla.org which is basically placing me in a loop. If I ask on irc.mozilla.org again, they will just refer me again to the bug tracker. This makes very little sense. Again, just re-license firefox as closed source if you don't wish to support compiling from source.
It looks like after the checkin I mentioned above, the condition for whether to enable the data tab is broken (this is where the bug lies). As a workaround, export MOZ_TELEMETRY_REPORTING=1 if you are compiling from source thus removing the reliance of the broken check.
Resolution: INCOMPLETE → DUPLICATE
You need to log in before you can comment on or make changes to this bug.