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 712531 - assertion failed in gkd-secret-unlock.c
assertion failed in gkd-secret-unlock.c
Status: RESOLVED OBSOLETE
Product: gnome-keyring
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-11-17 09:00 UTC by drdarkraven
Modified: 2021-06-18 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description drdarkraven 2013-11-17 09:00:30 UTC 
Several seconds after gnome-keyring-daemon is started by PAM, it crashes with SIGABRT.

The log says: "ERROR:gkd-secret-unlock.c:253:perform_next_unlock: assertion failed: (!self->current)"
Comment 1 Sebastien Bacher 2014-03-26 14:21:36 UTC 
There are similar reports/duplicates on https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1200950

Stacktrace from 3.8.2-0ubuntu3

"#0  0x00007ff7bd709037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
        resultvar = 0
        pid = 1777
        selftid = 1777

+ Trace 233396

  • #1 __GI_abort
    at abort.c line 90
  • #2 _g_log_abort
    at /build/buildd/glib2.0-2.37.3/./glib/gmessages.c line 255
  • #3 g_assertion_message
    at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c line 2075
  • #4 g_assertion_message_expr
    at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c line 2086
  • #5 perform_next_unlock
    at gkd-secret-unlock.c line 252
  • #6 mark_as_complete
    at gkd-secret-unlock.c line 185
  • #7 mark_as_complete
    at gkd-secret-unlock.c line 156
  • #8 perform_next_unlock
    at gkd-secret-unlock.c line 257
  • #9 gkd_secret_unlock_call_prompt
    at gkd-secret-unlock.c line 641
  • #10 prompt_method_prompt
    at gkd-secret-unlock.c line 336
  • #11 gkd_secret_unlock_real_dispatch_message
    at gkd-secret-unlock.c line 385
  • #12 service_dispatch_message
    at gkd-secret-service.c line 1040
  • #13 gkd_secret_service_filter_handler
    at gkd-secret-service.c line 1120
  • #14 dbus_connection_dispatch
    from /tmp/apport_sandbox_qoUVHx/lib/x86_64-linux-gnu/libdbus-1.so.3
  • #15 message_queue_dispatch
    at egg-dbus.c line 64
  • #16 g_main_dispatch
    at /build/buildd/glib2.0-2.37.3/./glib/gmain.c line 3058
  • #17 g_main_context_dispatch
    at /build/buildd/glib2.0-2.37.3/./glib/gmain.c line 3634
  • #18 g_main_context_iterate
    at /build/buildd/glib2.0-2.37.3/./glib/gmain.c line 3705
  • #19 g_main_loop_run
    at /build/buildd/glib2.0-2.37.3/./glib/gmain.c line 3899 






Comment 2


Sebastien Bacher





          2014-03-26 15:05:53 UTC
        



errors.ubuntu.com has a retracing with the assert not optimized

"s = 0x89107f8 "\340/~\bp\344*\267d-secret-unlock.c:252:perform_next_unlock: assertion failed: (!self->current)""






Comment 4


André Klapper





          2021-06-18 10:40:28 UTC
        



GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/

Thank you for your understanding and your help.