https://bugs.kde.org/show_bug.cgi?id=464055

--- Comment #14 from Guy <gmalacr...@gmail.com> ---
Hello Jack,
I found a way to solve the issue thanks to a thread in KDE.org, i.e.
https://forum.kde.org/viewtopic.php?f=69&t=173354
I think I'm basically did not setup Bitcoin properly although it
worked quite well since 2019 .....
Anyway, I followed the advice from the people in that thread and
created a security BTC, an investment a/c "Investement in BTC" and a
brokerage a/c "Investment in BTC (brokerage)".
It works, differently though as I need to input the BTC CHF rate (i.e.
19'988) instead of the c/v in CHF (i.e. CHF 60).
Thanks for your help and have a good day.
Guy

Le mar. 17 janv. 2023 à 18:43, Guy Malacrida <gmalacr...@gmail.com> a écrit :
>
> I'll have to figure out how to create that small .kmy file.
> Looks to me a currency issue. I enclose a snapshot of the same kind of
> transaction in November that went OK (kmymonneyNoCrash.png). You can
> see that exchange rates are proposed whereby none are proposed in the
> new transaction that crashes the programme (see kmymonneyCrash.png).
> One was in EUR and the last in CHF though...
>
>
>
> Le mar. 17 janv. 2023 à 16:37, Jack <bugzilla_nore...@kde.org> a écrit :
> >
> > https://bugs.kde.org/show_bug.cgi?id=464055
> >
> > Jack <ostrof...@users.sourceforge.net> changed:
> >
> >            What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >             Summary|crash when entering a       |crash when entering a
> >                    |portfogllio transaction     |portfollio transaction
> >
> > --- Comment #11 from Jack <ostrof...@users.sourceforge.net> ---
> > I need to find time to make another attempt to reproduce this.  If you can
> > create a small .kmy file which demonstrated the error (with exact 
> > instructions
> > on how to trigger it) that would be helpful.  I'll leave the status for 
> > now, so
> > we get reminded if nothing happens for too long.
> >
> > --
> > You are receiving this mail because:
> > You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to