Bug 390128

Summary: KMM 5.0 is core dumping when entering any new transaction
Product: [Applications] kmymoney Reporter: Mark Blakeney <mark.blakeney>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: crash CC: gdavies, wal
Priority: NOR    
Version: 5.0.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: coredumpctl info

Description Mark Blakeney 2018-02-09 07:03:34 UTC
Created attachment 110476 [details]
coredumpctl info

Since Arch updated with KMM 5.0 today I am getting a core dump every time I edit a new transaction. Happens in my existing files, but also happens if I create a completely new file. I normally run on GNOME on Wayland but also happens in GNOME on Xorg. I installed plasma-desktop (5.12.0-1) on my Arch system just to try there but the same crash occurs.

This is a critical bug for me. Have used KMM heavily for 12 years across 3 different financial entities with many thousands of transactions in each.

Arch version: kmymoney 5.0.0-1
Comment 1 Mark Blakeney 2018-02-09 12:19:02 UTC
I downgraded kmymoney 5.0.0-1 -> 4.8.1.1-1 and libalkimia 7.0-3 -> 5.0.0-1 and was able to use KMM again thankfully. Both those downgrades were necessary for KMM to run but they were the only downgrades required. I have now pinned those packages.
Comment 2 Graham Davies 2018-02-10 10:24:40 UTC
Similar problem here running KMyMoney 5.0.0-2 on Antergos x86_64 using 4.15.2-2-ARCH kernel, Gnome Shell 3.26.2.

When I start to enter new transaction KMM crashes when entering the payee and clicking on an existing payee in the drop down list. But if I type in the full name of an existing payee and press tab, it is accepted and a new entry can be made. Other fields for new entry can then be completed with no problem.

I've tried using the transaction input form and entering the data directly into the transaction list. Same problem with both methods.

I've also switched from Wayland to Xorg, same problem.
Comment 3 Thomas Baumgart 2018-02-16 19:21:31 UTC

*** This bug has been marked as a duplicate of bug 390264 ***