Created attachment 141661 [details] KMymoney file produced by the "steps to reproduce" SUMMARY I've observed this behavior in KMyMoney 5.1.1 (OpenSuSE RPMs) and 5.1.2 (built from source). The short description is that it's no longer possible to enter transactions into investment account ledgers. The "Price" and "Shares" fields no longer allow one to enter data directly, and the category fields (Interest and Fees) no longer accept focus. Also, "Buy Shares" transactions do not generate entries in the corresponding Brokerage account. STEPS TO REPRODUCE Sorry this section is a little long. I'll outline the steps to create a new kmymoney file, and reproduce the problem I'm seeing. File > New - provide Name: Mr. Tester. Click Next - Select US Dollar as currency. Click Next - Leave "I have a checking Account" checked. Name of Account: My Checking Account. Click Next - Select "Base-Simple" as Account Types. Click Next. - Click Finished - Select XML as storage type - save as "my-kmymoney-file.kmy" Institution > New Institution - name: My Financial Institution. Click Ok. Account > New Account - Institution: My Financial Institution. Click Next - Account Name: My Investment Account. Account Type: Investment. Click Next. - Check "Create Brokerage Account". Click Next - Select "Asset" as parent account. Click Next - Click Finish Open the My Investment Account (Brokerage) Leger - Enter a deposit for $100, with category "Job", so the balance is $100. Open the Investments View (left sidebar) - Select Account: My investment account - New Investment - Type of investment: Stock - Trading Symbol: TEST - Full Name: Test Stock - Click Next - Click Finish Open the "My Investment Account" Ledger - Click new - Activity: Buy Shares - Security: Test Stock - Account: My Investment Account (Brokerage) - In the "Shares" field, type "10". - The shares field contains "1.00", and the zero I typed went into the memo field. - Use the calculator field to enter 10 - In the Price per share field, attempt to enter 1.00 - Save the transaction - Observe the triangular warning symbol in the transaction legder ("Transaction is missing a category assignment") - Edit the transaction. Click in the "Fees" field. - Observe the cursor "jump" into the Memo field - Click in the "Interest" field. - Observe the cursor "jump" into the memo field - Click cancel Open the "My Invest Account (Brokerage)" Ledger - Note that the "Buy Shares" action did not produce a corresponding "Buy" entry in the Brokerage account ledger. The brokerage account still has an initial balance of $100. I'll attach the kmymoney file created with the procedure above. OBSERVED RESULT - values cannot be entered directly into the "Shares" or "Price" fields in Investment account transactions - The Fees and Interest fields will not accept focus, when editing an investment account transaction - "Buy Shares" does not produce a corresponding entry in the Brokerage account ledger EXPECTED RESULT - One should be able to type values into the "Shares" and "Price" fields when entering or editing investment account transactions. - The Fees and Interest fields should accept focus, and allow selection of configured categories - a new "Buy shares" transaction should generate a corresponding brokerage account entry SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.3. 5.3.18-59.19-default. KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION I'm able to build from source, and would be happy to test patches.
Are you using xorg or Wayland? Can you try the other?
I'm using xorg. I tried with Wayland and observed the same behavior.
An additional piece of information: if I run kmymoney as "ssh -X localhost kmymoney", then the issues I've reported to not occur -- kmymoney has a different appearance, but transaction data entry for investment accounts behaves normally. So, it looks like I have a workaround.
Thanks for the detailed problem description. I'd love if all of them had that quality. That sounds very strange. By building from source, do you mean the tar-ball 5.1.2 version or the source from the git 5.1 branch? You can try the latter easily by installing the latest stable AppImage version available on https://kmymoney.org/appimage. No need to uninstall your version. Does the problem persist or does it go away? Which theme are you using, because I noticed it is one thing that may change when one uses your 'ssh workaround'? If you start KMyMoney from a console then it prints the theme it uses as one of the first things to the console. (In the meantime, I noticed that you should know about all of cli business)
Hello Thomas, By "building from source", I was referring to the 5.1.2 tarball, which I downloaded from https://download.kde.org/stable/kmymoney/. I've tried the AppImage (KMyMoney-5.1.2-fae974f-x86_64.AppImage). That behaves normally; the problem goes away. I am using the "Oxygen" theme. Both the 5.1.2 AppImage and the 5.1.2 I built from source print the following line to stdout: System icon theme as reported by QT: "oxygen"
Hello Steve, thanks for the feedback. Seems that one of the recent changes may have solved the issue you encounter. Since you build from source, can you try to build from the "5.1" branch of the git sources and check what happens? This would make sure that it is not a side effect that solves the issue by running as AppImage. Thanks in advance.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!