all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Aurora via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 55136@debbugs.gnu.org, raingloom <raingloom@riseup.net>,
	Thiago Jung Bauermann <bauermann@kolabnow.com>
Subject: bug#55136: keepassxc segfaults when merging databases
Date: Thu, 09 Jun 2022 23:42:35 -0400	[thread overview]
Message-ID: <8735gdyyj8.fsf@disp3269> (raw)
In-Reply-To: <87edzxis9m.fsf@gmail.com>


Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> Strange, I use keepassxc regularly for a long time now and I've never
>> seen it crash. Though I don't do complex stuff such as merging
>> databases, just retrieval of users and passwords and creation of new
>> entries.
>
> I also use it everyday, but I simply open an existing (dated) database
> and edit entries to it/use it.  It seems to crash often when creating
> new databases for me.
>
> Maxim

I just tested Guix's Keepassxc v2.7.1 at Guix revision
01596f40a994a2bb39dde5867ca66e9f7e9e67e0 for merging newly created
databases (KDBX4) with and without conflicts in entries.

I experienced no crashes. Unless keepassxc or its dependencies changed
by the time I tested it, I think that something else might be
interacting.

- Aurora




  reply	other threads:[~2022-06-10  3:43 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=8735gdyyj8.fsf@disp3269 \
    --to=bug-guix@gnu.org \
    --cc=55136@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    --cc=maxim.cournoyer@gmail.com \
    --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 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.