gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Alex Murray]

After installing recent updates in 24.04, upon logging in the gnome-shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it.

Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-gnome-keyring 46.1-2build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 06:16:46 2024
InstallationDate: Installed on 2021-08-03 (980 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[David White (cppege-david-9ei9ny)]

It seems that the usual password keyring called Login is not automatically created in gnome-keyring. In fact there are no credentials of any kind in there on logging in after a clean install.

If you change your password via the control panel, the login keyring is then created.

However, when you reboot the Login keyring is not automatically unlocked, as it should be. So, any items you have stored in there are not accessible and you are asked for the password when a service needs credentials from it.

[Karol (wasowski02)]

I'm having the same issue after upgrading to the noble beta yesterday:

ProblemType: Bug
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2022-04-23 (720 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Package: gnome-keyring 46.1-2build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
UpgradeStatus: Upgraded to noble on 2024-04-11 (1 days ago)

[Martin Randau (cmmrandau)]

But it can't be affecting all installations. I installed one or two dailies before the beta. The error appeared after an upgrade. Currently fully upgraded. Maybe just re-install... It's annoying to type the password three times at each login. :D
ThinkPad P14s AMD Gen 3

[Karol (wasowski02)]

Yeah, I was just testing something else and did a couple of installs in VirtualBox and the issue didn't come up (agreed that VMs might behave very differently). Could this somehow be vendor related? I'm running a ThinkPad E14 AMD Gen 3 - this could also just be a coincidence and the fact, that ThinkPads are probably pretty popular among the Linux crowd.

[Archil Asanishvili (arch3r-temp)]

I have the same issue. Keyring and Login passwords are identical but keyring `Login` does not get unlocked automatically on startup. I noticed it couple of days ago after some updates for my 22.04 devel

[Daniel Holbert (dholbert)]

This affects me on a Microsoft Surface Pro 7+ which I upgraded in-place from 23.10 to 24.04-beta with `do-release-upgrade -d` yesterday.

[Emil Granberg (emil-j-granberg)]

I'm also experiencing this issue, although my keyring still exists under ~/.local/share/keyrings/login.keyring and after authenticating using the popup after logging in, all my passwords can be seen when starting "seahorse". The only problem I'm experiencing is that the keyring doesn't automatically unlock after logging in.

[Michael Pelley (mpelley)]

Same issue after upgrading from 23.10 on a Lenovo Legion 5 15ARH7H

[Joseph Powell (flashfennec)]

Same issue on an MSI b350m bazooka Mobo with Ryzen 5600 and rtx 3090 (proprietary drivers, v550)

Fresh install of 24.04 beta

I believe this bug is related to render hangs and DE crashes I've been experiencing at login. If the bug is circumvented by changing to a blank password for the keyring, these render errors no longer occur.

[jon richter (yallmende)]

I can confirm the behaviour after a recent upgrade from mantic to noble and has also been reported in https://discourse.ubuntu.com/t/noble-dev-branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt-install-work-but-apt-upgrade-fail/43979

Another oddity is, that I seem to have to type the password twice into the second, non-overlay password prompt, which has me type my password four times for a complete login.

This may also be connected to recent changes about how the ssh-agent is initialised, which may or may not involve problems with the Keyring or the new GCR. (Does anybody know what the abbreviation means? Its readme stays silent about it.)

- https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288

[Nicolás Abel Carbone (nicocarbone)]

I am having the same problem after upgrading from 23.10 on a Thinkpad T14 AMD Gen 2. Another problem I am having is that WiFi is not automatically connected after log-in. I suppose it is related to this bug, is anyone else having this issue?

[Kihoon Kim (hoonlight)]

I am having the same problem on 24.04 beta

[Jeremy Bícha (jbicha)]

Please don't leave comments here to mention only that you are experiencing this issue. It is already known that this bug affects Ubuntu 24.04 LTS.

Nicolás, this bug has nothing to do with Wifi.

[Nicolás Abel Carbone (nicocarbone)]

@jbicha sorry if I added noise. But the WiFi problem only happens with secured WiFi networks, not open ones. It seemed plausible that they are related, as the password for the WiFi network needs to be retrieved somewhere (the keyring, I assumed). But I will report a different bug report then.

[Jeremy Bícha (jbicha)]

Ok, I understand. However, wifi passwords are stored by the netplan.io package instead of in the gnome-keyring.

[Nathan Teodosio (nteodosio)]

This is unlikely to be a problem in Gnome Keyring, as SDDM has no problem unlocking in on log-in. I'm therefore adding here GDM3.

[Jan Visser (starquake)]

I noticed another problem which makes me wonder if it's related to this. When you unlock the keyring yourself it still fails to unlock ssh keys.

If you do:
$ export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh
it starts working again.

Is this related or should I report a separate bug?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Allen (ccwtech)]

Same issue here. I don't understand the status, "Won't fix"?

[Jeremy Bícha (jbicha)]

Allen, gnome-keyring is not the package that needs to be updated for this issue. It's gdm3.

https://launchpad.net/bugs/2060575

[Allen (ccwtech)]

Got it, thanks!

[Jurgen Schellaert (jurgen-schellaert-j)]

I believe that the evolution mail program and google accounts are to blame.

The problem went away for me after I deleted my keyring and switched from evolution to thunderbird.

Trying to (re-)add a mail account to evolution immediately brings the problem is back.

[Sebastien Bacher (seb128)]

> I believe that the evolution mail program and google accounts are to blame.

Those programs are just using the keyring to store credentials. The prompt is only visible if something tries to get a secret.

A fix has been uploaded now
https://launchpad.net/ubuntu/+source/gnome-shell/46.0-0ubuntu5

[Islam (islam)]

Please share the link to the commit code.

Usually how long it takes after a commit is pushed until the new package is available for upgrade in the repo?

[Jan Visser (starquake)]

Can you give me an answer to my question if this is related or if I should file a new bug?

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/comments/20

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-shell - 46.0-0ubuntu5

---------------
gnome-shell (46.0-0ubuntu5) noble; urgency=medium

  [ Daniel van Vugt ]
  * Drop loginDialog-Create-footer-container.patch - it's buggy and still
    under active development (LP: #2060893)

  [ Marco Trevisan (Treviño) ]
  * debian/patches/ubuntu-authd: Hide the right button if there are no
    sessions to choose (LP: #2061153)
  * debian/patches/ubuntu-authd: Do not start an unavailable authentication
    service (LP: #2060575)
  * d/p/ubuntu-authd: Fix selection of multi-factor auth modes (related to
    lp:2060546)

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 17 Apr 2024 07:45:42 +0200

[Jan Visser (starquake)]

Unlocking SSH keys with the passphrase that is saved to gnome-keyring now works too. Thanks!

[stefanott (ubuntu-stefanott)]

Automatically unlocking the keyring works and stored credentials for other applications are available too. Thanks :-)