https://bugs.kde.org/show_bug.cgi?id=358854
--- Comment #3 from allan ---
Come on now! We're a bit tetchy aren't we? I don't think you can have read .my
response fully as I am interested.If I gave that impression then I must be more
careful.While I did mark it as 'works for me' I went on to indi
https://bugs.kde.org/show_bug.cgi?id=342401
--- Comment #6 from harry bennett ---
FYI: I changed the heading on the bug to better reflect what I mean
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=342401
--- Comment #5 from harry bennett ---
Sure.
Christian hands me a check for services ($500).
Jack hands me a check for services ($1000).
Both of these checks may land into the same category (1099 income, in my case).
I walk into the bank and make a singl
https://bugs.kde.org/show_bug.cgi?id=342401
harry bennett changed:
What|Removed |Added
Summary|allow splits on payees |allow different payees on
|
https://bugs.kde.org/show_bug.cgi?id=358854
--- Comment #2 from Clark Wierda ---
I should know better than to submit bugs to KDE projects by now. I may yet
learn.
I feel obligated to report the conditions where it fails.
"FMCC CAFE 60033818 DEARBORN MI" is interpreted as "DEARBORN MI"
"BEST BU
Hi,
On Monday 01 February 2016 14:46:20 Christian Dávid wrote:
> Am Donnerstag, 28. Januar 2016, 16:51:35 schrieb Jack:
> > First, is there any way to make aqbanking remember the password? It
> > prompts every time, and I don't see any boxes or settings.
>
> No, there is no option to save the p
https://bugs.kde.org/show_bug.cgi?id=342401
Christian David changed:
What|Removed |Added
CC||christian-da...@web.de
--- Comment #4 from Ch
Am Donnerstag, 28. Januar 2016, 16:51:35 schrieb Jack:
> First, is there any way to make aqbanking remember the password? It
> prompts every time, and I don't see any boxes or settings.
No, there is no option to save the password permanently. This is currently
indented as most banks forbid the
https://bugs.kde.org/show_bug.cgi?id=355116
--- Comment #12 from allan ---
(In reply to Clark Wierda from comment #11)
> So the suggested fix is to revert to the older version and call it done?
Linux -
> So just for the in case anyone is experiencing the same problem: this bug
> has occurred wit
https://bugs.kde.org/show_bug.cgi?id=358854
allan changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=358579
--- Comment #10 from allan ---
I've been suffering from tunnel vision, and have been reading all the above
comments without noticing that there were two contributors. Apologies for
that, although it has had no bearing on the cause or analysis.
Your fe
https://bugs.kde.org/show_bug.cgi?id=358579
--- Comment #9 from MGR ---
Thank you for your answer.
What a pity with this problem that has no quick solution !...
After the Aquila's analysis, I started to eliminate the incriminated
symbols (<&>) in more than 20 accounts (in order to clean up _mo
12 matches
Mail list logo
