Ubuntu
sudo package

  1. Bug #194472
  2. Comment #92

Comment 92 for bug 194472

Revision history for this message
Vish (vish) wrote :

@Rick Spencer,
Last time we discussed this bug :
 - The desktop team mentioned that sudo-less desktop will *never* be achieved. And it is highly unlikely that Ubuntu desktop will /ever/ ship without sudo.
 - The team dont want to take responsibility for the change [fearing backlash from the cli-loving community]
 - That they would *not* object to this change. And would not actively work on this bug.
 - *But* are welcome if someone wants to work on it.
 - You did mention trying the change [as a trial phase] early in maverick alpha, so that the change can be assessed by the wider community and then decided before the final release.

What has changed since then? Why trying to close this issue now?
What is the issue if other teams work on it and take responsibility, why is desktop team now deciding that efforts from other teams too are best put elsewhere?

This is not a random controversial idea we just came up with and trying to push on Ubuntu. There is a genuine concern here and we are trying to fix it.

This bug can be fixed either by: [easiest to toughest]
1 - Removing sudo from desktop » desktop team already rejected this utopia «
or
2 - If someone works on a fix, trial phase this change during early Natty [or which ever release] and then decide before final.
or
3 - Announce and make sure that all ubuntu docs, ubuntu help , support in lp.answers , support in forums, blogs everywhere on the planet need to be fixed so that sudo is not referenced in their tutorials.
ex: documentation used for SRU > https://wiki.ubuntu.com/Testing/EnableProposed , [SRU wiki is more likely to be referred by a new user, than other high level docs, let alone problems for hardware issues] all the documentation everywhere need to be checked and changed.
4 - or what ttx mentions in comment#86

Alternatively, How do you suggest the likely fix for this problem be?
We are open to other suggestions too. There is a problem and looking the other way just because we've grown to expect a certain behavior from an app is not a right fix here.