Things have been going swimmingly. I haven't upgraded or changed my system lately. Now, when I try to open some reports on Investments, the program shuts down. This happens with "capital gains" and "performance". I ran a consistency check and got the message "Finished: data is [SIC] consistent." Any help would be appreciated.

We need more information. What version of KMM are you using, and what OS/distribution? What is the output if you run it from command line?

Thanks for the quick reply, Jack.
This is version 5.1.2 from the repository. (not from an appimage)
I am running plain Ubuntu version 21.10 (impish)
Here is the output of the cmd line:
_______________________________
WebConnect: Try to connect to WebConnect server
WebConnect: Connect to server failed
WebConnect: Starting server failed. Try to remove stale socket.
WebConnect: Running in server mode
System icon theme as reported by QT: "Yaru"
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/onlinejoboutboxview.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/qifexporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/konlinetasks_sepa.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_checkprinting.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/csvexporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/checkprinting.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/csvimporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/sqlstorage.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/reconciliationreport.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_forecastview.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/reportsview.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_qif.so" Validity false
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_reportsview.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/budgetview.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_xmlstorage.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/ofximporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/qifimporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kbanking.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/xmlstorage.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_icalendarexporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/gncimporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kcm_csvimporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/icalendarexporter.so" Validity true
Located plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/forecastview.so" Validity true
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/budgetview.so"
Plugins: budgetview loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/checkprinting.so"
Plugins: checkprinting loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/csvexporter.so"
Plugins: csvexporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/csvimporter.so"
Plugins: csvimporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/forecastview.so"
Plugins: forecastview loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/gncimporter.so"
Plugins: gncimporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/icalendarexporter.so"
Plugins: icalendarexporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/kbanking.so"
"Plugins: kbanking loaded, build with (5.6.0stable-0/6.2.10.0stable), run with (5.6.0.0/6.2.10.0)"
3:2021/11/11 17-24-21:(null)(7172):banking_update.c: 610: No AqBanking config folder found at [/home/john-patrick/.aqbanking/settings6/users] (-1)
3:2021/11/11 17-24-21:(null)(7172):banking_update.c: 610: No AqBanking config folder found at [/home/john-patrick/.aqbanking/settings/users] (-1)
3:2021/11/11 17-24-21:(null)(7172):banking_update.c: 411: There is no old settings folder, need initial setup
7:2021-11-11 17:24:21:aqbanking started
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/ofximporter.so"
Plugins: ofximporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/onlinejoboutboxview.so"
Plugins: onlinejoboutboxview loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/qifexporter.so"
Plugins: qifexporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/qifimporter.so"
Plugins: qifimporter loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/reconciliationreport.so"
Plugins: reconciliation report loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/reportsview.so"
Plugins: reportsview loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/sqlstorage.so"
Plugins: sqlstorage loaded
Loading "/usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/xmlstorage.so"
Plugins: xmlstorage loaded
reading file
start parsing file
startDocument
reading securities
endDocument
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
Cost center model created with items 0
Payees model created with items 0
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "42c7d6e7-5379-444e-9285-6073b6922aef-A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "42c7d6e7-5379-444e-9285-6073b6922aef-A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "42c7d6e7-5379-444e-9285-6073b6922aef-A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "42c7d6e7-5379-444e-9285-6073b6922aef-A001266"
3:2021-11-11 17:24:25:aqbanking banking_compat.c: 58: No account id for alias "A001266"
3:2021-11-11 17:24:44:aqbanking banking_compat.c: 58: No account id for alias "42c7d6e7-5379-444e-9285-6073b6922aef-A001266"
3:2021-11-11 17:24:44:aqbanking banking_compat.c: 58: No account id for alias "A001266"
Floating point exception (core dumped)
_______________________________________

