FS#58623 - [keepass] Coredump on start with latest mono release

Attached to Project: Community Packages
Opened by Chris (kitteboss) - Wednesday, 16 May 2018, 20:10 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 October 2021, 21:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Giancarlo Razzolini (grazzolini)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
keepass crashes on start with the newest mono package:
* Assertion at aot-runtime.c:2120, condition `info->generic_tramp_num == MONO_TRAMPOLINE_NUM' not met

Downgrading mono to mono 5.10.1.47-1 solves the issue

Additional info:
* package version(s)
keepass 2.39.1-1
mono 5.12.0.226-1


Steps to reproduce:
Upgrade to latest mono release and try to run keepass
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 14 October 2021, 21:46 GMT
Reason for closing:  Won't fix
Additional comments about closing:  2021-06-10: A task closure has been requested. Reason for request: Most likely not applicable in any form anymore
Comment by Troy Dowling (TroyDowling) - Thursday, 17 May 2018, 03:46 GMT
I started with a full upgrade and confirmed keepass still didn't work. Then, I downgraded keepass to the next most recent cached version:

sudo pacman -U /var/cache/pacman/pkg/keepass-2.39-1-any.pkg.tar.xz

Tested and it worked. Then immediately upgraded back to the most recent version (2.39.1-1) and tested again and it still works. Double checked with another full upgrade and everything is working as expected.
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 17 May 2018, 04:07 GMT
I was able to reproduce your issue only once. Because I had keepass already opened before the mono upgrade, it was still running. When I closed it and immediately tried to open it again, it didn't work. When I simply reinstalled the package, it worked. Also, I was not able to reproduce this on a machine where I rebooted before trying to run keepass. I think this affects only if you had keepass in memory and tried to re-open it using new mono. If someone else reports this issue, I'll see about a rebuild and bump. But for now, I don't think its necessary.
Comment by Andreas Radke (AndyRTR) - Thursday, 17 May 2018, 04:58 GMT
I can confirm this issue. A local rebuild of keepass pkg fixed it for me.
Comment by nackd (Prieto) - Thursday, 17 May 2018, 09:24 GMT
I also faced this. I don't think I had keepass open when I upgraded, but I'm not 100% sure. A simple reinstall of the official keepass package fixed it.
Comment by Andreas Radke (AndyRTR) - Thursday, 17 May 2018, 09:58 GMT
It seems to be ralated to the post_install stuff keepass is doing here. Probably this one here:

"mono --aot -O=all usr/share/keepass/KeePass.exe &> /dev/null"
Comment by ashka (ashka) - Thursday, 17 May 2018, 10:48 GMT
Reinstalling keepass (pacman -S keepass) fixes this for me using 2.39.1-1.
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 17 May 2018, 11:03 GMT
Indeed, it seems related with the post_install command. The thing is, this seems to happen only if you have keepass running when doing the upgrade. It doesn't happen if you don't. Nevertheless, I think this is a bug with mono itself, not with keepass. Also, this keepass version was built with the previous mono, so this could be related. I'm bumping the version on the repos with a build done with the current mono version.
Comment by jakob345 (jakob345) - Friday, 24 August 2018, 13:13 GMT
The same bug seems to take affect when upgrading to the new mono version 5.14.0.177-1 while keepass is running. Re-installing keepass fixed it as well.
Comment by Jeff Carpenter (jdc) - Tuesday, 11 September 2018, 23:21 GMT
Bug report on the mono tracker: https://github.com/mono/mono/issues/10191

Loading...