Ubuntu
sudo package

Bug wrongly marked as Invalid

Asked by Warren Hill

I reported a bug here:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1130643

Which in my opinion has been wrongly marked as invalid. On advice in another question I have marked the bug incomplete.
As such the bug is now not being looked at and so will probably not get fixed.
The bug however is not incomplete there is sufficient information in the bug report to confirm it.

There is the general question here of if someone believes a bug report as been wrongly marked invalid how do they get it reconsidered. Obviously I don't want to just reopen it to have it closed again. If it were to be closed again I would drop the issue but I would still believe it to be the wrong decision.

And there is the second specific issue of is my specific bug report valid or not. And if not why not

--------------------------------------
Steps to reproduce with Ubuntu 12.04, 12.10 or 13.04 open a terminal and enter

--------------------------------
man sudo root
-------------------------------

As you read through you will see

----------------------------------------------------------------------------
ALLOWING OTHER USERS TO RUN SUDO
       By default, only the user who installed the system is permitted to run
       sudo. To add more administrators, i. e. users who can run sudo, you
       have to add these users to the group 'admin' by doing one of the fol‐
       lowing steps:

       * In a shell, do

           sudo adduser username admin

       * Use the graphical "Users & Groups" program in the "System settings"
         menu to add the new user to the admin group.
----------------------------------------------------------------------------

However since 12.04 there is no "admin" group it has been depreciated and has been replaced by the "sudo" group.
See here for source https://help.ubuntu.com/community/RootSudo
So the documentation needs to be corrected (at least in future releases of ubuntu) to say

           sudo adduser username sudo

I have checked and the man page file "/usr/share/man/man8/sudo_root.8.gz" is provided by the package sudo and so the bug should be filled against the "sudo" package.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu sudo Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Warren Hill (warren-hill) said : 		#1

I've checked this in 12.04, 12.10 and 13.04. For versions prior to this the group was "admin" so the man page is correct.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

I'll have a look later too. I don't have Quantal though but I have Precise and Raring

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

andy@fileserver:/etc$ cat ./group | egrep 'sudo|admin'
sudo:x:27:andy
lpadmin:x:107:andy
andy@fileserver:/etc$ groups
andy adm cdrom sudo dip plugdev lpadmin sambashare apt-get
andy@fileserver:/etc$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

This is my output ounder Precise. Man page says:

ALLOWING OTHER USERS TO RUN SUDO
       By default, only the user who installed the system is permitted to run
       sudo. To add more administrators, i. e. users who can run sudo, you
       have to add these users to the group 'admin' by doing one of the folâ
       lowing steps:

       * In a shell, do

           sudo adduser username admin

       * Use the graphical "Users & Groups" program in the "System settings"
         menu to add the new user to the admin group.

But there is no admin group, the only group name with admin in it is lpadmin

Revision history for this message
Warren Hill (warren-hill) said : 		#4

Andrew,

Since you appear to be in agreement with Manfred and myself that the man page is wrong and as such this is a valid bug. I suggest you go to the bug page click "affects me too" and change the status to confirmed. This should get the bug moving again and I can then accept your answer to close the question.

Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#5

Done

Revision history for this message
Warren Hill (warren-hill) said : 		#6

Thanks actionparsnip, that solved my question.

Revision history for this message
Warren Hill (warren-hill) said : 		#7

I have requested a clarification from the owner of the Ubuntu bug squad. Which I will summarise here when I receive it.

For the moment however the bug is showing as new and there are comments from 3 people including Andrew and my self to confirm it.

Revision history for this message
Brian Murray (brian-murray) said : 		#8

In the event that a bug reporter believes that there bug report has been incorrectly marked Invalid the reporter should engage in a discussion with a wider audience regarding the bug report. The ideal location for this would be the ubuntu-bugsquad mailing list as it is monitored by members of the Ubuntu Bug Squad and Ubuntu Bug Control. However, the #ubuntu-bugs IRC channel on freenode is an acceptable place.

I say that this should happen in front of a wider audience as it is possible that not doing so could result in back and forth just between the reporter and the person who originally marked it as Invalid. The person opening the discussion should probably also mention that such has a discussion has been created and point to said discussion.

Revision history for this message
Warren Hill (warren-hill) said : 		#9

For the benefit of others Brian Murray is the owner of

Ubuntu Bug Squad, Ubuntu Bug Control and Ubuntu Bugs amongst other things.

His reply in post #8 is therefore the definitive answer to the first part of my question how to reopen a bug report if you believe it has been wrongly marked "invalid".

Thanks Brian

Thanks Also to Action Parsnip and Manfred Hampl for helping me to confirm this bug which has now been accepted.

I may have a go at submitting a patch for this bug myself.