Popularity Contest should be uninstallable

Bug #298617 reported by jan
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
popularity-contest (Ubuntu)
Fix Released
Wishlist
Unassigned
ubuntu-meta (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: popularity-contest

Popularity Contest is (at least in hardy) enabled by default.
It now has a dependency with ubuntu-standard, and no menu item in "services".
This means that switching it off cannot be done via the GNOME UI.
There are several reasons why a user or administrator would like to switch it off.

I see no reason for the dependency with ubuntu-standard, except in order to FORCE users to enable it when using Ubuntu.
Making it recommended for ubuntu-standard, instead of a hard dependency would enable me to uninstall it using synaptic package manager.

Arnaud Soyez (weboide)
Changed in popularity-contest:
status: New → Confirmed
Changed in ubuntu-meta:
status: New → Confirmed
Revision history for this message
Kees Cook (kees) wrote :

While popcon is installed by default, it is not enabled by default:

$ grep PARTICIPATE /etc/popularity-contest.conf
PARTICIPATE="no"

Changed in ubuntu-meta:
status: Confirmed → Invalid
Changed in popularity-contest:
status: Confirmed → Incomplete
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

It is interesting how that it came to "yes" on my system.

Most popularity-contest directories have been created on my system on 2008-05-01.
In the default file:
/usr/share/popularity-contest/default.conf
it is set to "no",

As I do not recall setting it that way, I assume it has been installed this way.
I think this has been done all in one Ubuntu release, as there is a sharp increase in the date graph at:
http://popcon.ubuntu.com/
Unfortunately, the date scale is unreadable there.
Apparently there are a lot of systems where it came to "yes" on that date.

Again: the issue is that the setting is apparently yes for quite a few people, and that it cannot be configured in the GUI.

Changed in popularity-contest:
status: Incomplete → New
Revision history for this message
Kees Cook (kees) wrote :

Unless we can track down the cause of this, we'll need to close this bug report.

Changed in popularity-contest (Ubuntu):
status: New → Incomplete
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Cause is in the upgrader of the release where the jump is in the graph.
Only somebody with access to the raw data can find the exact date, and thus the Ubuntu upgrade that has caused it.
Who has access to this data, and thus can help debug ?

Kees Cook (kees)
Changed in popularity-contest (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Incomplete
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm at http://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers. We also appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please be careful when reporting bugs in future when selecting the 'Security Problem' option. Thank you again.

Changed in popularity-contest (Ubuntu):
status: Incomplete → Invalid
security vulnerability: yes → no
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

I agree that it is may not be security (even though it may inadvertently report information that the system administrator does not wish to reveal). Even though, not being security bug, does not render the bug itself invalid.

Changed in popularity-contest (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

To do this would be a simple change in debian/control to drop it down to Recommends in ubuntu-standard. Perhaps there is a reason for it being the way it is, hence the explanation above, i.e. please open an idea on Ubuntu Brainstorm. If enough people get behind this idea it can be implemented. It is preferred to do it this way since it is a change to the default options of an installed system.
I have marked this Wishlist, Confirmed for now, but again, please see Brainstorm or alternatively one of the Ubuntu IRC channels, perhaps someone higher up in the chain of command can give you a better explanation or push this through.
Thank you and good luck :)

Changed in popularity-contest (Ubuntu):
importance: Undecided → Wishlist
status: Confirmed → Triaged
Revision history for this message
Christian Weiske (cweiske) wrote :

Please make the application uninstallable. For me it feels fishy like pre-installed bloatware on windows computers.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I don't see a reason not to demote the dependency as a recommends instead.

Changed in ubuntu-meta (Ubuntu):
importance: Undecided → Low
status: Invalid → Triaged
tags: added: bitesize
Mathew Hodson (mhodson)
tags: added: packaging
Lenin (gagarin)
Changed in popularity-contest (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
J. Snow (jon.snow) wrote :

@Lenin I'm not sure why you changed the status to "Fix Released". As far as I can see the ubuntu-standard still depends on popularity-contest on Ubuntu 19.10. The same applies for the development branch of Ubuntu 20.04: https://launchpad.net/ubuntu/focal/arm64/ubuntu-standard/1.443

Could you please change the status back to Triaged to indicate that this bug is unfixed?

Revision history for this message
wontfix (wontfix) wrote :
Changed in ubuntu-meta (Ubuntu):
status: Triaged → Invalid
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.