An update broke unlocking my keyring (twice)

Ask Fedora
, , ,
1

Hello. I have done routine update tonight:

  1. gstreamer1-plugins-good 1.22.5-1 - 1.22.5-3
  2. gstreamer1-plugins-good-gtk 1.22.5-1 - 1.22.5-3
  3. gstreamer1-plugins.good.qt 1.22.5-1 - 1.22.5-3
  4. qgnomeplatform-qt5 0.9.2-4 - 0.9.2-5

I have automatic login, so I always have to enter my password to unlock and after this update it says „wrong password”. Whatsworse, rollback doesn’t work. I’ve tried dnf history undo 50 and dnf history rollback 49, here’s the command output:

Error: The following problems occurred while running a transaction:
  Cannot find rpm nevra "gstreamer1-plugins-good-gtk-1.22.5-1.fc38.x86_64".
  Cannot find rpm nevra "gstreamer1-plugins-good-qt-1.22.5-1.fc38.x86_64".
  Cannot find rpm nevra "gstreamer1-plugins-good-1.22.5-1.fc38.x86_64".
  Cannot find rpm nevra "qgnomeplatform-qt5-0.9.2-4.fc38.x86_64".

That’s the second time it’s happening. At the first time what I did was to create a new keyring and enter all my credentials manually. I don’t want to neither repeat this process whenever I update packages, nor to keep my system outdated.

My system is Fedora Workstation 38 with Cinnamon DE.

2

Hello @anedroid ,
Welcome to :fedora: .
Are you using a different than us-eng keyboard layout? The password entry only accepts us-eng keyboard layout. This could be the reason for wrong password.

3

Yes, I use polish keyboard layout, however my password does not use non-ASCII characters.
Edit: switching the layout to US didn’t help.

4

So I do know that at times the rpmfusion free and non-free repos can lag behind Fedora’s update cycle. So this can be causing issue with the actual update. I am not certain why your password entry is failing, do you feel something is changing with Gnome Keyring as a result of the update?

5

I don’t know this topic very well (i.e. how unlocking and authentication works). I can provide journalctl during failed unlocking, but it doesn’t seem to be very helpful:

lis 16 13:48:15 fedora systemd[1407]: Started vte-spawn-39c5cc4b-c3ff-4b02-aee1-a7dd8d7141ca.scope - VTE child process 15453 launched by gnome-terminal-server process 15424.
lis 16 13:48:21 fedora systemd[1407]: Started dbus-:1.2-org.gnome.seahorse.Application@2.service.
lis 16 13:48:29 fedora systemd[1407]: Started dbus-:1.2-org.gnome.keyring.SystemPrompter@7.service.
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: bus acquired: org.gnome.keyring.SystemPrompter
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: registering prompter
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: bus acquired: org.gnome.keyring.PrivatePrompter
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: acquired name: org.gnome.keyring.SystemPrompter
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: creating new GcrPromptDialog prompt
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: automatically selecting secret exchange protocol
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: generating public key
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: beginning the secret exchange: [sx-aes-1]\npublic=nxXi1VhjDUzpch7hKv3mXQ4Quy2pfHn7oxgpDNE1mtDXeenQo/lHhPOzuezS5KV6GXAIU8Nr2copEQQMajv8zKmWvS13Ga5pjy1ILq50s3O7jPubDsVvhFe9l1xcGjVviL0xkxX+vCmrJMqsaUzpV/luNlyuEJGzw5OE1t/v1hHpN2+KZ5HfZtniOihdhyQfqpZgtOB4aLkjNCyh6fhUV6O9KwgESU9ZydLlits+I/LaWXjlAL6LsVatkOuI7Tzl\n
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: acquired name: org.gnome.keyring.PrivatePrompter
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: receiving secret exchange: [sx-aes-1]\npublic=bLZfGEfnwxCaKZkNRsr1otDHJ2DVHtpIQZXaJkRhrWkYpMwn/hYV1EAIH6VHSBqiLEnVTDfelQeyeMXWm+0AoWUT1H1TgS+3EXyHuGAZYe/danFNT4rBbJ7ybRjy8jTfEOl0+OroWWm/aNa7ixabSC/e/j85JLNMXYZmXu+4MGzAiuKTgJQsUjVdsSjeKZdxks0COA01ohizaGW57eW7PWoDp0VQzQwv08EfDXNFKe2gJnK+X62Us77SL1pzIjnT\n
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: deriving shared transport key
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: deriving transport key
lis 16 13:48:30 fedora gcr-prompter[15539]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: completed password prompt for callback :1.180@/org/gnome/keyring/Prompt/p13
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: encrypting data
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=nxXi1VhjDUzpch7hKv3mXQ4Quy2pfHn7oxgpDNE1mtDXeenQo/lHhPOzuezS5KV6GXAIU8Nr2copEQQMajv8zKmWvS13Ga5pjy1ILq50s3O7jPubDsVvhFe9l1xcGjVviL0xkxX+vCmrJMqsaUzpV/luNlyuEJGzw5OE1t/v1hHpN2+KZ5HfZtniOihdhyQfqpZgtOB4aLkjNCyh6fhUV6O9KwgESU9ZydLlits+I/LaWXjlAL6LsVatkOuI7Tzl\nsecret=N+hMLLlZCSz0msfRNM7I1A==\niv=jF8O2LYddTiZfHYjUFwOmw==\n
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: receiving secret exchange: [sx-aes-1]\npublic=bLZfGEfnwxCaKZkNRsr1otDHJ2DVHtpIQZXaJkRhrWkYpMwn/hYV1EAIH6VHSBqiLEnVTDfelQeyeMXWm+0AoWUT1H1TgS+3EXyHuGAZYe/danFNT4rBbJ7ybRjy8jTfEOl0+OroWWm/aNa7ixabSC/e/j85JLNMXYZmXu+4MGzAiuKTgJQsUjVdsSjeKZdxks0COA01ohizaGW57eW7PWoDp0VQzQwv08EfDXNFKe2gJnK+X62Us77SL1pzIjnT\n
lis 16 13:48:34 fedora gcr-prompter[15539]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: completed password prompt for callback :1.180@/org/gnome/keyring/Prompt/p13
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=nxXi1VhjDUzpch7hKv3mXQ4Quy2pfHn7oxgpDNE1mtDXeenQo/lHhPOzuezS5KV6GXAIU8Nr2copEQQMajv8zKmWvS13Ga5pjy1ILq50s3O7jPubDsVvhFe9l1xcGjVviL0xkxX+vCmrJMqsaUzpV/luNlyuEJGzw5OE1t/v1hHpN2+KZ5HfZtniOihdhyQfqpZgtOB4aLkjNCyh6fhUV6O9KwgESU9ZydLlits+I/LaWXjlAL6LsVatkOuI7Tzl\n
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: cancelling active prompting operation for /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: closing the prompt
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p13@:1.180, and ignoring reply
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p13@:1.180
lis 16 13:48:35 fedora gcr-prompter[15539]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.180
6

