I have a number of dual boot laptops on 20.04. One of the laptops has a strange device name structure. Instead of /dev/sda1 it has structure below. Any idea why this is?
/dev/nvme0n1p7 20230424 11696832 7482884 61% /
/dev/nvme0n1p8 90893056 7919952 78312932 10% /home
/dev/nvme0n1p1 692224 99192 593032 15% /boot/efi
I have that as well on my new laptop. It is a nvme based drive.
My standard laptop is a spin drive type and has the sda convention.
Ahhh, should have googled it–thanks!
Actually, I was trying to understand two problem this laptop.
When you do a cold boot and enter the user,s password, it then goes into terminal modem and displays the /dev/ drive and the clean statement and the goes back to the login page. Entering the password again then works as expected. Also, for some reason, the windows boot partition shows up under Places.
Cold boot. Try to login. Get the first issue.
Change to a tty I.e. ctrl alt 3 … login
journalctl -ae --full
Using the cursor key scroll back and find the first login. Look at the logs and see why there is a failure.
Jun 20 11:46:41 linux lightdm[1756]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 20 11:46:41 linux lightdm[1756]: PAM adding faulty module: pam_kwallet.so
Jun 20 11:46:41 linux lightdm[1756]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 20 11:46:41 linux lightdm[1756]: PAM adding faulty module: pam_kwallet5.so
Jun 20 11:46:41 linux lightdm[1756]: pam_succeed_if(lightdm:auth): requirement “user ingroup nopasswdlogin” not met by user "janice"
Jun 20 11:46:41 linux lightdm[1756]: pam_unix(lightdm:auth): Couldn’t open /etc/securetty: No such file or directory
Jun 20 11:46:43 linux lightdm[1756]: pam_unix(lightdm:auth): Couldn’t open /etc/securetty: No such file or directory
Jun 20 11:46:43 linux lightdm[1756]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=janice
Jun 20 11:46:45 linux lightdm[1764]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 20 11:46:45 linux lightdm[1764]: PAM adding faulty module: pam_kwallet.so
Jun 20 11:46:45 linux lightdm[1764]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 20 11:46:45 linux lightdm[1764]: PAM adding faulty module: pam_kwallet5.so
Jun 20 11:46:45 linux lightdm[1764]: pam_succeed_if(lightdm:auth): requirement “user ingroup nopasswdlogin” not met by user “janice”
Jun 20 11:46:45 linux lightdm[1764]: pam_unix(lightdm:auth): Couldn’t open /etc/securetty: No such file or directory
Jun 20 11:46:46 linux systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 20 11:46:48 linux lightdm[1764]: pam_unix(lightdm:auth): Couldn’t open /etc/securetty: No such file or directory
Jun 20 11:46:48 linux lightdm[1764]: gkr-pam: unable to locate daemon control file
Jun 20 11:46:48 linux lightdm[1764]: gkr-pam: stashed password to try later in open session
Jun 20 11:46:48 linux systemd[1]: Stopping Session c3 of user lightdm.
Jun 20 11:46:48 linux systemd[1]: session-c3.scope: Succeeded.
Jun 20 11:46:48 linux systemd[1]: Stopped Session c3 of user lightdm.
Jun 20 11:46:48 linux lightdm[1764]: pam_unix(lightdm:session): session opened for user janice by (uid=0)
Jun 20 11:46:48 linux systemd-logind[965]: Removed session c3.
Jun 20 11:46:48 linux systemd-logind[965]: New session c4 of user janice.
Jun 20 11:46:48 linux systemd[1]: Started Session c4 of user janice.
Jun 20 11:46:48 linux lightdm[1764]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Jun 20 11:46:48 linux dbus-daemon[1638]: [session uid=1001 pid=1638] Activating via systemd: service name=‘org.gtk.vfs.Daemon’ unit=‘gvfs-daemon.service’ requested by ‘:1.10’ (uid=1001 pid=1872 comm="/usr/libexec/gnome-session-check-accelerated " label=“unconfined”)
This bit is very curious
pam_succeed_if(lightdm:auth): requirement “user ingroup nopasswdlogin” not met by user “janice”
The account “janice” is trying to be validated as an account with no password logon rights … I.e. auto logon bypassing the lightdm password greeter.
I have tried various scenarios; typing in a wrong password and then getting message “wrong password” , same thing with no password entered,same results. It’s only when the correct password is entered does the system loop back to display the tty clean drive and then the login screen.
After a clean install, right after first reboot I see several PAM errors (no such file or dir) as well…
kwallet in a Budgie Desktop ?
Do you have many Desktop environments installed in that system ?
kwallet?
No, not that I am aware of. However, some time ago I might have tried to install the bitwarden client
desktop environments? - only Budgie desktop
Ok bitwarden may depend on kwallet.
To be sure about Desktop Environments :
ls /usr/share/xsessions/
which should only return :
budgie-desktop.desktop