After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616176 - gnome-keyring-daemon assert failure: gnome-keyring-daemon: gck-rpc-dispatch.c:2278: gck_rpc_layer_uninitialize: Assertion `ds->socket == -1' failed.
gnome-keyring-daemon assert failure: gnome-keyring-daemon: gck-rpc-dispatch.c...
Status: RESOLVED FIXED
Product: libgnome-keyring
Classification: Core
Component: General
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-04-19 13:32 UTC by Sebastien Bacher
Modified: 2019-02-22 11:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2010-04-19 13:32:11 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/564792

"everytime I log in (Lucid, Gnome session) the apport icon appears on the panel and tells me that gnome-keyring has crashed. I do not encounter any missing or broken functionality. For example, using the gnome-keyring for UbuntuOne tokens and for passwords in gwibber works fine. If you need more information, I'd be happy to assist.

  • #1 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 *__GI_abort
    at abort.c line 92
  • #3 *__GI___assert_fail
    at assert.c line 81
  • #4 gck_rpc_layer_uninitialize
    at gck-rpc-dispatch.c line 2278
  • #5 pkcs11_daemon_cleanup
    at gkd-pkcs11.c line 53
  • #6 egg_cleanup_perform
    at egg-cleanup.c line 82

Comment 1 Stef Walter 2010-09-11 23:47:55 UTC
This crash occurs during the shutdown of gnome-keyring-daemon.

Pardon me if this seems like a dumb question, Philipp, but are you shutting down GNOME in a abnormal way? If so I'd like to hear the details, so we can fix gnome-keyring-daemon for your use case.
Comment 2 Sebastien Bacher 2010-09-13 10:47:24 UTC
the submitter replied 

"this bug does not occur anymore for me since approximately the release of lucid. Sorry for not reporting this. However, I'm sure that I always used the normal shutdown mechanism (Item "Shutdown" in indicators or the system menu)."

could be just because the crash report system is off by default in stable though.
Comment 3 Felipe Besoaín Pino 2010-10-28 04:11:15 UTC
since sebastien comment in comment 2, "this bug does not occur anymore" I will close this ticket as Fixed, please feel free to reopen it if this happen again setting the version of the package.

Thanks