From: Aurora via Bug reports for GNU Guix <bug-guix@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 55136@debbugs.gnu.org
Subject: bug#55136: keepassxc segfaults when merging databases
Date: Thu, 28 Apr 2022 12:38:06 -0400 [thread overview]
Message-ID: <87mtg54101.fsf@disp3269> (raw)
In-Reply-To: <20220426172546.15675818@riseup.net>
raingloom <raingloom@riseup.net> writes:
> Sorry, can't really send the database files, obviously.
>
> Here is the error message instead.
>
> ```
> failed to register FdoSecrets::Item(0x5596b3d47a20) at
> "/org/freedesktop/secrets/collection/passes/c417f89606a5463fa0746d0a5f5625ba"
> "Failed to register item on DBus at path
> '/org/freedesktop/secrets/collection/passes/c417f89606a5463fa0746d0a5f5625ba'"
> QObject::connect(Group, Unknown): invalid nullptr parameter
> QObject::connect(FdoSecrets::Item, FdoSecrets::Collection): invalid
> nullptr parameter QObject::connect(FdoSecrets::Item,
> FdoSecrets::Collection): invalid nullptr parameter [1] 1425
> segmentation fault keepassxc
> ```
It might be advisable to try a synthetic test using two new databases
with some dummy entries in them, to see if it's a general problem with
database merging or if there's something specifically about the
databases you're trying to merge that's not being accepted.
next prev parent reply other threads:[~2022-04-28 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 15:25 bug#55136: keepassxc segfaults when merging databases raingloom
2022-04-28 16:38 ` Aurora via Bug reports for GNU Guix [this message]
2022-06-08 21:20 ` Maxim Cournoyer
2022-06-09 2:29 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-06-09 18:52 ` Maxim Cournoyer
2022-06-10 3:42 ` Aurora via Bug reports for GNU Guix
2022-06-10 13:11 ` raingloom
2023-10-04 3:14 ` Maxim Cournoyer
2023-10-08 14:27 ` Csepp
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtg54101.fsf@disp3269 \
--to=bug-guix@gnu.org \
--cc=55136@debbugs.gnu.org \
--cc=raingloom@riseup.net \
--cc=rind38@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).