Yeah, me neither. It does seem to fail at password entry. GDM is the password entry tool used by Gnome, perhaps try to egrep that from the journal of the failed login. Also, afterwards, are you left with a system that was (mostly) updated?

7

I always update when I see updates are available – usually every few days.

8

Isn’t GDM a display manager?

9

Yes, but it also handles the login process with Gnome, so it may be part of the chain of failure.

10

I use Cinnamon and my display manager is LightDM. Here’s the log of LightDM:

lis 16 13:35:26 fedora lightdm[11354]: pam_unix(lightdm:session): session opened for user test(uid=1001) by (uid=0)
lis 16 13:35:26 fedora lightdm[11354]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
lis 16 13:41:29 fedora lightdm[13401]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=988) by (uid=0)
lis 16 13:41:43 fedora lightdm[13496]: gkr-pam: unable to locate daemon control file
lis 16 13:41:43 fedora lightdm[13496]: gkr-pam: stashed password to try later in open session
lis 16 13:41:43 fedora lightdm[13496]: pam_unix(lightdm:session): session opened for user test(uid=1001) by (uid=0)
lis 16 13:41:43 fedora lightdm[13496]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
lis 16 13:43:14 fedora lightdm[15098]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=988) by (uid=0)
lis 16 13:43:20 fedora lightdm[15201]: gkr-pam: unable to locate daemon control file
lis 16 13:43:20 fedora lightdm[15201]: gkr-pam: stashed password to try later in open session

It says I was trying to unlock my keyring as another user (test), I have copied it from my main user.

11

This may be an actual issue for the lightdm team at GitHub - canonical/lightdm: Display Manager. I would report it there, at least it looks like there was an error during sign-in but it seems to point to pam which is the actual security portion. They probably would know in the least, the best steps to take next.

12

Hmm, it seems like this issue is present since 2019 and haven’t been fixed since then ;(

13

Well that’s disappointing. Perhaps another DM should be chosen so you can bridge this gap. You don’t have to use Cinnamon, I find Sway to be nice, and you can let it be as simple or as busy as you like. Also being a tiled widowing manager is nice too.

14

I know sway, but I got used to Cinnamon. Can I use Cinnamon with GDM and will it help?

15

I think you can use any DM, but there is likely a bit of a learning curve associated. There is also SDDM which is used by i3 and sway as well as others. You can also just use Gnome in Classic mode which is pretty much Cinnamon. Try it out by selecting it as an option at login.

16

I switched to GDM, re-entered all my passwords once again and now GDM unlocks the keyring automatically, so the only password I need to enter is LUKS password. I hope this will not break soon.

17

Fingers crossed eh? Glad you were able to switch to GDM easily. Hope this solves it for you. Next update will tell, should be soon.

18

Well, I’ve performed full system upgrade from Fedora 38 to 39 using fedora system-upgrade and as for now nothing seem to be broken.

19

Perhaps you should mark the comment you feel is the solution as a solution which will show this topic to others who may be having the same issue. It’s good you solved it.

20

Thank you for your help.