At this point, I'm grabbing at straws, but that last line "Floating point exception" seems key. I'm not familiar with the Yaru theme, but just as a guess, can you try changing themes to see if it helps. My next guess is to ask whether there might be something odd with your data (not enough to trigger any consistency check warning) but causing some bad calculation. Can you try other reports, such as the Information ones, to see if it's any report that triggers the crash, or just some.
Also, you might try running KMM under gdb to see if the backtrace when it crashes provides any useful information. You might also run gdb against the core dump file for the same info.

I appreciate your straw grasping.
1) Changed themes and the problem remains.
2) I am new to Linux and had not heard of gdb before. But, it was not that hard to get up to speed to use it to run KMM. Interpreting the results would take more effort but might not be needed; (see 3 below)
3) I think your straw about a data flaw might be a good one. Also, that is hinted at by the "floating point exception" error. So, first not all reports yield this problem. The main one is the Capital Gains. I have a gains report that is filtered to only two stocks. I brought that one up and added all the stocks in one account (I wish there was a "check all" box for the investments in one account). Then applied it and it worked. I started again with a second account and it failed. So, tomorrow I will do half of the stocks in that account, then 1/4, etc until I whittle it down. If I find a problem, I will report it to you or the powers that be as maybe it is something, like you say, should be caught in the consistency check but is not. Night and thanks again.
A

"At this point, I'm grabbing at straws, but that last line "Floating point exception" seems key. I'm not familiar with the Yaru theme, but just as a guess, can you try changing themes to see if it helps. My next guess is to ask whether there might be something odd with your data (not enough to trigger any consistency check warning) but causing some bad calculation. Can you try other reports, such as the Information ones, to see if it's any report that triggers the crash, or just some.
Also, you might try running KMM under gdb to see if the backtrace when it crashes provides any useful information. You might also run gdb against the core dump file for the same info."

As we would say in Ireland "Done and Dusted".
There were two stocks that had different problems. The first had no "add" entry on the date when the shares were transferred from another broker, but it did have a recent sell entry along with a few years of dividend entries. When I added the shares, that account's capital gains worked. The second stock had a small negative share balance in an account that I had closed. This balance of -0.01 shares was due to the fact that I could not find a way to enter share price or # of shares in amounts of less than 2 decimal places. So, I made it a positive 0.09 shares and then the capital gains worked.
Thank you so much, Jack, for your help. The whole community benefits from the efforts of you and the other contributors. A
P.S. If you need any other information from me, please ask.

I think you did discover something about the program. Holding zero shares is not by itself invalid data, but apparently can lead to a "divide by zero" error. (I don't know for sure without some testing, but it seems likely here.) That would obviously not be caught by a consistency check, but probably should be caught by the report logic before actually making the required calculations. Either that, or trap such an error and issue a warning, instead of crashing. I'll experiment a bit, and probably submit a bug. If you can produce a minimal data file that triggers the error, that would make it easier.

When you say "less than two decimals" did you mean a number requiring more than two decimal places? (that is a number less than .01?) That should be possible, but you need to check the price precision setting for the specific security. I believe two places is the default, but I have all of mine set to 4 places. I'm not at my desktop now, so I can't check the exact screen where you set this, but can do so later, if you can't find it.

I will work on getting you a minimal data set. (I will then be a KMM minor contributor!! )

I can get more than 2 decimal places?! yay! I'll find it.
A

Congrats for figuring out the root cause of this crash. To both of you: would you mind to open an entry on our bug tracker so that we a) don't forget to fix it and b) you have a chance to attach your demo file to reproduce the problem? Many thanks in advance.

@atheist: welcome to the choir of KMyMoney contributors

ipwizard wrote:Congrats for figuring out the root cause of this crash. To both of you: would you mind to open an entry on our bug tracker so that we a) don't forget to fix it and b) you have a chance to attach your demo file to reproduce the problem? Many thanks in advance.

==> Ok, it took me a while to get a stripped down file that crashes or does not based on a small change. I will open a bug report posthaste.

@atheist: welcome to the choir of KMyMoney contributors

Do I get a bumper sticker or a mug?
A

I see that the change has been added to the latest appimage. That's fast response! Thanks, TB.