SUMMARY Trying to open the Split Transaction editor results in immediate crash, whether in existing or new book or in existing, new, or scheduled transaction. Behavior first appeared sometime after 17 Jan 2026. STEPS TO REPRODUCE 1. Run any recent 5.2.1 AppImage (for example, 5.2.1-cb18307). 2. In an existing transaction, new transaction, or scheduled transaction, try to open the Split Transaction editor (either by clicking on split transaction icon or using ctrl+space key combo). OBSERVED RESULT KMyMoney application immediately terminates. EXPECTED RESULT Split Transaction editor window opens. SOFTWARE/OS VERSIONS Linux Mint 22.3 22.3 (x86_64) ADDITIONAL INFORMATION Crash occurs on Linux Mint 22.3 computer running AppImages back to 5.2.1-429fb80. Crash does not occur on Linux Mint 22.1 computer (with no software updates for past few weeks) nor Windows 10 Version 22H2 computer, each running 5.2.1-cb18307.
I am assuming this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=514619 ? Your non-working version was from 12/7, although you say the crash occurs "back to" that version. You don't specify the most recent version which crashes. Bug 514619 was fixed on 1/16, your working versions are from 1/25 (today,) and so include the fix. My only uncertainty is that bug 514619 was when closing the split editor, and yours is when invoking it. Please reopen if the crash still occurs with a more recent developer or stable appimage. *** This bug has been marked as a duplicate of bug 514619 ***
(In reply to Jack from comment #1) > I am assuming this is a duplicate of > https://bugs.kde.org/show_bug.cgi?id=514619 ? > Your non-working version was from 12/7, although you say the crash occurs > "back to" that version. You don't specify the most recent version which > crashes. > Bug 514619 was fixed on 1/16, your working versions are from 1/25 (today,) > and so include the fix. > > My only uncertainty is that bug 514619 was when closing the split editor, > and yours is when invoking it. Please reopen if the crash still occurs with > a more recent developer or stable appimage. > > *** This bug has been marked as a duplicate of bug 514619 *** This bug is not a duplicate of bug 514619, which crashed when split editor was closed. My crash occurs when trying to invoke the split editor in the latest version (5.2.1-cb18307; most recent stable AppImage, released 23 Jan) running in Linux Mint 22.3. My crash does not occur in latest version running in Linux Mint 22.1 or in Windows 10.
(Please, always specify exact version, since "latest version" can change depending on exactly when you wrote. In this case, we do have the specific versions, so we don't need more info about that.) If I read correctly, the the version for commit cb18307 crashes for Mint 22.3 but not Mint 22.1 (both Appimages) and does not crash for Windows. If this is the case, knowing what changed between those Mint versions might point to where the problem is. Unfortunately, that may be difficult to pin down, but it is certainly possible that there was a change in one of the underlying Qt or KDE libraries which triggers the bug. Can you get a backtrace of the crash? That would be quicker to point to where the crash happens.
I read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, but that link said that it didn't apply to AppImages. If you can point me to a way to generate a backtrace from an AppImage, I'll do my best to provide one. I've been using Linux for only a few months, so I'm still inexperienced with the operating system.
Ah, I didn't think about that. Let me try it myself first just to see how it works, but I would try the same as a regular application: "gdp path/to/appimage/executable". I'm just not sure how much extra output or layers would be added, but hopefully it's just some more lines to be ignored. Also, if you invoke the appimage from command line, is there any useful output to console right before the crash?
Yes, that appears to work (except for using "gdb" and not "gdp".) That debugging page even confuses me, and I've been doing this for a while. As I said, first just try "gdb path.to.appimage" and after KMM crashes, type "bt" (short for backtrace) to the gdb prompt. Hopefully, it will at least have enough information to know which functions and libraries are involved, although it probably won't have adequate debugging information. If that is not enough, the next step would be to follow the DEBUGINFOD section for Ubuntu based distros.
Created attachment 188881 [details] gdb backtrace failed attempt gdb backtrace didn't generate any information when the KMyMoney appimage crashed.
Created attachment 188882 [details] Messages generated when running KMyMoney appimage from a terminal. The last 4 lines were generated when I tried to open the Split Editor.
Sorry about the wall of text with the terminal output; and I'm still learning how to use this commenting portion of the bug reporting system.
Actually, "double free or corruption (out)" is likely the problem - we just need to figure out where in the program it happens. It looks like your first attachement was a backtrace - but did you do that before running the program and causing it to crash? Once you say yes to the debuginfod question, you need to say "run" to gdb to make it actually run the program. After the crash, then you type "bt". All the text in your second attachment is normal KMyMoney console output. However, the last two lines might indeed indicate that gdb can't get the info it needs with an Appimage. Question: what version of KMyMoney does Mint 23.1 package, and does it crash?
(In reply to Jack from comment #10) > Question: what version of KMyMoney does Mint 23.1 package, and does it > crash? Mint 22.1 package includes KMyMoney 5.1.3 and it does not crash. AppImage KMyMoney 5.2.1-cb18307 also does not crash. Mint 22.3 package includes KMyMoney 5.1.3 and it does not crash. AppImage KMyMoney 5.2.1-cb18307 crashes. Will re-run gdb and report back.
Created attachment 188925 [details] KMyMoney backtrace Ah, gdb "run"; that's the secret command I missed. Anyway, here's a screenshot showing gdb output at point of failure. The first 5 lines are the result of selecting a transaction. As soon as I clicked on the split icon, the blank line and 2 following lines were generated. Then I entered the "bt" command to generate the rest. Hopefully this is useful. I could re-run this with output to a text file If it would help. Or, I could run debuginfod on the appimage in non-crashing Mint 22.1 for comparison purposes.
Seems it fails on restoring a previously saved settings information for the split view header. That might explain, why it is crashing only on this one computer. Can you try to 1. stop all KMyMoney instances 2. rename ~/.config/kmymoney/kmymoneyrc to ~/.config/kmymoney/kmymoneyrc.bak 3. Start the application (settings will be reset to defaults, so don't be surprised) and see if the problem persists? If the problem still shows up, please report back. If not try this: 4. stop all KMyMoney instances 5. rename ~/.config/kmymoney/kmymoneyrc.bak to ~/.config/kmymoney/kmymoneyrc 6. remove the section named "[SplitEditor]" and all its entries (should be two) from ~/.config/kmymoney/kmymoneyrc 7. save the file 8. Start the application (settings will be back) and see if the problem persists?
Creating new kmymoneyrc file resolved issue (did not crash when opening Split Editor). Removing "[SplitEditor]" section from previous kmymoneyrc file also resolved issue (no crash). Application now seems to be operating normally. Any idea what may have caused the configuration file corruption, if that's what it was?
> Any idea what may have caused the configuration file corruption, if that's what it was? The only thing I can think of is that this happens when when switching between different versions of KMyMoney.