all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: kiasoc5@disroot.org
Cc: 58285@debbugs.gnu.org
Subject: bug#58285: secrets crashes when unlocking database
Date: Mon, 10 Oct 2022 01:21:36 -0400	[thread overview]
Message-ID: <87tu4c1cf3.fsf@gmail.com> (raw)
In-Reply-To: <4ab80905bcad5ceb75fd25af98e186e8@disroot.org> (kiasoc5@disroot.org's message of "Tue, 04 Oct 2022 05:39:21 +0000")

Hi,

kiasoc5@disroot.org writes:

> (.secrets-real:8886): Gtk-WARNING **: 01:35:46.681: GtkText - did not
> receive a focus-out event.
> If you handle this event, you must return
> GDK_EVENT_PROPAGATE so the default handler
> gets the event as well
> Traceback (most recent call last):
>   File
>   "/gnu/store/b07y8a2axslnz97pjdg7lp73xwk1gf8w-python-pygobject-3.40.1/lib/python3.9/site-packages/gi/overrides/__init__.py",
>   line 351, in wrap
>     return func(a, b, *user_data)
>   File
>   "/gnu/store/sadrq8giqh8f5r1x7ycxa2dciv1445f4-secrets-6.5/lib/python3.9/site-packages/gsecrets/sorting.py",
>   line 60, in sort_by_ctime_asc
>     return ele1.ctime.compare(ele2.ctime)
> TypeError: GLib.DateTime.compare() takes exactly 2 arguments (1 given)

I could reproduce that; I first updated to version 7, but I had an
unrelated problem with otp something.  Unfortunately I'm not sure what's
wrong.  Would you have the time to open an issue with upstream?  You'll
need an account with their gitlab here:
https://gitlab.gnome.org/World/secrets.

-- 
Thanks,
Maxim




  reply	other threads:[~2022-10-10  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  5:39 bug#58285: secrets crashes when unlocking database kiasoc5--- via Bug reports for GNU Guix
2022-10-10  5:21 ` Maxim Cournoyer [this message]
2022-10-14  1:44   ` kiasoc5 via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tu4c1cf3.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=58285@debbugs.gnu.org \
    --cc=kiasoc5@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.