When starting keepass, it shows a black window then displays the following crash report attached. You may need to try to open a file first. It was initially crashing on opening the password file, but then I moved the file away and it put up a dialog with a can't-find-file error, and then a file chooser. I chose the file, then it locked up and crashed again. Ever since then, it's crashed again. It's still looking for the original file, though, since moving the file back brought back the right window shape for entering in the password. It crashed before I upgraded to the latest mono version this morning (I run ~amd64) and also after. I _believe_ i upgraded libc this weekend, so I suspect it's either a latent bug or a bug in the double-free checker. Reproducible: Always Steps to Reproduce: 1.run keepass in a terminal 2.dialog appears. don't need to do anything 3.observe crash Actual Results: crash Expected Results: not crash
Created attachment 652734 [details] output from the crash
Created attachment 652736 [details] mono_crash.*.json files A set of mono_crash.*.json files (tar xz)
There are a few occasions where it doesn't crash. It crashes pretty reliably for me, though (> 9/10 times)
Does it crash with 2.45 and 2.44? We need to have all information at hand before ticket assignment. That is why I ask you to * attach the logs and * paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket Please reopen this ticket (Status:UNCONFIRMED) afterwards.
Created attachment 652818 [details] emerge --info dev-lang/mono
Created attachment 652820 [details] emerge --info keepass
Logs were already attached. I had emerge --info in, but not attached. Maybe I accidentally removed it (I had to try several times due to character count limitations) I've attached emerge --info for mono and for keepass.
Re: versions. I really don't think keepass itself is the issue, since this is an issue in glibc.
From the looks of things, I haven't updated glibc since July, and mono only this morning (crashed before and after the update). Keepass hasn't been updated for quite some time, and today was the first time it's crashed on me.
Once I can get into keepass, it works fine.
(In reply to Jonas Stein from comment #4) > We need to have all information at hand before ticket assignment. No, we don't. > Please reopen this ticket (Status:UNCONFIRMED) afterwards. Please stop doing that.
Some update this weekend seems to have fixed it. I've not had a crash since at least Monday. Since it's now working, I'll close this.
