[kmymoney] [Bug 507416] Crash under 5.2 when opening existing database

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=507416

Thomas Baumgart <tbaumgart at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|REOPENED                    |NEEDSINFO

--- Comment #7 from Thomas Baumgart <tbaumgart at kde.org> ---
A few clarifications of statements that have been made in this thread. Some
more instructions on how to proceed at the end of this message.

> While I think that is still theoretically possible, I believe that not all fixes and
> enhancements that are specific to the Qt6 code have been backported to the
> Qt5 code, and will likely not be, so it is important to be sure your errors do
> still show up with a Qt6 build.
At this point in time, the code base supports all features on Qt5 and has a few
quirks on Qt6 (due to missing/broken support of some stuff we had in Qt5 e.g.
bug #507049) which renders the above statement as false.

> the categories incorrectly placed into the account field
Category is a synonym for income/expense account. So if category ids show up in
accountId fields that is perfectly fine and happens by design.

> Interestingly, whatever changes occurred in the last couple of weeks,
> or using the default build flags is preventing the crash on startup
It is these two changes
(https://invent.kde.org/office/kmymoney/-/commit/cb50551c and
https://invent.kde.org/office/kmymoney/-/commit/7c5ac5cc) which prevent the
crash and removes the offending split and shows the transaction as unassigned.

> ... but have you run the program under a debugger to get a backtrace?
No need, since we caught the culprit with some debug output and fixed it in
https://invent.kde.org/office/kmymoney/-/commit/7c5ac5cc

> This might simply be Kmymoney having changed some bit of logic tied
> to the structure of account IDs and categories in a way that was not
> historically a problem, and imported accounts violating these assumptions.
If that is the case it did not happen deliberately. Nevertheless, the code to
organize the data in memory has been completely rewritten between 5.1.3 and 5.2
but it could well be that the new code assumes the first character of an
account/category id to be the character A when looking for accounts/categories
which is not true in all of your cases.

Next step: KMyMoney supports a feature to create an anonymized version of your
data which allows the developers to look at the structure without disclosing
private information. Please see
https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.formats.anonymous.html
on how to create one. Since they are XML you can take a look for yourself.
Please send them to me directly, no need for the mailing list mentioned or
attaching it to this ticket.

Please create one version of the anon file using 5.1.3 with the original data
from your backup (i.e. unaltered by 5.2) and one created with the version of
5.2 you built yourself. Make sure that the version created with 5.1.3 still
shows the symptoms when loaded using 5.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.