| Summary: | Transaction entry for Scheduled Transactions blocks input into fields | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Dylan Wolters <dylanwolters> |
| Component: | ux-ui | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | p.r.worrall |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Recording of me attempting to interact with Scheduled Transaction entry | ||
|
Description
Dylan Wolters
2026-02-01 12:19:32 UTC
I've tested on my laptop running Fedora and the same behavior is there as well: SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.21.0 Qt Version: 6.10.2 KMyMoney: 5.2.1 (Maybe helpful) Additional Context: I don't recall updating either of my computers since the last time I entered scheduled transactions. They both independently seem to no longer accept input into this form. I did run updates prior to submitting this report, but the behavior continued. I also switched to the Flatpak version (provided by Flathub) and that had the exact same behavior. It seems that across builds and distributions it is not currently possible to enter scheduled transactions. In fiddling around I have gotten the input fields to be editable again. I believe there is still a bug at play here, but not sure if the original categorization is accurate. I have a recorded video and gif of the issue that i will try uploading shortly for reference. **When entering scheduled transactions: I normally type the first few letters of the account, then press enter once it is the top option. I then tab through the remaining fields, inputting as I go. When encountering the bug above I followed this process. **What I did differently to regain access: I used the visual dropdown menu and selected the account with my mouse. The previously inaccessible fields now became editable and remained so. **Conclusions based on this behavior: 1. The fields being inaccessible carried across devices and installations (Flatpak vs. Official Repositories). This, coupled with the fact that I had not recently updated my packages, leads me to think that some setting or configuration stored within the kmy file replicated this bug across devices and installations. I sync my budget files with Dropbox. 2. This is likely not a regression and a separate bug entirely. Created attachment 189132 [details]
Recording of me attempting to interact with Scheduled Transaction entry
When I tried to reproduce this, I noticed that those fields don't become active until you've got a valid account selected in the Account field. In your recording, 'ewfew' isn't a valid account name (hence having a red box around it). |