[SOLVED] elogind help

3rensho · 05-25-2023, 09:43 AM

Hi all,

Have moved recently and after almost two weeks finally got an internet hookup and the Slackware box back up. In my haste to update everything I upgraded all which included eligond from a recent update. Also built 6.3.4 which appeared in my absence. After rebooting system runs fine. I boot always to run level 3 and can login as root but not as my usual user. I think it is probably down to the elogind change. I copied a logind.conf from an old backup to /etc/elogind but still no go. Trying to unpack a ton of moving boxes and get the -current64 box running normally so if someone could please take pity on this old soul and let me know what the probably obvious fix is it would be most appreciated. Thank you in advance.

garpu · 05-25-2023, 10:01 AM

For the sake of testing, can you create a new user and log in correctly?

3rensho · 05-25-2023, 12:49 PM

Yes the New User worked normally. The protonvpn kill switch has locked me out, so using phone

garpu · 05-25-2023, 12:55 PM

Okay...have you tried resetting your normal account's password? (Think it's like sudo passwd and whatever the username is. I'd have to look it up because I haven't done it in awhile.)

marav · 05-25-2023, 01:47 PM

Anything in /var/log/secure?

3rensho · 05-26-2023, 02:57 AM

Quote:

Originally Posted by garpu

Okay...have you tried resetting your normal account's password? (Think it's like sudo passwd and whatever the username is. I'd have to look it up because I haven't done it in awhile.)

Got logged in again as root and then did su - to get to my user account. Tried "passwd" and that prompted me for the original user pw but that wasn't accepted.

3rensho · 05-26-2023, 03:00 AM

Quote:

Originally Posted by marav

Anything in /var/log/secure?

Had a look marav and found the following:

Code:


May 26 09:47:37 sammy su[2046]: Successful su for tom by root
May 26 09:47:37 sammy su[2046]: + /dev/tty1 root:tom
May 26 09:47:37 sammy su[2046]: pam_unix(su:session): session opened for user tom(uid=1000) by root(uid=0)
May 26 09:47:37 sammy su[2046]: The gnome keyring socket is not owned with the same credentials as the user login: /root/.cache/keyring-GHSW51/control
May 26 09:47:37 sammy su[2046]: gkr-pam: couldn't unlock the login keyring.
May 26 09:47:48 sammy polkitd[2281]: Loading rules from directory /etc/polkit-1/rules.d
May 26 09:47:48 sammy polkitd[2281]: Loading rules from directory /usr/share/polkit-1/rules.d
May 26 09:47:48 sammy polkitd[2281]: Finished loading, compiling and executing 9 rules
May 26 09:47:48 sammy polkitd[2281]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 26 09:49:08 sammy su[4359]: pam_unix(su:auth): user [root] has blank password; authenticated without it
May 26 09:49:08 sammy su[4359]: gkr-pam: no password is available for user
May 26 09:49:08 sammy su[4359]: Successful su for root by tom
May 26 09:49:08 sammy su[4359]: + /dev/pts/2 tom:root
May 26 09:49:08 sammy su[4359]: pam_unix(su:session): session opened for user root(uid=0) by root(uid=1000)
May 26 09:49:08 sammy su[4359]: gkr-pam: unable to locate daemon control file
May 26 09:49:08 sammy su[4359]: gkr-pam: gnome-keyring-daemon started properly
May 26 09:49:15 sammy su[4359]: pam_unix(su:session): session closed for user root
May 26 09:49:18 sammy su[4528]: pam_unix(su:auth): user [root] has blank password; authenticated without it
May 26 09:49:18 sammy su[4528]: gkr-pam: no password is available for user
May 26 09:49:18 sammy su[4528]: Successful su for root by tom
May 26 09:49:18 sammy su[4528]: + /dev/pts/2 tom:root
May 26 09:49:18 sammy su[4528]: pam_unix(su:session): session opened for user root(uid=0) by root(uid=1000)
May 26 09:49:18 sammy su[4528]: gkr-pam: unable to locate daemon control file
May 26 09:49:18 sammy su[4528]: gkr-pam: gnome-keyring-daemon started properly
May 26 09:49:39 sammy su[4528]: pam_unix(su:session): session closed for user root
May 26 09:54:34 sammy unix_chkpwd[6694]: check pass; user unknown
May 26 09:54:41 sammy unix_chkpwd[6695]: check pass; user unknown
May 26 09:54:41 sammy unix_chkpwd[6695]: password check failed for user (tom)
May 26 09:54:41 sammy passwd[6693]: pam_unix(passwd:chauthtok): authentication failure; logname=root uid=1000 euid=0 tty= ruser= rhost=  user=tom
May 26 09:57:53 sammy su[6766]: pam_unix(su:auth): user [root] has blank password; authenticated without it
May 26 09:57:53 sammy su[6766]: gkr-pam: no password is available for user
May 26 09:57:53 sammy su[6766]: Successful su for root by tom
May 26 09:57:53 sammy su[6766]: + /dev/pts/3 tom:root
May 26 09:57:53 sammy su[6766]: pam_unix(su:session): session opened for user root(uid=0) by root(uid=1000)
May 26 09:57:53 sammy su[6766]: gkr-pam: unable to locate daemon control file
May 26 09:57:53 sammy su[6766]: gkr-pam: gnome-keyring-daemon started properly

3rensho · 05-26-2023, 06:27 AM

DOOOH, got over my Homer Simpson moment. Problem easily fixed using the solution pointed to by garpu. Many thanks. Brain apparently turned off by all the stress from moving to a different country.

Petri Kaukasoina · 05-26-2023, 07:09 AM

Quote:

Originally Posted by 3rensho

Code:

May 26 09:49:08 sammy su[4359]: pam_unix(su:auth): user [root] has blank password; authenticated without it

As root, try

Code:

grep '^[^:]*::' /etc/shadow

If it prints anything, you still have a problem. (root without password?)

3rensho · 05-26-2023, 09:59 AM

Quote:

Originally Posted by Petri Kaukasoina

As root, try

Code:

grep '^[^:]*::' /etc/shadow

If it prints anything, you still have a problem. (root without password?)

Thanks Petri it didn't print anything.