[Bug 987003] Re: In Pangolin, sudoer not registered for a new admin profile

[altermd]

** Description changed:

- I was installing Lubuntu cause an old my old computer doesn' completly accepted by unfinity live-dvd .
- So I installed Lubuntu-desktop-cd first, and after that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo first ?)
- My first administrator was fine accepted as Sudoer .
- So I installed two new users and an another admin.
- I discovered that the new administrator was not registred as sudoer (you are not a sudoer and I will make a report " , was the message, when I tried a "sudo  aptitude" or any synaptic and any command for admninistrator.
+ I recently installed Lubuntu 12.04 cause my old computer wasn't completly accepted by unfinity live-dvd due to its cd limit.
+ So I installed Lubuntu-desktop-cd first quitly fine, with no matter.
+ After that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo first ?)
+ My first administrator was fine accepted as Sudoer.
+ So I installed two new users and an another admin in the Gnome environment .
+ But , when I tried a "sudo  aptitude" with this new "adm" profile, I discovered that the new administrator was not registred as sudoer : the message was "you are not a sudoer and I will make a report " and twice in synaptic or any command for admninistrator.
  
- So ,I came back to verify that in the first admin's deskotp.
- In effect, the new admin was not registred in the "sudoer" group, but it was registred in the "adm" group. 
+ So, I came back to verify these news status in the first admin's deskotp.
+ In effect, the new admin was not registred in the "sudoer" group, but was registred in the "adm" group.
+ 
  First I put on the case for this new one in sudo and adm group.
  
  At the first try, the new admin sudoer registration "by hand" didn't took effect.
  I quitted and shutdown (as if in a simple ms boot-on system ;-) .
-  And after reeboot, the new second admin was accepted as sudoer.
+ And after reeboot, the new second admin was accepted as sudoer.
  So I thought I had to report this little anomaly before we have some newbes in trouble the D day.
- Perhaps wasn't due to succession of my manipulations or not ?.... So you have a part of answer, if it is.
+ Perhaps wasn't due to succession of my manipulations or not ?....
+ So you have a part of answer, if it is.
  
  Good luck and long life for the Pangolin !
  
  Alter.md

** Summary changed:

- In Pangolin, sudoer not registered for a new admin profile
+ In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome enviroment)

** Summary changed:

- In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome enviroment)
+ In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome environment)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/987003

Title:
  In Pangolin, a new administrator profile was not registred in the
  sudoer group (Lubuntu /Gnome environment)

Status in “sudo” package in Ubuntu:
  New

Bug description:
  I recently installed Lubuntu 12.04 cause my old computer wasn't completly accepted by unfinity live-dvd due to its cd limit.
  So I installed Lubuntu-desktop-cd first quitly fine, with no matter.
  After that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo first ?)
  My first administrator was fine accepted as Sudoer.
  So I installed two new users and an another admin in the Gnome environment .
  But , when I tried a "sudo  aptitude" with this new "adm" profile, I discovered that the new administrator was not registred as sudoer : the message was "you are not a sudoer and I will make a report " and twice in synaptic or any command for admninistrator.

  So, I came back to verify these news status in the first admin's deskotp.
  In effect, the new admin was not registred in the "sudoer" group, but was registred in the "adm" group.

  First I put on the case for this new one in sudo and adm group.

  At the first try, the new admin sudoer registration "by hand" didn't took effect.
  I quitted and shutdown (as if in a simple ms boot-on system ;-) .
  And after reeboot, the new second admin was accepted as sudoer.
  So I thought I had to report this little anomaly before we have some newbes in trouble the D day.
  Perhaps wasn't due to succession of my manipulations or not ?....
  So you have a part of answer, if it is.

  Good luck and long life for the Pangolin !

  Alter.md

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/987003/+subscriptions