[kmymoney4] [Bug 358129] Changing dividend transaction to reinvested dividend transaction after import of QIF/QFX file on online banking update.
https://bugs.kde.org/show_bug.cgi?id=358129 NSLW changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||lukasz.wojnilow...@gmail.co ||m --- Comment #6 from NSLW --- KMM 4.7.1 is old and unmaintained. Please update to 4.8. Besides: (In reply to Jack from comment #3) > [...] I have plenty of > OFX transactions that import as dividend, that I change to > reinvest-dividend, and it works fine for me. [...] -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 363824] Crash when i save a new budget report
https://bugs.kde.org/show_bug.cgi?id=363824 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from NSLW --- KMM 4.7.2 is old and unmaintained. Please update to 4.8. There is no problem on master version. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 343291] backup fail
https://bugs.kde.org/show_bug.cgi?id=343291 NSLW changed: What|Removed |Added Product|kmymoney|kmymoney4 Component|General |general CC||lukasz.wojnilow...@gmail.co ||m -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 345113] KMyMoney crashes when trying to retrieve deleted account details
https://bugs.kde.org/show_bug.cgi?id=345113 NSLW changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED CC||lukasz.wojnilow...@gmail.co ||m --- Comment #2 from NSLW --- (In reply to Thomas Baumgart from comment #1) > This looks like an AqBanking problem to me[...] -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 384062] New: Printing Reports
https://bugs.kde.org/show_bug.cgi?id=384062 Bug ID: 384062 Summary: Printing Reports Product: kmymoney4 Version: 4.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-devel@kde.org Reporter: jpf4...@outlook.com Target Milestone: --- When I try and print a Report to my HP Wireless printer I get a message saying report can not print. Dose this software support the HP deskjet 2600 series Printers -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 354944] Line/bar Chart Reports Unavailable for Full Period Spanning Years
https://bugs.kde.org/show_bug.cgi?id=354944 --- Comment #4 from flywire --- This is an aside to the whole issue of not using the Fiscal year setting which still stands. @Ralf Habacker - Can you confirm the bug? -- You are receiving this mail because: You are the assignee for the bug.
libalkimia version questions
Am I correct that KMM 4.x requires libalimia < 6.0.0 and git master requires >= 6.0.0? Can these two versions of libalkimia coexist, or not? I know one can be installed outside the main system area, and the version of KMM that need it can be pointed to it, but wanted to be sure that was necessary. (In Gentoo terminology, can the two versions be in different slots?) Where is the "official" home of libalkimia? All the Gentoo resources seem to point to "http://kde-apps.org/content/show.php/libalkimia?content=137323"; which has a most recent date of 2012. Thanks for any info. Jack
[kmymoney4] [Bug 384051] New: No reset of hcbi account pin possible
https://bugs.kde.org/show_bug.cgi?id=384051 Bug ID: 384051 Summary: No reset of hcbi account pin possible Product: kmymoney4 Version: 4.8.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-devel@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- I tried to configure hbci for a newly created german volksbank account. After entering the account data kmymoney connected the hbci server and got the message that the pin needs to be changed before accessing this account. Then I openend a browser and changed the pin at the online banking web frontend. After returning to kmymoney I tried to finish the account registration but I did not found any button to reenter the changed pin. Instead it tries to continue with the old pin which results into a locked account. I need to cancel hbci account registration and shutdown and start kmmymoney again and have to add the hbci account again with the changed pin. How to reproduce ? See above with a newly created hbci account What is expected ? If there any problems with accessing the account on the account registration process it should be possible to save the recent setting and to finish the hbci account registration process later point there is no way to save the recent settings and to return back later. At this point it should not use the cached pin. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 384021] Crash on investment charts with multiple investments
https://bugs.kde.org/show_bug.cgi?id=384021 --- Comment #2 from David Houlden --- Created attachment 107532 --> https://bugs.kde.org/attachment.cgi?id=107532&action=edit Anon file to demonstrate problem Open the anon file attached. In investment reports, R13, 14, 16 will crash KMyMoney. R18 will work. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 384021] Crash on investment charts with multiple investments
https://bugs.kde.org/show_bug.cgi?id=384021 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- You have a test case or a how to reproduce ? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 383977] In Accounts view, do not change expand/collapse state after editing an account
https://bugs.kde.org/show_bug.cgi?id=383977 NSLW changed: What|Removed |Added Version|git (master)|unspecified Status|UNCONFIRMED |CONFIRMED CC||lukasz.wojnilow...@gmail.co ||m Ever confirmed|0 |1 Component|general |General Product|kmymoney4 |kmymoney -- You are receiving this mail because: You are the assignee for the bug.
