When I go to the 'Accounts' button on the left, instead of just a group of Assets and a group of Liabilities, there are four groups. Two Asset groups and two Liability groups. When I open any of these, exactly the same accounts are appearing twice, within the groups. If I am in a ledger view, the dropdown box up the top left hand corner lists the same, Asset accounts twice and Liability accounts twice ??

So, later I exited from KMM and then went into it again, and this particular problem disappeared ?? The only functions done today out of the ordinary is an export to QIF file. So, I assume the QIF export is altering the view properties somehow ??

Before we start consulting our crystal balls: can you please provide some information about the KMyMoney version you are using? Also, it would be cool to know, if you are able to duplicate the problem by repeating the QIF-export operation or not. Thanks in advance.

ipwizard wrote:Before we start consulting our crystal balls: can you please provide some information about the KMyMoney version you are using?

Aren't crystal balls an external representation of what is inside though ? Anyhoo, KMM version is 5.0.8

As the KDE forums no longer allow attachments, I have sent you (mail) a screendump of the problem.

ipwizard wrote:Also, it would be cool to know, if you are able to duplicate the problem by repeating the QIF-export operation or not. Thanks in advance.

Yes I was able to produce it again. Did the export and the accounts view was okay. Then edited one transaction, went back and checked and it now shows the accounts appearing twice. The same with the dropdown box, it shows 4 categories instead of just two (Assets/Liabilities) and the accounts viewed within the categories are duplicated. Then I exited KMM, went in again and the problem disappeared, just like a puff of smoke.

I was able to reproduce the problem with 5.0.8 but not with 5.1.1 nor master. We must have fixed it in the meantime. Case closed.

@ipwizard - Thank you very much. I have also tested with version Version 5.1.1-6bd4987 , and the problem does not exhibit. As you say, case closed.