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]:
[Expired for gnome-keyring (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
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]:
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
This version has expired now
** Changed in: gnome-keyring (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/738063
Title:
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
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
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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
https://bugs.launchpad.net/bugs/738063
Title:
gnome-keyring-daemon assertion failures when changing password
remotely
--
desktop-bugs mailing list
$ egrep -v '^#|^$' /etc/pam.d/common-password
passwordrequisite pam_cracklib.so retry=3
minlen=8 difok=3
password[success=1 default=ignore] pam_unix.so obscure use_authtok
try_first_pass sha512
passwordrequisite
10 matches
Mail list logo
