| Summary: | Status: frozen | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | jooseeg <jooseegj> |
| Component: | buildsystem | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | jswami |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
jooseeg
2025-09-16 22:02:59 UTC
This is not a bug, but a poorly documented "feature." Also, this is not a recent change - for a long time, it has not been possible to change anything at all about a transaction marked as frozen. Unfortunately, I just confirmed that this is not mentioned in the Handbook (I thought I had added it recently, but it seems not.) It is now on the list for updating, hopefully in time for 5.2.2. Other than directly editing your data file (which is not generally recommended) reverting to your most recent backup is the only way to change this, other than creating a new transaction with all the same details and then deleting the frozen one. Also, it might be possible to get a pop-up warning added that requires an extra confirmation when setting this value. I'm going to leave this open with consideration of changing it to a wishlist for that purpose. I've run into the same issue. Somehow a transaction I entered was marked "Frozen" (though I didn't knowingly mark it), and now I can neither duplicate nor delete it. KMM 5.2.1. Fedora Project flatpak. Fedora 42. Gnome 48. As I said in my previous comment, the best way to fix your data is to create a new transaction with identical data (except for the state) and then delete the frozen transaction. The only other option is to manually edit your data file, which is not recommended. I will leave this bug open until I confirm the Manual has been updated to discuss this issue. (In reply to Jack from comment #3) > As I said in my previous comment, the best way to fix your data is to create > a new transaction with identical data (except for the state) and then delete > the frozen transaction. The only other option is to manually edit your data > file, which is not recommended. > I will leave this bug open until I confirm the Manual has been updated to > discuss this issue. Thank you, Jack. But as others have commented above and at https://discuss.kde.org/t/unfreeze-transaction/36625, when a transaction is frozen KMM won't let us alter or delete it. Thank you very much,
I have already been able to solve it with your instructions
> El 28 oct 2025, a las 16:03, bugzilla_noreply@kde.org escribió:
>
> https://bugs.kde.org/show_bug.cgi?id=509571
>
> --- Comment #4 from jswami@pamho.net ---
> (In reply to Jack from comment #3)
>> As I said in my previous comment, the best way to fix your data is to create
>> a new transaction with identical data (except for the state) and then delete
>> the frozen transaction. The only other option is to manually edit your data
>> file, which is not recommended.
>> I will leave this bug open until I confirm the Manual has been updated to
>> discuss this issue.
>
> Thank you, Jack.
>
> But as others have commented above and at
> https://discuss.kde.org/t/unfreeze-transaction/36625, when a transaction is
> frozen KMM won't let us alter or delete it.
>
> --
> You are receiving this mail because:
> You reported the bug.
|