[kmymoney] [Bug 403558] New: Problem caleder/date
https://bugs.kde.org/show_bug.cgi?id=403558 Bug ID: 403558 Summary: Problem caleder/date Product: kmymoney Version: 4.8.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bugtracker Assignee: kmymoney-devel@kde.org Reporter: heidikrahn...@gmx.de Target Milestone: --- SUMMARY Sorry, my english ist too bad and Idnon't understand enough of develloping programs: In kmymoney 4.8.2. there is a problem with the date. The calender shows the correct date, but if I choose it manually it is 14 days later or earlier and it changed the date of all the old bookings into 14 days earlier. Is this a problem in compatibility with my computer? What can I do to change it? STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 403558] Problem caleder/date
https://bugs.kde.org/show_bug.cgi?id=403558 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Thomas Baumgart --- This sounds very weird to me. Maybe, you can explain your problem in German (since some of the devs do understand that pretty well). In which view does this happen? Please explain exactly what you do and what happens, e.g. I open this view, I click this button, I enter this data, and when I press OK this happens. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 403558] Offset in date when using calendar
https://bugs.kde.org/show_bug.cgi?id=403558 Thomas Baumgart changed: What|Removed |Added Summary|Problem caleder/date|Offset in date when using ||calendar -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 403565] New: Crash when importing qif
https://bugs.kde.org/show_bug.cgi?id=403565 Bug ID: 403565 Summary: Crash when importing qif Product: kmymoney Version: 5.0.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: importer Assignee: kmymoney-devel@kde.org Reporter: kwanza.p...@virginmedia.com Target Milestone: --- Created attachment 117642 --> https://bugs.kde.org/attachment.cgi?id=117642&action=edit Backtrace SUMMARY Whenever, I try to import a QIF file, the application crashes immediately STEPS TO REPRODUCE 1. Select "import->QIF" 2. Select file to import (in QIF format) 3. Select Asset class OBSERVED RESULT Immediate crash EXPECTED RESULT Import file and process transactions SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 403558] Offset in date when using calendar
https://bugs.kde.org/show_bug.cgi?id=403558 --- Comment #2 from heidikrahn...@gmx.de --- Yeah, I think that's pretty crazy too.I use Windows 10 - I tried kmymoney version 4.8.2 of kmymoney.org and Heise.de - both times the same problem. Now I went back to 4.6.4, which works, but is very slow on my computer. So here is my description in English and further down the German version, in case I got things badly formulated. When I use the Calendar: I have opened the form for entering a booking and would like to enter a new booking. I open the calendar and click on the date. In the field in which the date is displayed, a date appears which is 14 days before. If I finish the booking with ‚enter’, this wrong date appears in the list of bookings. When I enter the date directly in the field: I have opened the form for entering a booking and would like to enter a new booking. I enter the date directly in the field in which the date is displayed, then the correct date appears. When I finish the booking with 'enter', this correct date will appear in the list of bookings. Old bookings: I used a file that already had bookings. The dates of all the old bookings were postponed by 14 days earlier, than they were before. Create a new file: When I create a new file, there is the same problem when I try entering the opening date. Wenn ich den Kaldender nutze: Ich habe das Formular zum Eingeben einer Buchung geöffnet und möchte eine neue Buchung eingeben. Ich öffne den Kalender und klicke das Datum an. In dem Feld, in dem das Datum daraufhin angezeigt wird, erscheint ein Datum, das 14 Tage vorher liegt. Wenn ich die Buchung mit enter abschließe, erscheint dieses falsche Datum in der Liste der Buchungen. Wenn ich das Datum direkt in dem Feld eingebe: Ich habe das Formular zum Eingeben einer Buchung geöffnet und möchte eine neue Buchung eingeben. Ich gebe das Datum dirket in dem Feld ein, in dem das Datum angezeigt wird, so erscheint das richtige Datum. Wenn ich die Buchung mit enter abschließe, erscheint dieses richtige Datum in der Liste der Buchungen. Alte Buchungen: Ich habe eine Datei genutzt, in der schon Buchungen vorhanden waren. Die Daten aller Buchungen wurden um 14 Tage zurückverlegt, nachdem ich die Datei geöffnet hatte. Eine neue Datei anlegen: Wenn ich eine neue Datei anlege, gibt es bei der Eingabe des Eröffnungsdatums das gleiche Problem. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 403558] Offset in date when using calendar
https://bugs.kde.org/show_bug.cgi?id=403558 --- Comment #3 from heidikrahn...@gmx.de --- Hey, I „solved“ the problem. After installing the 8.4.2-Version I opened the language-setting and reseted all items to their default value. Then it worked. I do not know why – it seems like the settings of the old version were not compatible with the new on. -- You are receiving this mail because: You are the assignee for the bug.
Re: KmyMoney 5.0.0
Dean, To be clear, I am not a KMM developer. I have been compiling from source for 10 or more years and I wrote scripts to manage it back in the cvs days, migrated the scripts to svn and then to git. I shared them on the mailing list a long time ago but they were not very user friendly at the time. I have recently made them much more user friendly, interactive and generic. I will send an email to the list shortly with the current version assuming I can attach a tar file. If not I will find some other way to share them. I hope they help you install either the current official release or, better yet, from one of the git branches. Brendan Coupe On Thu, Jan 24, 2019 at 2:35 PM Dean Albert wrote: > Hi, > > I am using KmyMoney version 5.0.0. I got it from Linux Mint 19.1 Mate. > Synaptic was used to install it. Synaptic calls the version 5.0.1-2. That > is incorrect. 5.0.0 is right as that is on the welcome screen and under > "About". > > I have some easy to fix (I think) bugs with the program. > > I have been using it for 8-10 years. I don't use checks much, but I do > use the "No." column all the time for other reasons. > > In earlier versions of KMM, I was able use the check number which would > auto increment, but I was also able to use repeating numbers to signify > debit card transaction numbers. (I have to keep track of them for some > bank programs.) When I put in a duplicate "check number" a warning would > popup saying: "Check number xxx has already been used in account > xxx. Do you want to replace it with the next available number? NO > or YES". I would click "NO" and I would be able to reuse that number. > > Every month for example I would run the numbers from F1,F2,... to F12. > Then, I would do the same numbers the next month. It was a way of keeping > track of the debit card transactions. I can not do that anymore and it is > making working with KMM a real pain. > > 1) The 5.0.0 program has a button under KMM Ledger, Data Entry called > Auto Increment Check Number. The button is there to allow you to turn OFF > auto increment. However, it does NOT work. Nor would I want it to, as > when I write a check, I would not want it to duplicate a number. > > When I want to use the same check number or debit card transaction number, > etc., I get the same warning about duplicate check numbers as before, but > when I click "NO" meaning let me reuse the check number, it ignores my > selection and no number is allowed to be put in the box! It does not allow > the repeat of the number even though it gives you a choice. It does NOT > work properly. I ran into this when I tried KMM on Windows. In previous > Linux & KMM versions I was able to repeat check numbers with no issues. > > SOLUTION: > > A) Please get rid of the Auto Increment button and leave the default > as Auto Increment Check Number. That way people who want to auto increment > their check numbers can. > > Getting rid of the button means you don't have to fix it, as it is > useless anyway. > > B) When you try to duplicate a check number and the warning comes up > telling you that you are about to use a duplicate check number, allow the > user to click the "NO" button and duplicate the number if they desire. It > they want > > Auto Increment, they click the "YES" button. > > > 2) I have been forced to use Tags as a way around this. However, there > are issues with Tags. First the field is too long. It takes up a lot of > the Memo field. I use the Memo field to copy & paste confirmations of > bills that I pay. It is the most important field in the entire program and > should be the largest field. Now, it is difficult to see what I am doing > as the height is not as tall as it was. I also use the "No." field to > paste the receipt of the check I paid through the bank. This works only > because the confirmation numbers are always changing. It is theoretically > possible for two to be the same at some point in the future. If you don't > have the duplicate check number warning "NO & YES" options working, you > could not enter a duplicate confirmation number either. > > Using Tags take longer as I have to go to a drop down field for the > correct Tag. Since I have multiple bank accounts, the number of Tags is > quite large. 68 in my case. > > SOLUTION: > > C) Please allow users to turn Tags On or Off if they don't want to > use them. > > D) Make the Tag field less intrusive if you insist on having them. > > > I have been in contact with one of your developers, Brendan Coupe. He has > been very helpful on this subject. He told me I should report bugs to the > development team. I was reporting them through the KMM program whch sent > me to the KDE bug site. That's why I am writing to you now. > > He is using a different version of KMM than I am am, so he was not able to > duplicate the bugs I ran into. He is using 5.0.2. > > I am not a Linux wiz. I can no
KMM Build Scripts
I have been running my own scripts to compile, install and uninstall KMM since back in the cvs days. I have recently updated them to make them more user friendly, interactive and generic. I will post the latest versions of the scripts on Google Drive for any interested users to try out. Your feedback is welcome. The first public version can be found here: https://drive.google.com/drive/folders/1sfo2HgzaCCSb3d7pjl3To50yoQT5BaXM The basic steps are: 0) Read the README.txt file 1) Remove any version of KMM that you installed another way before using running step 4. Step 3 is safe with an installed version of KMM. 2) Do your best to get the dependencies installed (hints in the README.txt file, this is the hard part). 3) Run the BuildKMM.sh script, this does not install anything. If it does not get to 100% it failed. Back to step 2. 4) Run the InstallKMM.sh script, this does install KMM. Don't run this unless step 3 is successful. 5) Repeat steps 3 & 4 in order to move to a newer (or older) version of KMM or between branches and/or releases. 6) Run the RemoveKMMBuilds.sh script to remove build directories of builds you never plan to use again. 7) Run the UninstallKMM.sh script to Uninstall the currently installed build that was installed with these scripts. This should be done before reinstalling from any other source, such as your package manager. To be clear, Uninstalled means uninstalling KMM from your system. Remove means remove the build folders containing compiled versions you never plan to install again. Never remove the installed version build folder (should be impossible with the script). I install from source every week or two so the old build directories can pile up. All builds are clean builds with full source download. These scripts do not have any provisions for updating an existing source tree fro git. If you want to use these scripts to install an official KMM release just download the release source code (kmymoney-5.0.2.tar.xz) and put it in your build directory and run BuildKMM.sh. I have run all of the scripts many times on 3 clean systems and have fixed all of the bugs that I could find and added as many troubleshooting messages as I could to help you understand what went wrong. Start with the README.txt file, modify the ScriptsKMM.conf file as needed. Then try to build and install. I know there are probably a lot of errors that I did not run into so please help me find and fix them. Please submit any questions to the KMM developer mailing list with the above subject. If you have dependency issues please submit them to the mailing list with a different subject. The developers have helped me solve dependency problems many times. Brendan Coupe BuildScriptsKMM-2019.01.24.tar.gz Description: application/gzip
[kmymoney] [Bug 403558] Offset in date when using calendar
https://bugs.kde.org/show_bug.cgi?id=403558 Thomas Baumgart changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are the assignee for the bug.
Re: KmyMoney 5.0.0
Dean, On Donnerstag, 24. Januar 2019 22:34:47 CET Dean Albert wrote: > I am not a Linux wiz. I can not change to 5.0.2 or anything that uses a > .tar.gz file. I have no clue how to compile or figure out which > dependencies to use, much less find them. I use Synaptic to do this. > Apparently, it is Mint version specific. I can use the terminal if if > am told what to write in each line. Let's give that a try then. Before I jot some command lines here, I want you to make a backup of your data. Just in case. 1) Visit https://binary-factory.kde.org/job/KMyMoney_Nightly_Appimage_Build/ and download the latest successful artifact (which is currently around 180 MB). 2) Save the file in your local directory folder (e.g. your user home directory - which I will use in the following) 3) Make that file executable (the number in the filename may change depending on changes we make) cd $HOME chmod 755 kmymoney--7152278-x86_64.appimage 4) Execute the program (again, the number may be different) ./kmymoney--7152278-x86_64.appimage You are now running a very current software version of KMyMoney. It is build daily, so when we change something you have it the next day. You should try that. It does not solve your problems, but you make sure to have things in place once they are available. Hope that helps so far. -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Computers let you make more mistakes faster than any other invention in human history, with the possible exception of handguns and tequila. --Mitch Radcliffe - signature.asc Description: This is a digitally signed message part.
