can't use sudo after a fresh install (karmic)

Bug #387997 reported by Hassan El Jacifi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Invalid
Undecided
Rolf Leggewie

Bug Description

Binary package hint: sudo

I just try karmic-server-amd64 (Alpha-2) and I can't run sudo on it.

ssh testor@192.168.122.80
testor@192.168.122.80's password:
Linux ubuntu 2.6.30-8-server #9-Ubuntu SMP Wed Jun 3 16:37:12 UTC 2009 x86_64

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

To access official Ubuntu documentation, please visit:
http://help.ubuntu.com/

  System information as of Tue Jun 16 18:10:01 CEST 2009

  System load: 0.03 Memory usage: 7% Processes: 68
  Usage of /: 60.1% of 895MB Swap usage: 0% Users logged in: 1

  Graph this data and manage this system at https://landscape.canonical.com/

35 packages can be updated.
0 updates are security updates.

Last login: Tue Jun 16 18:09:18 2009 from 192.168.122.1

testor@ubuntu:~$ sudo date
[sudo] password for testor:
testor is not in the sudoers file. This incident will be reported.

testor@ubuntu:~$ id
uid=1000(testor) gid=1000(testor) groups=1000(testor)

testor@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

testor@ubuntu:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 896M 538M 313M 64% /
tmpfs 245M 0 245M 0% /lib/init/rw
varrun 245M 72K 244M 1% /var/run
varlock 245M 0 245M 0% /var/lock
udev 245M 156K 244M 1% /dev
tmpfs 245M 0 245M 0% /dev/shm
/home/testor/.Private
                      896M 538M 313M 64% /home/testor

Revision history for this message
Hassan El Jacifi (waver) wrote :
Hassan El Jacifi (waver)
Changed in sudo (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathias Gug (mathiaz) wrote :

I'm not able to reproduce this. I've successfully installed karmic alpha2 and the admin group was in the sudoers file.

Could you post the logs of the installation process (/var/log/installer/)?

Changed in sudo (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Hassan El Jacifi (waver) wrote :

As requested

Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Hassan El Jacifi (waver) wrote :
Changed in sudo (Ubuntu):
status: Incomplete → New
Revision history for this message
Hassan El Jacifi (waver) wrote :

You should do some test with crypted home directory. I will test tomorrow without encryption

Revision history for this message
Hassan El Jacifi (waver) wrote :

I reinstall again with the same procedure like I use for my first test and I can reproduce the bug.

Try to test like this:

- Use all entry disk without LVM
- Encrpted home directory
- Select OpenSSH server

Changed in sudo (Ubuntu):
status: New → Confirmed
Revision history for this message
Hassan El Jacifi (waver) wrote :

Without Encryption, sudo work perfectly.

@ Mathias, can you please test with encryption

Let's start doing some other test for ubuntu-ha ;)

Revision history for this message
Rolf Leggewie (r0lf) wrote :

does this ever occur in trusty or later?

Changed in sudo (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: Confirmed → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in sudo (Ubuntu):
status: Incomplete → Invalid
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.