JFTR, the OP was using Mysql, I am using Postgresql.

I use many other Postgresql tools and have code (mine and third-party) that
accesses my databases (including the Gnucash ones) and have never had anything
make a peep about keyrings, only Gnucash.  Google Chrome, although it has
nothing to do with Postgresql, also generates the same kind of keyring prompts
(but I don't use it so I don't care).  I agree there is probably something
messed up on my system regarding the keyring and login, but I don't see that
Postgresql (and analogously Mysql) themselves care.  Which leaves Gnucash and
libdbi as the prime suspects.

Since, to me, the annoyance is less than the time it would probably take
to research/fix it, I will wait until I serendipitously encounter some post
from someone with the same problem who has fixed it.  Or until I upgrade
someday and the problem magically disappears. :-)

On 4/3/19 2:28 AM, Colin Law wrote:
I think Adrien is correct, mysql needs access to the keyring in order
to check user access permissions, though if you logon to the PC
manually, entering your password, then I would not have expected it to
have to ask again, and it certainly should not happen each time you
run gnucash.  I think it is most likely an issue with your system and
mysql though, not a GnuCash issue.

Colin

On Tue, 2 Apr 2019 at 23:08, Stuart McGraw <smcg4...@mtneva.com> wrote:

It opens without the popup.  Which I suppose implies that the keyring checking 
is occurring in gnucash code conditionally for database access, or in whatever 
api gnucash uses for database access (libdbi?), or possibly in 
database-specific api libdbi uses (eg libpq(?) for Postgresql).  I don't think 
it's the latter since I've not noticed anything about it in the libpq docs but 
I could have easily missed something.

On 4/2/19 3:09 PM, Colin Law wrote:
If, as an experiment, you start a new accounts file and save it as
xml, then shutdown and restart gnucash, which should then open the xml
file, do you get the popup?

Colin

On Tue, 2 Apr 2019 at 18:21, Stuart McGraw <smcg4...@mtneva.com> wrote:

No auto-login here and I think the app that needs an option to ignore the 
keyring check entirely is Gnucash (not the database which isn't an app).  As 
for creating a different default keyring, I'll look into that sometime (so 
thanks for the direction to look!) but right now, clicking the Cancel button is 
the easiest way out.  As annoyances go it is nowhere near as bad as those 
caused by Gnome/GTK but that's a subject for a different list. :-)

There are multiple reasons for that pop-up and a solution for each. One 
involves disabling automatic login to the desktop. (if you use it) You can also 
create a different ‘default’ keyring and set it to non-protected. (so it is 
visible to anyone—not wise unless you store nothing in it.) Some apps also let 
you tell them to ignore the keyring check entirely. (Chrome is one such app, 
not sure about MySQL)

Regards,
Adrien

On Mar 31, 2019, at 8:23 PM, Stuart McGraw <smcg4...@mtneva.com> wrote:


I do have a long persisting problem where I am asked every time for a password for my 
keyring (something I've never used, set up, or want) but since clicking 
"Cancel" results in gnucash opening fine I've never bothered to try to fix it.  
(I'm running gnucash on Ubuntu linux.)

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to