On 25/05/2019 13.44, Bob Williams wrote:

On Sat, 25 May 2019 11:59:05 +0200 "Carlos E. R." <> wrote:

...

...

Maybe there is some message on syslog.

2019-05-25T12:37:21.584169+01:00 europa su: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control 2019-05-25T12:37:21.585214+01:00 europa su: gkr-pam: couldn't unlock the login keyring.

I get many of those, so it should not be an issue.

I forgot to mention that the desktop is KDE Frameworks/plasma/whatever

Ah, then try with another desktop. Even better, try text mode login. ctrl-alt-f1. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 25/05/2019 14.48, Bob Williams wrote:

On Sat, 25 May 2019 13:52:01 +0200 "Carlos E. R." wrote:

...

...

I forgot to mention that the desktop is KDE Frameworks/plasma/whatever

Ah, then try with another desktop. Even better, try text mode login. ctrl-alt-f1.

Text mode login doesn't even ask for a password! Login incorrect

:-(

That should mean something, but I don't know what. Google doesn't help, maybe wrong search string. There should be something in journal or syslog :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On Sat, 25 May 2019 07:54:48 -0400 Patrick Shanahan wrote:

* Bob Williams [05-25-19 07:47]:

...

On Sat, 25 May 2019 11:59:05 +0200 "Carlos E. R." wrote:

...

On 25/05/2019 11.02, Bob Williams wrote:

...

This machine was upgraded from Leap 15.0 to 15.1 during the beta testing phase. The upgrade was done by switching all the repos to the 15.1 version, followed by zypper dup.

Verify by doing "zypper lr --details | less -S" that all repos are for 15.1

Verified

...

...

At that time, there were two users on the machine, both of whom continue to be able to login satisfactorily. I have tried to create a third user using the YaST module, and it appears to work, but the new user cannot login. When I enter the password and click Login, the password gets highlighted in blue, and the message 'Login failed' appears.

Maybe there is some message on syslog.

2019-05-25T12:37:21.584169+01:00 europa su: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control 2019-05-25T12:37:21.585214+01:00 europa su: gkr-pam: couldn't unlock the login keyring.

I forgot to mention that the desktop is KDE Frameworks/plasma/whatever

zypper -v rm -u gnome-keyring

Good morning Patrick, Removing gnome-keyring didn't help. :-( Thanks -- Bob

On 25/05/2019 13.44, Bob Williams wrote:

On Sat, 25 May 2019 11:59:05 +0200 "Carlos E. R." wrote:

...

On 25/05/2019 11.02, Bob Williams wrote:

...

This machine was upgraded from Leap 15.0 to 15.1 during the beta testing phase. The upgrade was done by switching all the repos to the 15.1 version, followed by zypper dup. Verify by doing "zypper lr --details | less -S" that all repos are for 15.1

Verified

Try this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE\ Leap\ 15\.1|openSUSE_Leap_15\.1" | less -S It will list all packages that *might* not belong to 15.1. You will then have to consider the action: perhaps missing repo, remove, change repo... Also, run this: rpmconfigcheck The output will be like this, but much longer: Telcontar:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/usr.lib.dovecot.auth.rpmnew /etc/apparmor.d/usr.lib.dovecot.config.rpmnew /etc/apparmor.d/usr.lib.dovecot.dovecot-lda.rpmnew /etc/apparmor.d/usr.sbin.smbd.rpmnew /etc/my.cnf.rpmnew /etc/pam.d/login.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/rsyslog.conf.rpmnew /etc/ssh/ssh_config.rpmnew /etc/ssh/sshd_config.rpmnew Telcontar:~ # You will have to review them. For example, as root, I would do: meld /etc/postfix/main.cf.rpmnew /etc/postfix/main.cf & and then decide what to do. .rpmnew is a new version of the file propossed by the rpm update process, while .rpmsave is the old version (the new was applied). Also, do "aa-logprof" and act on the results. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 25/05/2019 17.07, Bob Williams wrote:

Thank you Carlos, Patrick, Dave and Felix.

The problem was a yubikey that I'd been playing with still being in the USB slot.

Why, what did it do? I'm curious.

Sorry for the noise. Anno Domini? Lack of coffee? Too much sun?

:-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 26/05/2019 11.25, Bob Williams wrote:

On Sat, 25 May 2019 17:15:10 +0200 "Carlos E. R." wrote:

...

On 25/05/2019 17.07, Bob Williams wrote:

...

Thank you Carlos, Patrick, Dave and Felix.

The problem was a yubikey that I'd been playing with still being in the USB slot.

Why, what did it do? I'm curious.

Two factor authorisation. The initial two users had been set up to require the presence of the yubikey to allow login. I hadn't completely disabled this setup when trying to add another user, though I thought I had.

And the yubikey impedes new users being created? I would understand that no yubikey plugged means no login, but it was the reverse that happened. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)