Re: segfault in new ledger code

2020-01-10 Thread Thomas Baumgart
On Freitag, 10. Januar 2020 23:24:24 CET Jack wrote: > On 2020.01.10 16:48, Thomas Baumgart wrote: > > On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote: > > > On 2020.01.10 15:34, Jack wrote: > >>> Per your suggestion in the Wayland thread, I just recompiled with > >>> UNFINISHEDFEATURES enab

[kmymoney] [Bug 415517] AppImage - Price update not working

2020-01-10 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=415517 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

Re: segfault in new ledger code

2020-01-10 Thread Jack
On 2020.01.10 16:48, Thomas Baumgart wrote: On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote: > On 2020.01.10 15:34, Jack wrote: Per your suggestion in the Wayland thread, I just recompiled with UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an immediate segfault, from both

Re: segfault in new ledger code

2020-01-10 Thread Jack
On 2020.01.10 16:48, Thomas Baumgart wrote: On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote: > On 2020.01.10 15:34, Jack wrote: Per your suggestion in the Wayland thread, I just recompiled with UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an immediate segfault, from both

Re: segfault in new ledger code

2020-01-10 Thread Thomas Baumgart
On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote: > On 2020.01.10 15:34, Jack wrote: > > Thomas, > > > > Per your suggestion in the Wayland thread, I just recompiled with > > UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an > > immediate segfault, from both 5.0 and master,

Re: segfault in new ledger code

2020-01-10 Thread Jack
On 2020.01.10 15:34, Jack wrote: Thomas, Per your suggestion in the Wayland thread, I just recompiled with UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an immediate segfault, from both 5.0 and master, and whether or not I have already selected an account. I'm pretty sure

segfault in new ledger code

2020-01-10 Thread Jack
Thomas, Per your suggestion in the Wayland thread, I just recompiled with UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an immediate segfault, from both 5.0 and master, and whether or not I have already selected an account. I'm pretty sure I can easily enough get a backt

segfault in new ledger code

2020-01-10 Thread Jack Ostroff
Thomas, Per your suggestion in the Wayland thread, I just recompiled with UNFINISHEDFEATURES enabled. Selecting the new ledger gives me an immediate segfault, from both 5.0 and master, and whether or not I have already selected an account. I'm pretty sure I can easily enough get a backt

[kmymoney] [Bug 416080] Kmymoney: distinction between date of record and date of movement

2020-01-10 Thread René
https://bugs.kde.org/show_bug.cgi?id=416080 --- Comment #2 from René --- Thank you for your reply. Looking forward to solving this issue. Regards. René Cluzel Le vendredi 10 janvier 2020 à 12:24 +, Thomas Baumgart a écrit : > https://bugs.kde.org/show_bug.cgi?id=416080 > > Thomas Baumga

[kmymoney] [Bug 416080] Kmymoney: distinction between date of record and date of movement

2020-01-10 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=416080 Thomas Baumgart changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Thomas Baumgart

[kmymoney] [Bug 416080] New: Kmymoney: distinction between date of record and date of movement

2020-01-10 Thread René
https://bugs.kde.org/show_bug.cgi?id=416080 Bug ID: 416080 Summary: Kmymoney: distinction between date of record and date of movement Product: kmymoney Version: 5.0.7 Platform: Fedora RPMs OS: Linux

Re: Glitch on Wayland fedora 31

2020-01-10 Thread Thomas Baumgart
Jack, On Donnerstag, 9. Januar 2020 22:50:13 CET Jack wrote: > On 2019.12.07 04:13, Thomas Baumgart wrote: > > On Samstag, 7. Dezember 2019 06:08:36 CET Jesus Varela wrote: > > > I don't know if anyone here saw this bugzilla reported bug: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=17