Bug 510298

Summary: Entering a scheduled transaction shifts the view to an earlier date in the ledger
Product: [Applications] kmymoney Reporter: jswami
Component: ux-uiAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: REPORTED ---    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.2.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description jswami 2025-10-06 12:47:30 UTC
SUMMARY

Entering a scheduled transaction on 10/1/25 worked but scrolled the display back to the start of the ledger--1/23/2020.

STEPS TO REPRODUCE
1. Enter a scheduled transaction in the ledger.
2. See what occurs.

OBSERVED RESULT
View scrolled back to the first entry in the ledger.

EXPECTED RESULT
View should have stayed focused on the present transaction.

SOFTWARE/OS VERSIONS
Linux: Fedora Linux 42 running Gnome 48.
# System Details Report
---

## Report details
- **Date generated:**                              2025-10-06 14:41:33

## Hardware Information:
- **Hardware Model:**                              Lenovo ThinkPad X1 Carbon Gen 10
- **Memory:**                                      16.0 GiB
- **Processor:**                                   12th Gen Intel® Core™ i5-1250P × 16
- **Graphics:**                                    Intel® Iris® Xe Graphics (ADL GT2)
- **Disk Capacity:**                               1.0 TB

## Software Information:
- **Firmware Version:**                            N3AET86W (1.51 )
- **OS Name:**                                     Fedora Linux 42 (Workstation Edition)
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               48
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.16.7-200.fc42.x86_64

KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I've seen this happen consistently, several times. I don't know if similar behavior occurs for other types of transactions.