Summary: | KMyMoney crashes after mapping an online account w/ AqBanking | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | dgns2009 |
Component: | onlinebanking | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bob, lukasz.wojnilowicz, martin |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
dgns2009
2016-11-27 14:41:11 UTC
Something is wrong with the information managed by AqBanking. Did you ever use AqBanking for production purposes? Are there any mapped accounts with valid information setup? Do you use another application (e.g. GnuCash) that uses AqBanking? I am asking, becuase it might be the easiest to wipe out the AqBanking data that is certainly missing something. But before I tell you how to do it, I want to make sure we don't wipe out important data. You could try to start KMyMoney from the command line with option -n which prevents opening the last opened file after startup. Goto Settings/Aqbanking settings and remove entries for accounts and users you don't need. See if that makes a difference when loading a KMyMoney file. I never used AqBanking for production purpose. I set up an "testing" account in the fleeting hope to be able to connect to PostFinance (in spite of all information to the contrary...) After deleting ~/.kde/share/config/kmymoneyrc, starting KMyMoney without loading an existing file, disabling all plugins in the settings menu, I was able to load my original kmy-file again. Since then I'm able to load/save without problems. I haven't tried to re-enable the AqBanking-plugin again. Please see if the information at https://bugs.kde.org/show_bug.cgi?id=375391 helps you. *** This bug has been marked as a duplicate of bug 375391 *** |