Summary: | KMyMoney crashes when connecting to DKB Bank Berlin; AqBanking related? | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | daniel |
Component: | onlinebanking | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | lukasz.wojnilowicz |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.6.6 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
daniel
2015-07-05 09:01:40 UTC
Did you upgrade AqBanking packages in between? Please try to upgrade KMyMoney as well. Current stable is 4.7.2 which should also be available as package for your distro. Yes, it is certainly AqBanking related (which does not mean that the cause is in AqBanking itself). I have checked my bank account and was notified that the bank actually blocks access to it. I had similar experience before with them as they are quite aggressive with blocking accounts with "suspicious" behavior. I will get new account details soon - so this explains that access is blocked and therefore I assume the login problems are not related to KMyMoney or AqBanking. What I however do not understand is why the wrong login details can provoke the whole application to break. I assume there should be a notice about probably wrong credentials rather than a stall. Maybe someone finds the time to look into this Kind regards and thanks for the efforts on working on this application What I have found out is that the underrun of a counter throws an assertion in AqBanking code. I have no idea why that is, but have forwarded this entry to its author. Let's see what he comes up with. Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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! |