SUMMARY I am trying to relocate a closed loan account in the accounts hierarchy, option "Edit > Modify other loan information" does not allow me to choose its parent account, and "Edit > Modify loan attributes" makes KMM crash with the following error msg: Unknown schedule id 'SCH000124' in file /build/kmymoney-Dt2Zsa/kmymoney-4.7.2/kmymoney/mymoney/storage/mymoneyseqaccessmgr.cpp line 1,285 STEPS TO REPRODUCE 1. Close a loan account 2. Try to relocate it in the accounts family tree (hierarchy) 3. KMM crashes OBSERVED RESULT Loan accounts cannot be relocated in the hierarchy, and KMM crashes EXPECTED RESULT KMM should allow relocating a loan account like for other types of accounts, and should not crash. SOFTWARE/OS VERSIONS KDE: 4.14.2 Qt Version: QMake version 3.0 Using Qt version 5.2.1 in /usr/lib/x86_64-linux-gnu
If you reopen the account, can you then move it (and close it again after moving?) Regarding the crash - is there still a schedule for this loan? If so, try closing/ending the schedule before closing the account. Also, as Thomas said in a comment to your other bug, 4.7 is very old, and we would need to know if this still happens with 5.x or even 4.8.x.
Jack, yes when I try to move the account(s) I re-open them, and then try to move them... No, regarding the crash, the schedules have been deleted a LONG time ago (most were for a mortgage 10+ years ago which has been closed). I need to upgrade Linux Mint to latest and then reinstall everything and try KMM 5. Fair question but I need to ask: Is 5.0 ready for production? My KMM DB (via MySQL) has 20k+ transactions & splits, almost a hundred schedules and several thousand payees, etc.... backups are being made daily, but I'd rather keep using a reliable/proven release instead of being upstream too much with my important data. As for testing the newest & greatest, I can always use a VM to do so with a copy of my DB.
I personally have been using the 5.0 branch git head for a long time, but I don't use the sql back end. I have not used Mint in a long time, so I don't know how hard it would be to find a 4.8 package that should work for you without a full upgrade. In any case, I would certainly advise backing up the database before trying any new version. Another thought: have you grepped your kmy file for SCH000124? That might show where it is being referenced, and we might find a way to remove that reference and avoid the crash. Note: If you change the but state back to "Reported" when you reply, we might notice and be able to reply sooner.
Unfortunately, I am in worst position after upgrading the OS and KMM to 5.0.0. See https://bugs.kde.org/show_bug.cgi?id=406990
Tried to move accounts in KMM 5.0.0, still cannot relocate loan accounts. Trying to relocate via: "Edit > Modify other loan information" STILL does not allow me to choose its parent account However "Edit > Modify loan attributes" NO LONGER makes KMM crash.
Changed KMM version in this bug ticket, in KMM > Help > About KMM I see Version 5.0.0 but Linux Mint package reports 5.0.1.......... dpkg -s kmymoney Package: kmymoney Status: install ok installed Priority: optional Section: kde Installed-Size: 12337 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: amd64 Version: 5.0.1-2 Depends: kio, libalkimia5-7 (>= 7.0), libaqbanking35 (>= 5.6.1beta), libc6 (>= 2.14), libgcc1 (>= 1:3.0), libgmp10, libgpgmepp6 (>= 1.10.0), libgwengui-cpp0, libgwengui-qt5-0, libgwenhywfar60 (>= 3.11.6), libical3 (>= 3.0.0), libkchart2 (>= 2.6.0), libkf5activities5 (>= 4.96.0), libkf5akonadicore-bin, libkf5akonadicore5abi1 (>= 4:16.12.3+git20170414), libkf5archive5 (>= 4.96.0), libkf5codecs5 (>= 4.96.0), libkf5completion5 (>= 4.97.0), libkf5configcore5 (>= 4.98.0), libkf5configgui5 (>= 4.97.0), libkf5configwidgets5 (>= 5.23.0), libkf5contacts5 (>= 15.07.90), libkf5coreaddons5 (>= 5.2.0), libkf5holidays5 (>= 15.12.0), libkf5i18n5 (>= 4.97.0), libkf5identitymanagement5abi1 (>= 16.04.3), libkf5itemmodels5 (>= 4.96.0), libkf5itemviews5 (>= 4.96.0), libkf5jobwidgets5 (>= 4.96.0), libkf5kcmutils5 (>= 4.96.0), libkf5kiocore5 (>= 4.96.0), libkf5kiofilewidgets5 (>= 4.96.0), libkf5kiowidgets5 (>= 4.96.0), libkf5notifications5 (>= 4.96.0), libkf5service-bin, libkf5service5 (>= 5.2.0+git20140930), libkf5sonnetui5 (>= 4.96.0), libkf5textwidgets5 (>= 4.96.0), libkf5wallet-bin, libkf5wallet5 (>= 4.96.0), libkf5webkit5 (>= 4.96.0), libkf5widgetsaddons5 (>= 4.96.0), libkf5xmlgui-bin, libkf5xmlgui5 (>= 4.98.0), libofx7, libpython2.7 (>= 2.7), libqt5core5a (>= 5.9.0~beta), libqt5dbus5 (>= 5.0.2), libqt5gui5 (>= 5.8.0), libqt5network5 (>= 5.1.0), libqt5printsupport5 (>= 5.0.2), libqt5quickwidgets5 (>= 5.3.0), libqt5sql5 (>= 5.0.2), libqt5webkit5 (>= 5.6.0~rc), libqt5widgets5 (>= 5.4.0), libqt5xml5 (>= 5.1.0), libstdc++6 (>= 5.2), libaqbanking35-plugins, kmymoney-common (= 5.0.1-2) Recommends: gnupg-agent, pinentry-qt | pinentry-x11 Suggests: kcalc Description: personal finance manager for KDE KMyMoney is the Personal Finance Manager for KDE. It operates similar to MS-Money and Quicken, supports different account types, categorisation of expenses, QIF import/export, multiple currencies and initial online banking support. Original-Maintainer: Debian KDE Extras Team <pkg-kde-extras@lists.alioth.debian.org> Homepage: https://kmymoney.org/
If your distro does not provide update packages for newer versions of KMyMoney, please try to run off an AppImage which can be found on https://binary-factory.kde.org/job/KMyMoney_Stable_Appimage_Build/ I just made another change in that area which fixes bug 402672. This should be part of the next run of the AppImage build (#98).
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!
After several years without retrying anything for this issue, I just tried using 5.1-606 I still dont see any option in Loan properties to move the account somewhere else in the accounts tree.... Moreover, renaming the loans worked for all except an old one that I created back in 2009. KMM just crashes with the following message in Terminal and nothing else: Segmentation fault (core dumped)
First, to move a loan account, can you try to drag/drop it to the new parent in the Accounts View? It is a known problem that editing a loan account only lets you edit the scheduled transaction information for the loan, not the basic loan account details. Separately, when you get the crash on renaming the account, how are you trying to rename it?
Moving the account using drag and drop is only available in the master branch version not in any 5.1 version.
@Jack: I renamed the loans by doing this: -> Right-click on the loan, then select "Edit account" then click the "Next" button; -> Select "Modify loan attributes" (the last radio box in the list) then click the "Next" button; -> Rename the loan in the text box then click the "Finish" button. @Thomas: Thanks for clarifying the drag'n drop thing ;)
Given that you CAN move a loan account in master branch, I'd like to close this as fixed in 5.2. However, if the crash on rename is still happening, we can either change the bug to that issue, or open a separate bug for that problem.