Summary: | kmymoney crashes after aborting removal of aqbanking stale lock file | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | MK <bugs.m1> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
MK
2011-02-13 08:38:56 UTC
Hi,
On Sonntag 13 Februar 2011, MK wrote:
[...]
> #9 0x00007f38dc862389 in AH_User_Extend (u=0x3bde0f0, pro=0x3983d90,
> em=AB_ProviderExtendMode_Extend, db=0x3b91e70) at user.c:184
[...]
Fixed in current SVN of AqBanking.
The problem with hitting "abort" in this situation is that the AqBanking
settings database might become inconsistent in this case (e.g. some account
settings might have been been written already but the corresponding user
settings have not due to the abort).
However, if you are sure that your instance of KMyMoney is the only
application accessing the settings database at that time you can safely allow
for the forced removal of the file lock.
Regards
Martin
Closed by upstream. |