| Summary: | Error with transaction. | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | rzeta <erre.zeta> |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | NEEDSINFO WAITINGFORINFO | ||
| Severity: | normal | CC: | mrp |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Transactione splited
unpacked directory. |
||
Please try to switch to the latest stable version of KMyMoney 5.2.1. The whole editing of transactions and splits has been rewritten. If the problem persists with that version, please let us know. Thank you Thomas, The version I use is the latest one that LMDE6 makes available in its repositories. Can you show me where to download the latest version you say, but not AppImage version? Better Deb or Flatpack. I can't find.. I have tried AppImage 5.2.1-d892ba4, but for my problem nothing changes. Some graphical improvements, but negative balances aren't coloured in red. Thanks bye Unfortunately, using a LTS distribution often has the side effect of making it very difficult to get a updated version of all packages. Also, if any new fix is applied to KMyMoney, it will only be applied to master and 5.2 branches, and as the code in this area has changed, as Thomas said, it will not be easily backported to 5.1. https://kmymoney.org/download.html leads to all the versions available for download, including snap. There is also a flatpak version, but it says the latest is 5.1.0 (which was a known mislabel for 5.1.3.) I had thought there was a more recent version packaged, so I don't know if I'm wrong, or it's just still mislabeled. I'm curious why you don't want to use an Appimage. The version you mention is a week old, although I think that was after the 5.2.1 release, so it should include the fix for your original issue. If it doesn't, please provide an updated screenshot. The lack of red for negative balances is known, and will eventually get fixed, but I'm not sure how high a priority it is at the moment. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! (In reply to Jack from comment #3) > I'm curious why you don't want to use an Appimage. I have tried using different releases of Appimage, but with daily updates, they do not look like stable versions to me. I also tried downloading version 5.2.1 tar.xz but I can't compile it to use. The developer version of the Appimage is from master branch of git, so definitely not stable. The "stable" version is from the git head of the 5.2 branch, which is the released version plus bug fixes. You are correct it is not exactly the same as the released version, but it should be safe to use. Compiling from source is not really difficult, but it can be a challenge if you are not used to compiling software. Besides, if you compile from git (either master or 5.2 branch,) what you end up with it pretty much equivalent to the Appimage. Compiling from a released tarball should give you the released version, but it that is easy, then the Distro would likely have done it. Stable and LTS releases are often stuck on older versions of underlying libraries, making it difficult to do upgrades. On your original issues: the liability balances not shown in red is know, and will eventually get fixed. I'm not sure what you mean by not being able to remove a label. If you mean a tag, it should be possible to remove it, so please describe exactly what you have tried. (In reply to Jack from comment #6) Thank you for your quicky reply > > On your original issues: the liability balances not shown in red is know, > and will eventually get fixed. Well.... hopefully soon >I'm not sure what you mean by not being able > to remove a label. >If you mean a tag, it should be possible to remove it, > so please describe exactly what you have tried. Exactly what I meant... it is not possible to remove a previously inserted tag You can see the image I attached at the beginning. That's all I do... I select the first line with an empty tag, but on exiting the previous one As for the downloaded Tarball. Once it has been unpacked, I cannot find any different instructions to give the commands I know ./configure make make install KMyMoney (and most KDE software) does not use ./configure. Instead, you create a build directory, cd into it, and then run "cmake path/to/the/root/of/unpacked/tarball". There are lots of potential options, but the defaults should work OK as a starting point. After that, you can still do make and make install. I don't understand your screenshot. Unfortunately, you can't resize the columns until you run the new version, and even if there is a problem with 5.1.3, it will not get fixed, as it is probably already fixed in 5.2.1. Have you tried either the Flatpak or Snap version of 5.2.1? Created attachment 184640 [details]
unpacked directory.
I attach a screen of the unpacked directory.
(In reply to Jack from comment #8) > Have you tried either the Flatpak or Snap version of 5.2.1? I don't know where to download Flatpack. For Snap, the link location listed on the site is corrupt. https://snapcraft.io/kmymoney > KMyMoney (and most KDE software) does not use ./configure. Instead, you > create a build directory, cd into it, and then run "cmake > path/to/the/root/of/unpacked/tarball". Now I'm the one who doesn't understand the instructions. See my previous attachment Looks like we need to track down and publish proper links for current snap and flatpack. (flathub still refers for a years old 5.0.0 version.) For building yourself, the really abbreviated version is to unpack the tarball, cd into the root of the unpacked source, "mkdir build", "cd build", "cmake .." More complete building instructions used to be in several places, but were removed from many as redundant. https://develop.kde.org/docs/getting-started/building/cmake-build/ seems to be reasonably up-to-date, and certainly newer than when I started doing it years ago. The problem is once you start building software, it becomes rote, and then harder to describe to someone new to building from source. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Since there is a question about where to find flatpaks: https://discuss.kde.org/t/kmymoney-nightly-flatpak-available/39788 (In reply to Thomas Baumgart from comment #13) > Since there is a question about where to find flatpaks: > https://discuss.kde.org/t/kmymoney-nightly-flatpak-available/39788 Thank you. Can I find a stable flatpack release, not nightly? https://flathub.org/en/apps/org.kde.kmymoney , but it's on 5.1.3 until https://github.com/flathub/org.kde.kmymoney/pull/54 gets merged 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! |
Created attachment 184098 [details] Transactione splited The transaction breakdown contains display errors that make it difficult to work with. If a label is inserted, it cannot be removed.