[kmymoney] [Bug 390406] switching from Investments page to Ledgers always shows same stale closed account ledger
https://bugs.kde.org/show_bug.cgi?id=390406 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m --- Comment #10 from NSLW --- (In reply to David Nelson from comment #8) > Version 5.0.80-757c7cbe > > there still seems to be a problem... > > start kmm, click on Ledgers without selecting acct in home view, stale acct > is still shown, combobox shows 'Asset', before the fix this was blank. It could be a bug or a wish to change default behaviour. I think that using preferred account, as Thomas suggested, should solve your issue. > however, selecting Ledgers after Investments now syncs to the correct acct. > > thanks. No problem. Please don't aggregate issues in one bug, because it's harder to solve the bug. This bug was about synchronization between ledgers and investment views. Any other issue should be precisely reported as an another bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 390406] switching from Investments page to Ledgers always shows same stale closed account ledger
https://bugs.kde.org/show_bug.cgi?id=390406 --- Comment #11 from David Nelson --- i'm not comfortable yet with git branching, but i pulled branch 5.0 and confirmed that kgloballedgerview_p.h has your changes. if you start kmm, click on Ledgers (without selecting an account in Home view) the account selection combobox is still showing 'Asset'. the problem seems to be that Ledgers view does not default to an account (before the user selects one) in the way Investments view does. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391453] New: Displaying the ledger without an account having been selected displays a closed account
https://bugs.kde.org/show_bug.cgi?id=391453 Bug ID: 391453 Summary: Displaying the ledger without an account having been selected displays a closed account Product: kmymoney Version: 5.0.0 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: ostrof...@users.sourceforge.net Target Milestone: --- Originally reported as part of bug 390406 (switching between ledger and investment views did not always show the same account) the issue here is that if you select the Ledger view without having selected and account (in some other view) it displays a "arbitrary" account. (Arbitrary in the sense I don't know how it chooses, but it might just be the account with the lowest internal ID.) In that bug, it displayed an old, closed account, which probably should not be shown at all. I suggest the preferred display should be an empty ledger, until an account it actually chosen, but if a random/arbitrary account is displayed, it should be one of the preferred accounts, if there are any, but in no case should a closed account be displayed. I don't suppose it really matters much if this is considered a minor bug or a wishlist, but it should rarely be an issue, once the other bug is fixed. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 390406] switching from Investments page to Ledgers always shows same stale closed account ledger
https://bugs.kde.org/show_bug.cgi?id=390406 --- Comment #12 from Jack --- Per comment 11, the issue of which account is shown in the ledger if no account has yet been selected is different from showing some account in the ledger, switching to another view, and switching back to the ledger and seeing a different account. Since the fix for the first did not happen to address the second (because they really are separate issues) I've submitted this separately as bug 391453. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] New: passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 Bug ID: 391454 Summary: passwords not integrating (storing) with KMM 5.0 and KDEWallet properly Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bugtracker Assignee: kmymoney-devel@kde.org Reporter: mfcarp...@gmail.com Target Milestone: --- After Mapping a Brokerage account (checking & investment)using OFX the passwords don't appear to be linking correctly with KMM. I input the information (ID & Password) and update (download) the transactions which works fine. Then I come back again to update and it shows the account is mapped but the "Update account" is greyed out. If I select Update all accounts it asks me to select the checking account associated with an unidentifiable account. The only workaround is to unmap, remap and download the transaction each time. Passwords are properly stored in KDEWallet. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #1 from Jack --- I think the issue of KMM asking for the user to identify the checking account is a separate bug (I do not think yet reported, but I think I mentioned it on the mailing list) where it should automatically choose the Brokerage account for the Investment account being processed. I also think I reported to the mailing list the issue that accounts which were mapped in 4.8 did not show as mapped in 5.0. However, that issue was fixed in 5.0, even though it seems at least partly similar here. Also, please clarify which OFX you are using, and your process to map the account. From memory, you have to specify the ID and password when you map the account, and it should save them then. If you have to specify them again when actually updating the account the first time, then there might be some problem with password storage. I know I have not had any problem udpating accounts (OFX, not aqbanking) with 5.0. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #2 from Michael Carpino --- I tried a few different things which is appears to cause a linking issue or lack there of. First I deleted the passwords in KDEWallet to make sure the passwords where being set there correctly. Then I unmapped the investment accounts. With my first brokerage account(TD Ameritrade), I went the checking account and mapped the checking account by selecting account > map account > ofximporter > TD Ameritrade. After finalizing I verified that I can update and it works. But if I go to the Investment Ledger for this account it is still showing Unmapped. I can go through all the steps and map it but there is some type of linkage problem I didn't have to do this in earlier versions. With my other brokerage account (Fidelity NetBenefits) I went through the same steps above except I started by mapping the Investment ledger. Then I went to the (brokerage) checking account and it shows it isn't mapped. When I look in KDEWallet the paswords are stored there correctly. I have other accounts that are not "Brokerage" type and mapping is working just fine. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #3 from Jack --- So we need to fix the docs somehow, to make it clear how to handle this situation. You should ONLY map the investment account, and NOT the brokerage (checking) account. When you download, any cash transactions are correctly put in the associated brokerage account. (At least they used to be. Now, you may need to specify the brokerage account when KMM asks what checking account to use when you do the first update.) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #4 from Michael Carpino --- Yes, I dualboot and went to my windows 10 KMM 4.8.1.1 and the transactions are going into the investment account as you stated. With 5.0 the issue is it asks everytime what checking account you want to use. And there is no description on what account its referring to so you're clueless when you have more than 2 on what to do. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #5 from Michael Carpino --- With 5.0 the only way to kinda getting it to work is to Map both accounts (Brokerage and Investment) and the transactions are dumped into the checking account. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #6 from Jack --- I strongly suspect, but have no proof, that you will end up with more problems if you map the brokerage account. (In fact, I believe that KMM should warn you if yo do try to map a brokerage account, but it seem to only know that if you accept the default name for it, which is "(Brokerage)" appended to the name of the investment account. I don't know if there is a bug filed already for KMM asking where to put the "checking" transactions. If you only update one account at a time, you can know which brokerage account to specify, so until this is sorted, I would just advise against updating all at once. Also,, you should not be able to map more than one KMM account to the same online account, or else it wouldn't know which account to use. (That is true in general, although Investment accounts are of course different...) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #7 from Michael Carpino --- Ok I'll take your advice and unmap the brokerage/checking account and update the accounts 1 account at a time. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 391458] New: LibAlkimia5 required version not available
https://bugs.kde.org/show_bug.cgi?id=391458 Bug ID: 391458 Summary: LibAlkimia5 required version not available Product: kmymoney Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-devel@kde.org Reporter: eaglex...@gmail.com Target Milestone: --- When I try to build the 5.0 branch I get: CMake Error at CMakeLists.txt:58 (find_package): By not providing "FindLibAlkimia5.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "LibAlkimia5", but CMake did not find one. I looked in line #58 and it has: find_package(LibAlkimia5 7.0.0 REQUIRED) I am running Kubuntu 17.10 and I have libalkimia5 installed which is version 5.0.0. Package: libalkimia5 Architecture: amd64 Version: 5.0.0-3 Priority: optional Section: universe/libs Source: libalkimia Origin: Ubuntu After researching it appears that 7.0.0 is only available for KDE neon and Kubuntu 18.04 Boinc (scheduled to be release in Apr 2018). Can I change CMakeLists to match 4.8.1.1 or KMM not work? -- You are receiving this mail because: You are the assignee for the bug.
