Upgrade from Saucy to Trusty removed my user from sudoers

Bug #1310341 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just did a full upgrade from Saucy to Trusty.

After completing the upgrade and rebooting and logging in, I opened a terminal an attempted to add a ppa so I could try out a calendar indicator applet.

However, I just discovered that the upgrade destroyed my sudoers file and my ONLY user account no longer has sudo access.

Because of this, I can't do ANYTHING on my system because I don't have sudoers.

So my upgrade from Saucy to Trusty has, right off the bat, left me with an unusable system I must now repair.

bladernr@klaatu:~$ sudo add-apt-repository ppa:atareao/atareao
[sudo] password for bladernr:
bladernr is not in the sudoers file. This incident will be reported.
bladernr@klaatu:~$ sudo su -
[sudo] password for bladernr:
bladernr is not in the sudoers file. This incident will be reported.
bladernr@klaatu:~$ cat /etc/sudoers
cat: /etc/sudoers: Permission denied
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2012-03-15 (765 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
NonfreeKernelModules: nvidia
Package: sudo 1.8.9p5-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Sudoers: Error: command ['pkexec', '/bin/cat', '/etc/sudoers'] failed with exit code 126: Error executing command as another user: Request dismissed
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-04-20 (0 days ago)
UserGroups: adm lpadmin wireshark
VisudoCheck: Error: command ['pkexec', '/usr/sbin/visudo', '-c'] failed with exit code 126: Error executing command as another user: Request dismissed
_MarkForUpload: True
modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: u'/etc/sudoers']
modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: u'/etc/sudoers.d/README']

Revision history for this message
Jeff Lane  (bladernr) wrote : Dependencies.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jeff Lane  (bladernr) wrote :

I couldn't even submit some information for this bug via apport-collect because it requires SUDO.

WINNING

Revision history for this message
Jeff Lane  (bladernr) wrote :

So after fixing this by hacking sudoers in a live image, I can now do "stuff" via sudo again.

Not sure what the problem was exactly, other than there was no entry in sudoers for my user.

That could have been all along, however. I noticed there's a line in sudoers that says:

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

Is %admin correct? the actual group name is adm, not admin.

And I don't know if my user was previously in the sudo group, but that account IS part of adm.

Revision history for this message
Seth Arnold (seth-arnold) wrote :

In 11.10 and earlier, the admin group was used to control "administrative users": https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop#PrecisePangolin.2BAC8-ReleaseNotes.2BAC8-CommonInfrastructure.Common_Infrastructure -- it has since changed to the sudo group but the configuration has remained to support older configurations.

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.