[kmymoney] [Bug 460151] No Report-View installed
https://bugs.kde.org/show_bug.cgi?id=460151 --- Comment #2 from Fabiano Caruana --- Hello Dawid, Thank you for the info. I searched everywhere for "KChart" and that was installed with me. Now I have seen in "kde-ci.yml" that "KDiagram" is in the dependencies. Please excuse me, I'm a newbie and have only been compiling for a few days. Greetings from Riegelsberg Udo -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 460151] No Report-View installed
https://bugs.kde.org/show_bug.cgi?id=460151 --- Comment #3 from Dawid Wróbel --- No worries, it's understandable — I bumped into the same issue myself coupe times. The telegram/IRC channels I mention have developers there as well, so you'll get answers to your questions more quickly. -- You are receiving this mail because: You are the assignee for the bug.
Re: KMyMoney | Use QtKeychain instead KWallet directly (#46)
I don't know why I didn't notice this earlier, but if I don't want to type all my passwords again, are there instructions for how I would go about migrating them? (on Linux, KDE Plasma)
Re: KMyMoney | Use QtKeychain instead KWallet directly (#46)
On Mon, Oct 10, 2022 at 6:16 PM Jack via KMyMoney-devel < kmymoney-devel@kde.org> wrote: > I don't know why I didn't notice this earlier, but if I don't want to > type all my passwords again, are there instructions for how I would go > about migrating them? (on Linux, KDE Plasma) > I imagine you'd have to rename them accordingly. Try saving a new credential using master build (I just merged the code). Then see the differences. The new credential should be saved under a "org.kde.kmymoney" name/folder. Renaming should be relatively easy, if my experience here on macOS with its own native vault is to be of any value. Unfortunately, this cannot be automated from the app level, but we could add a manual page/FAQ on how to do this, possibly with a bash script (via DBus). Which actually begs the question: should we look into how to prepare a "What's new in xxx release"? for when we push an alpha release? -- Best Regards, Dawid Wrobel
Re: KMyMoney | Use QtKeychain instead KWallet directly (#46)
On 10/10/22 12:23, Dawid Wrobel wrote: On Mon, Oct 10, 2022 at 6:16 PM Jack via KMyMoney-devel wrote: I don't know why I didn't notice this earlier, but if I don't want to type all my passwords again, are there instructions for how I would go about migrating them? (on Linux, KDE Plasma) I imagine you'd have to rename them accordingly. Try saving a new credential using master build (I just merged the code). Then see the differences. The new credential should be saved under a "org.kde.kmymoney" name/folder. Renaming should be relatively easy, if my experience here on macOS with its own native vault is to be of any value. Unfortunately, this cannot be automated from the app level, but we could add a manual page/FAQ on how to do this, possibly with a bash script (via DBus). Which actually begs the question: should we look into how to prepare a "What's new in xxx release"? for when we push an alpha release? We definitely need to do something to give users a heads-up. I would be very surprised, and not very happy, if without any warning, an upgrade seemed to lose all my passwords. I don't know how typical I am, but I have over a dozen mapped accounts, and I don't really know any of the passwords - I would have to look up each one in one of the (few) secure places they are stored. Quite possible, but certainly annoying. I would certainly want to know it's going to happen, and know it's for a good reason. Perhaps some pop-up on needing a password telling why it might not be there if it used to be, and at least a pointer to instructions on how to migrate, if possible. Jack
Re: KMyMoney | Use QtKeychain instead KWallet directly (#46)
> Perhaps some pop-up on needing a password telling why it might not be there if it used to be, and at least a pointer to instructions on how to migrate, if possible. The problem is that it would have to show only once, and for all users, as we won't be able to know whether or not they had some passwords saved previously. And if we were already doing a "one time for all" pop up, we might as well make it into a complete "What's new in this major release" and point them to an article/open a manual/page/whatever. -- Dawid
Re: KMyMoney | Use QtKeychain instead KWallet directly (#46)
On 10/10/22 12:34, Dawid Wrobel wrote: > Perhaps some pop-up on needing a password telling why it might not be there if it used to be, and at least a pointer to instructions on how to migrate, if possible. The problem is that it would have to show only once, and for all users, as we won't be able to know whether or not they had some passwords saved previously. And if we were already doing a "one time for all" pop up, we might as well make it into a complete "What's new in this major release" and point them to an article/open a manual/page/whatever. Not everyone reads "WhatsNew" postings, although the information should certainly be included there. What I'm suggesting is a relatively minor wording to be added to the password prompt, which would only be shown in two cases. If the user had (intentionally) not saved the password, they just enter the password and proceed. If they had previously saved it, they can now either enter it again and click the "save" box or else follow the instructions to migrate the passwords, and then not see that popup again.
