gnome-keyring-daemon crashed with signal 7

[Paul Broadhead]

* Impact

The keyring daemon crashes after login on arm installation with ssh keys in use

* Test case

- configure a ssh key on your machine
- try to use to log into another machine from a desktop session

The keyring should prompt for the passphrase. You should be able to store the key in the keyring and use it still after a logout/login. No crash prompt should be displayed

* Regression potential

The fix is in the ssh agent service so if there is an issue it's going to be with ssh key authentication.

---------------------------------

Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

gnome-keyring:
  Installed: 40.0-3ubuntu1
  Candidate: 40.0-3ubuntu1
  Version table:
 *** 40.0-3ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
        100 /var/lib/dpkg/status

Background process crashes unexpectedly a few moments after login.

I'm running the dev release of Jammy on a Raspberry Pi 400 with all updates applied.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-keyring 40.0-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
Uname: Linux 5.15.0-1003-raspi aarch64
ApportVersion: 2.20.11-0ubuntu79
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Mon Mar 14 15:26:41 2022
Disassembly: => 0xffffffff: Cannot access memory at address 0xffffffff
ExecutablePath: /usr/bin/gnome-keyring-daemon
ImageMediaBuild: 20201022
ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
Signal: 7
SourcePackage: gnome-keyring
StacktraceTop:
 ()
 ()
 () at /lib/aarch64-linux-gnu/libgio-2.0.so.0
 g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0
Title: gnome-keyring-daemon crashed with signal 7
UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
separator:

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

The issue should be fixed with https://launchpad.net/ubuntu/+source/gnome-keyring/42.1-1 according to the gitlab ticket, it might be worth SRUing to the LTS if we have a testcase describing how to trigger the issue

[Anthony Sottile (asottile)]

here's my reproduction:

- boot ubuntu desktop on arm64
- open gnome-terminal
- have an ssh key in ~/.ssh/
- `git clone <email address hidden>:asottile/astpretty` # or really any ssh clone

I've set up a PPA with the patch and verified it fixes the problem: https://launchpad.net/~asottile/+archive/ubuntu/gnome-keyring-jammy

[Sebastien Bacher (seb128)]

Thanks, I've uploaded the fix as a stable update now, the bug will be update with testing instructions once it's accepted from the queue

[Robie Basak (racb)]

FTR, the upstream commit is here: https://gitlab.gnome.org/GNOME/gnome-keyring/-/commit/a17707681f35b73a5ecd8ca60a5ff950c790df39

[Robie Basak (racb)]

Hello Paul, or anyone else affected,

Accepted gnome-keyring into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-keyring/40.0-3ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Hironobu Ishii (ishii-hironobu)]

Hello Robie,

hishii@hishii-desktop:~$ dpkg-query -l | grep gnome-keyring
ii gnome-keyring 40.0-3ubuntu3 arm64 GNOME keyring services (daemon and tools)
ii gnome-keyring-pkcs11:arm64 40.0-3ubuntu3 arm64 GNOME keyring module for the PKCS#11 module loading library
ii libpam-gnome-keyring:arm64 40.0-3ubuntu3 arm64 PAM module to unlock the GNOME keyring upon login
hishii@hishii-desktop:~$ uname -a
Linux hishii-desktop 5.15.0-1011-raspi #13-Ubuntu SMP PREEMPT Thu Jun 2 11:44:34 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

In my environment, the problem was solved with -proposed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-keyring - 40.0-3ubuntu3

---------------
gnome-keyring (40.0-3ubuntu3) jammy; urgency=medium

  * debian/patches/git_ssh_arm.patch:
    - cherry pick an upstream change to fix the ssh agent crashing on arm,
      thanks Anthony Sottile for pointing out the fix (lp: #1964795)

 -- Sebastien Bacher <email address hidden> Tue, 21 Jun 2022 09:27:03 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for gnome-keyring has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.