Bug 454821 - Unexpected application crash when trying to save the changes of a new transaction
Summary: Unexpected application crash when trying to save the changes of a new transac...
Status: RESOLVED DUPLICATE of bug 453857
Alias: None
Product: kmymoney
Classification: Applications
Component: file (show other bugs)
Version: 5.1.2
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-04 04:36 UTC by Ricky
Modified: 2022-06-04 04:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ricky 2022-06-04 04:36:07 UTC
SUMMARY
Unexpected application crash when trying to save the changes of a new transaction. The crash can be reproduced every time.

From the terminal report these lines:
 kmymoney: malloc.c:2617: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
22 -- exe=/usr/bin/kmymoney
zsh: alarm      kmymoney

STEPS TO REPRODUCE
1. Enter a new record
2. Click on save the new record
3. The app stays open for a few seconds and then closes. When reopening it the changes are lost

OBSERVED RESULT
When trying to save changes from the menu and even from the save icon, the app crashes and when you open it again the save record has not occurred.

EXPECTED RESULT
When a new record is made by clicking on the Save icon or from the menu, the added records should be kept.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Qonos 21.2.6
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Comment 1 Jeremy Whiting 2022-06-04 04:52:24 UTC
This is another duplicate of https://bugs.kde.org/show_bug.cgi?id=453857 See that bug for details, but basically it's a regression in gnutls 3.7.5. Either downgrade to gnutls 3.7.4 or ask your distribution to patch gnutls with the patch mentioned on that bug.

*** This bug has been marked as a duplicate of bug 453857 ***
Comment 2 Jeremy Whiting 2022-06-04 04:55:25 UTC
https://lists.gnupg.org/pipermail/gnutls-help/2022-May/004744.html has some details also. Seems they released gnutls 3.7.6 to mitigate this regression in 3.7.5.