gnome-keyring-daemon crashes; assertion failed; (permission denied?)

[thedoctar]

This error occurs when I first open Skype. Skype loads, but not prompt for the keyring password occurs. After killing skype from the command line and starting it again, everything works and I am prompted for the keyring passw.

(Also reported upstream here: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/64)

From journalctl:

gnome-keyring-daemon[803]: **
            ERROR:daemon/dbus/gkd-secret-unlock.c:243:perform_next_unlock: assertion failed: (!self->current)

From /var/crash:

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 16 12:08:08 2020
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/bin/gnome-keyring-daemon
ExecutableTimestamp: 1583917570
ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'

(full file attached)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-keyring 3.36.0-1ubuntu1
Uname: Linux 5.8.0-050800-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Sun Aug 16 13:47:41 2020
InstallationDate: Installed on 2020-05-11 (96 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[thedoctar (thedoctar)]

Hi sebastian, I deleted the .crash file for security reasons, as you said.

My error report I will send you by email.

[Sebastien Bacher (seb128)]

Thanks, from the error 5faa95fe-e099-11ea-b3b0-fa163e983629

() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
perform_next_unlock (self=self@entry=0x5607907f5d80) at daemon/dbus/gkd-secret-unlock.c:243
mark_as_complete (self=self@entry=0x5607907f5e60, dismissed=dismissed@entry=0) at daemon/dbus/gkd-secret-unlock.c:176
mark_as_complete (dismissed=0, self=0x5607907f5e60) at daemon/dbus/gkd-secret-unlock.c:248