gnome-keyring-daemon assertion failures when changing password remotely

[Tuomas Heino]

Binary package hint: gnome-keyring

Changing password remotely results in the following assertion failures in auth.log:

Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password changed for test123
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: gp11_module_get_slots: assertion `data->funcs' failed
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_session: assertion `slot' failed
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: create_credential: assertion `GP11_IS_SESSION (session)' failed
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: egg_error_message: assertion `error' failed
Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: couldn't create new login credential: (unknown)
Mar 19 09:49:18 gx1 passwd[17883]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match.
Mar 19 09:49:18 gx1 passwd[17883]: Passphrase file wrapped

Mar 19 09:55:57 gx1 passwd[18305]: pam_unix(passwd:chauthtok): password changed for test124
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: gp11_module_get_slots: assertion `data->funcs' failed
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_session: assertion `slot' failed
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: create_credential: assertion `GP11_IS_SESSION (session)' failed
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: egg_error_message: assertion `error' failed
Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: couldn't create new login credential: (unknown)
Mar 19 09:55:57 gx1 passwd[18305]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match.
Mar 19 09:55:57 gx1 passwd[18305]: Passphrase file wrapped

To reproduce:
sudo adduser --encrypt-home test123
sudo adduser test124

ssh in as both users created above, run passwd and change the password. Have not tested behaviour without ecryptfs-utils installed, but it should be unrelated since both encrypted and unencrypted homedirs behaved the same.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
CheckboxSubmission: bc3a49cd6e76f0d54c8965120b490eef
CheckboxSystem: abf102d6ef41328208f5c1554651535a
Date: Sat Mar 19 09:51:57 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: gnome-keyring

[Tuomas Heino (iheino+ub)]

$ egrep -v '^#|^$' /etc/pam.d/common-password
password requisite pam_cracklib.so retry=3 minlen=8 difok=3
password [success=1 default=ignore] pam_unix.so obscure use_authtok try_first_pass sha512
password requisite pam_deny.so
password required pam_permit.so
password optional pam_gnome_keyring.so
password optional pam_ecryptfs.so

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Tuomas Heino (iheino+ub)]

gp11-module.c has only two instances of g_return_val_if_fail (data->funcs, NULL); of which only one is in gp11_module_get_slots(), at line 843 for 2.92.92.is.2.30.3-0ubuntu1.1.

I think DebuggingProgramCrash does not apply here as such, since g_return_if_fail does not really abort the program, it only returns the specified error code and makes the log entry, as can be seen from the PID staying the same in the logs.

http://mail.gnome.org/archives/gtk-devel-list/2007-October/msg00053.html does mention "--g-fatal-warnings", but applying that to "passwd" sounds nontrivial at best.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Tuomas Heino (iheino+ub)]

As passwd is setuid, setting environment variable of G_DEBUG=fatal_criticals or G_DEBUG=fatal-warnings before running it does not help.

DebuggingProcedures / DebuggingGNOME / DebuggingProgramCrash do not seem to contain information on how to set the necessary environment for setuid programs like passwd (well, to be exact: programs exec'd from passwd).

[dino99 (9d9)]

This version has expired now

[Tuomas Heino (iheino+ub)]

Reproduced on trusty (using just the test124 part of reproduction instructions above):

Aug 22 13:08:23 gx1 sshd[11844]: pam_unix(sshd:session): session opened for user test124 by (uid=0)
Aug 22 13:08:23 gx1 systemd-logind[1275]: New session 4 of user test124.
Aug 22 13:09:22 gx1 passwd[11988]: pam_unix(passwd:chauthtok): password changed for test124
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: Gck: gck_module_new: assertion 'funcs != NULL' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: module_instances: assertion 'module' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 'error' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't find secret store module: (unknown)
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: create_credential: assertion 'GCK_IS_SESSION (session)' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 'error' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't create new login credential: (unknown)
Aug 22 13:09:22 gx1 passwd[11988]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match.
Aug 22 13:09:22 gx1 passwd[11988]: pam_ecryptfs: Passphrase file wrapped
Aug 22 13:09:23 gx1 passwd[11997]: Error attempting to open [/home/test124/.ecryptfs/wrapped-passphrase] for reading
Aug 22 13:09:23 gx1 passwd[11997]: pam_ecryptfs: Error attempting to unwrap passphrase; rc = [-5]

Version: 3.10.1-1ubuntu4.2

[dino99 (9d9)]

Nobody else but you have reported that issue ; you are the only one affected.
So i wonder if you are using that system since the Lucid installation (or even before) and have made lots of dist-upgrading ?

It shoulb be helpfull to know which kind of formatted partition are used.
Are you able to reproduce that issue with a fresh installation ?

As you can see , the bug team have not paid attention to that report because you only are affected, and the report as not been made using ubuntu-bug via apport.

[Launchpad Janitor (janitor)]

[Expired for gnome-keyring (Ubuntu) because there has been no activity for 60 days.]

[Damiön la Bagh (kat-amsterdam)]

Problem still exists in Trusty:

Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: Gck: gck_module_new: assertion 'funcs != NULL' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: module_instances: assertion 'module' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: assertion 'error' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't find secret store module: (unknown)
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: create_credential: assertion 'GCK_IS_SESSION (session)' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: assertion 'error' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't create new login credential: (unknown)
Dec 20 13:17:37 hostname passwd[23986]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match.