Root Password does not work except with the SDDM Login Manager - Package i installed and what i idd to get my OS working again:




Im using opensuse tumbleweed
I when to Yast2 > to install NIS
yast told me that the NIS package was not available
So i downloaded a .RPM of it instead ans installed that
It added 3 extra repositorys - one of which is for Devs
My system then had problems boot up after that and also would not shut down properly
because i use the btrfs FS, i decided to copy over ALL the previous days OS's root folders from one of my btrfs snapper snapshot backups - as a sort of 'go back in time' procedure
This worked
However, i have this root password issue

I found some useful sutff via google:

journalctl -b -f

leave it running and try to authenticate, it should print info from polkit about what went wrong.

Authenticate = mean to type in your admin password
Then review the messages in terminal

"Does rebooting help?

Have you manually changed the pam configuration?

I'm not at all sure here. However, my experience suggests that these requests from policy-kit depend on the systemd user agent. Presumably the user agent communicates with the main systemd process.
If an update restarts the main systemd process, that breaks the communication and it might not work properly until reboot. And if the systemd entry is removed from the pam configuration, that also breaks the communication."




Repositorys that i removed that were added by the NIX package

Home:munix9
home:beyerle:IAC
devel:tools:ide



https://forums.opensuse.org/showthre...d-not-accepted

Check the system journal; run this command as root in terminal:
Code:

journalctl -b -f

leave it running and try to authenticate, it should print info from polkit about what went wrong.

Authenticate = mean to type in your admin password
Then review the messages in terminal

"Does rebooting help?

Have you manually changed the pam configuration?

I'm not at all sure here. However, my experience suggests that these requests from policy-kit depend on the systemd user agent. Presumably the user agent communicates with the main systemd process.
If an update restarts the main systemd process, that breaks the communication and it might not work properly until reboot. And if the systemd entry is removed from the pam configuration, that also breaks the communication."




TERMINAL OUTPUT:

Aug 15 09:22:01 IntelPC su[6632]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Aug 15 09:22:01 IntelPC su[6632]: gkr-pam: couldn't unlock the login keyring.
Aug 15 09:22:01 IntelPC unix_chkpwd[6633]: check pass; user unknown
Aug 15 09:22:01 IntelPC unix_chkpwd[6633]: password check failed for user (root)
Aug 15 09:22:01 IntelPC su[6632]: pam_unix(su:auth): authentication failure; logname= uid=1000 euid=1000 tty=/dev/pts/3 ruser=starman rhost= user=root



Do i need to re-install tumbleweed OS again from scratch ?