| 2024-08-02 16:02:25 |
Nick Rosbrook |
bug |
|
|
added bug |
| 2024-08-02 16:02:55 |
Nick Rosbrook |
nominated for series |
|
Ubuntu Noble |
|
| 2024-08-02 16:02:55 |
Nick Rosbrook |
bug task added |
|
pam (Ubuntu Noble) |
|
| 2024-08-02 16:03:06 |
Nick Rosbrook |
pam (Ubuntu Noble): importance |
Undecided |
Critical |
|
| 2024-08-02 16:03:09 |
Nick Rosbrook |
pam (Ubuntu): importance |
Undecided |
Critical |
|
| 2024-08-02 16:03:12 |
Nick Rosbrook |
pam (Ubuntu Noble): milestone |
|
ubuntu-24.04.1 |
|
| 2024-08-02 16:03:49 |
Nick Rosbrook |
tags |
amd64 apport-bug noble |
amd64 apport-bug noble rls-nn-incoming |
|
| 2024-08-06 17:29:57 |
daas |
bug |
|
|
added subscriber daas |
| 2024-08-08 08:59:54 |
Tim Andersson |
attachment added |
|
_usr_bin_blueman-tray.1000.crash https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2075968/+attachment/5803753/+files/_usr_bin_blueman-tray.1000.crash |
|
| 2024-08-08 15:27:38 |
Julian Andres Klode |
tags |
amd64 apport-bug noble rls-nn-incoming |
amd64 apport-bug foundations-todo noble |
|
| 2024-08-08 19:13:16 |
Nick Rosbrook |
affects |
pam (Ubuntu) |
cloud-init (Ubuntu) |
|
| 2024-08-08 19:13:43 |
Nick Rosbrook |
summary |
cannot login after upgrade from xubuntu 22.04 to 24.04 |
cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04 |
|
| 2024-08-08 19:15:11 |
Nick Rosbrook |
cloud-init (Ubuntu): importance |
Critical |
High |
|
| 2024-08-08 19:15:13 |
Nick Rosbrook |
cloud-init (Ubuntu Noble): importance |
Critical |
High |
|
| 2024-08-08 19:20:31 |
Nick Rosbrook |
attachment added |
|
cloud-init collect-logs https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2075968/+attachment/5803918/+files/cloud-init.tar.gz |
|
| 2024-08-08 20:01:35 |
Nick Rosbrook |
attachment added |
|
journal on reboot after upgrade https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2075968/+attachment/5803953/+files/reboot-after-upgrade-journal.txt |
|
| 2024-08-08 22:17:12 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2024-08-08 22:25:53 |
Nick Rosbrook |
bug task added |
|
ubuntu-release-upgrader (Ubuntu) |
|
| 2024-08-08 22:26:06 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu Noble): importance |
Undecided |
High |
|
| 2024-08-08 22:26:10 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu): importance |
Undecided |
Medium |
|
| 2024-08-08 22:26:16 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu): importance |
Medium |
High |
|
| 2024-08-08 22:26:19 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu Noble): assignee |
|
Nick Rosbrook (enr0n) |
|
| 2024-08-08 22:26:23 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu Noble): status |
New |
Triaged |
|
| 2024-08-08 22:26:27 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu): status |
New |
Triaged |
|
| 2024-08-08 22:26:29 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu): assignee |
|
Nick Rosbrook (enr0n) |
|
| 2024-08-08 22:26:44 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu Noble): milestone |
|
ubuntu-24.04.1 |
|
| 2024-08-09 15:19:32 |
Nick Rosbrook |
description |
After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty.
Dropping to a rescue shell, I can see this in the logs:
root@xubuntu:~# journalctl -b --grep pam
Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP>
Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0)
Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0)
Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring.
Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root"
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session
Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0)
Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring
Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root
Other notes:
(1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here.
(2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-modules 1.5.3-5ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: XFCE
Date: Fri Aug 2 11:55:51 2024
InstallationDate: Installed on 2024-07-30 (3 days ago)
InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: pam
UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago)
mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 |
[Impact]
Since Jammy, desktop metapackages have gained a Recommends: cloud-init, which means that cloud-init will be installed on upgrades to Noble. On the first boot following the upgrade, cloud-init will run because as far as cloud-init can detect, this is the first boot. However, this is wrong, and we do not want cloud-init to run after the upgrade.
One practical impact of this is that by default, cloud-init creates user `ubuntu` with `lock_passwd: true`. If the upgraded machine already has a user `ubuntu`, they will be locked out.
[Test Plan]
The proposed patch is for ubuntu-release-upgrader to disable cloud-init if it is being installed for the first time during the upgrade. This is done by creating /etc/cloud/cloud-init.disabled.
Test #1:
This test must be done on 22.04 desktop where cloud-init is not installed.
1. Confirm that cloud-init is not installed
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that /etc/cloud/cloud-init.disabled was created by ubuntu-release-upgrader
$ cat /etc/cloud/cloud-init.disabled
4. Reboot, and confirm that cloud-init does not run
$ systemctl status cloud-init.service
It should be skipped because the ConditionPathExists=!/etc/cloud/cloud-init.disabled is not satisfied.
Test #2:
This test must be done on 22.04 server where cloud-init is installed. A LXD container works.
1. Confirm that cloud-init is installed:
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that cloud-init was not disabled by ubuntu-release-upgrader
$ stat /etc/cloud/cloud-init.disabled
[Where problems could occur]
It is important that the correct file is created to correctly disable cloud-init. Regressions would be related to whether or not this file is created in the correct circumstances.
[Original Description]
After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty.
Dropping to a rescue shell, I can see this in the logs:
root@xubuntu:~# journalctl -b --grep pam
Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP>
Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0)
Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0)
Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring.
Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root"
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session
Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0)
Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring
Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root
Other notes:
(1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here.
(2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-modules 1.5.3-5ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: XFCE
Date: Fri Aug 2 11:55:51 2024
InstallationDate: Installed on 2024-07-30 (3 days ago)
InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: pam
UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago)
mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 |
|
| 2024-08-09 15:37:37 |
Nick Rosbrook |
description |
[Impact]
Since Jammy, desktop metapackages have gained a Recommends: cloud-init, which means that cloud-init will be installed on upgrades to Noble. On the first boot following the upgrade, cloud-init will run because as far as cloud-init can detect, this is the first boot. However, this is wrong, and we do not want cloud-init to run after the upgrade.
One practical impact of this is that by default, cloud-init creates user `ubuntu` with `lock_passwd: true`. If the upgraded machine already has a user `ubuntu`, they will be locked out.
[Test Plan]
The proposed patch is for ubuntu-release-upgrader to disable cloud-init if it is being installed for the first time during the upgrade. This is done by creating /etc/cloud/cloud-init.disabled.
Test #1:
This test must be done on 22.04 desktop where cloud-init is not installed.
1. Confirm that cloud-init is not installed
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that /etc/cloud/cloud-init.disabled was created by ubuntu-release-upgrader
$ cat /etc/cloud/cloud-init.disabled
4. Reboot, and confirm that cloud-init does not run
$ systemctl status cloud-init.service
It should be skipped because the ConditionPathExists=!/etc/cloud/cloud-init.disabled is not satisfied.
Test #2:
This test must be done on 22.04 server where cloud-init is installed. A LXD container works.
1. Confirm that cloud-init is installed:
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that cloud-init was not disabled by ubuntu-release-upgrader
$ stat /etc/cloud/cloud-init.disabled
[Where problems could occur]
It is important that the correct file is created to correctly disable cloud-init. Regressions would be related to whether or not this file is created in the correct circumstances.
[Original Description]
After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty.
Dropping to a rescue shell, I can see this in the logs:
root@xubuntu:~# journalctl -b --grep pam
Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP>
Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0)
Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0)
Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring.
Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root"
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session
Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0)
Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring
Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root
Other notes:
(1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here.
(2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-modules 1.5.3-5ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: XFCE
Date: Fri Aug 2 11:55:51 2024
InstallationDate: Installed on 2024-07-30 (3 days ago)
InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: pam
UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago)
mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 |
[Impact]
Since Jammy, desktop metapackages have gained a Recommends: cloud-init, which means that cloud-init will be installed on upgrades to Noble. On the first boot following the upgrade, cloud-init will run because as far as cloud-init can detect, this is the first boot. However, this is wrong, and we do not want cloud-init to run after the upgrade.
One practical impact of this is that by default, cloud-init creates user `ubuntu` with `lock_passwd: true`. If the upgraded machine already has a user `ubuntu`, they will be locked out.
[Test Plan]
The proposed patch is for ubuntu-release-upgrader to disable cloud-init if it is being installed for the first time during the upgrade. This is done by creating /etc/cloud/cloud-init.disabled.
Test #1:
This test must be done on 22.04 desktop where cloud-init is not installed.
1. Confirm that cloud-init is not installed
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that /etc/cloud/cloud-init.disabled was created by ubuntu-release-upgrader
$ cat /etc/cloud/cloud-init.disabled
4. Reboot, and confirm that cloud-init does not run
$ systemctl status cloud-init.target
$ cat /run/cloud-init/ds-identify.log
Test #2:
This test must be done on 22.04 server where cloud-init is installed. A LXD container works.
1. Confirm that cloud-init is installed:
$ apt policy cloud-init
2. Do an upgrade
$ do-release-upgrade -d
3. After the upgrade, confirm that cloud-init was not disabled by ubuntu-release-upgrader
$ stat /etc/cloud/cloud-init.disabled
[Where problems could occur]
It is important that the correct file is created to correctly disable cloud-init. Regressions would be related to whether or not this file is created in the correct circumstances.
[Original Description]
After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty.
Dropping to a rescue shell, I can see this in the logs:
root@xubuntu:~# journalctl -b --grep pam
Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP>
Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0)
Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0)
Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring.
Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu
Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu"
Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root"
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file
Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session
Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0)
Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring
Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root
Other notes:
(1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here.
(2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-modules 1.5.3-5ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: XFCE
Date: Fri Aug 2 11:55:51 2024
InstallationDate: Installed on 2024-07-30 (3 days ago)
InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: pam
UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago)
mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 |
|
| 2024-08-09 15:55:08 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu Noble): status |
Triaged |
In Progress |
|
| 2024-08-09 15:56:29 |
Nick Rosbrook |
ubuntu-release-upgrader (Ubuntu): status |
Triaged |
Invalid |
|
| 2024-08-12 11:07:17 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-08-12 11:07:18 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-08-12 11:07:20 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2024-08-12 11:07:24 |
Łukasz Zemczak |
tags |
amd64 apport-bug foundations-todo noble |
amd64 apport-bug foundations-todo noble verification-needed verification-needed-noble |
|
| 2024-08-12 21:37:40 |
Nick Rosbrook |
tags |
amd64 apport-bug foundations-todo noble verification-needed verification-needed-noble |
amd64 apport-bug foundations-todo noble verification-done verification-done-noble |
|
| 2024-08-22 08:22:15 |
Łukasz Zemczak |
tags |
amd64 apport-bug foundations-todo noble verification-done verification-done-noble |
amd64 apport-bug foundations-todo noble verification-needed verification-needed-noble |
|
| 2024-08-22 13:37:12 |
Nick Rosbrook |
tags |
amd64 apport-bug foundations-todo noble verification-needed verification-needed-noble |
amd64 apport-bug foundations-todo noble verification-done verification-done-noble |
|
| 2024-08-27 10:40:13 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-08-27 10:40:56 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-08-30 22:54:21 |
Chad Smith |
cloud-init (Ubuntu): status |
New |
Invalid |
|
| 2024-08-30 22:54:24 |
Chad Smith |
cloud-init (Ubuntu Noble): status |
New |
Invalid |
|
