All. Angel's suggestion did nothing, unfortunately: set DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
I run that once connecting with x2go, then run evolution, and evolution cant access any keyring. It failed to retrieve creds from keyring, and doesn't even prompt for keyring password like when I replace GKD. On Fri, Nov 15, 2019 at 10:52 AM Daffy Duck <suffsuccot...@gmail.com> wrote: > Hi, > > locally running that says > unix:path=/run/user/1000/bus > > So should I run > > set DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus > > when I run x2go or vnc? > > On Wed, 2019-11-13 at 23:06 +0100, Ángel wrote: > > Rather than replacing the running gnome-keyring-daemon, try: > > > 1. Connect locally and print the value of $DBUS_SESSION_BUS_ADDRESS > > 2. Connect from x2go and set DBUS_SESSION_BUS_ADDRESS environment > > variable to the value printed at 1. > > > I expect this would make both sessions to use the same dbus and allow > > the second session to talk to the existing keyring, so it would work in > > both cases. > > > > Additionally, it is interesting that the keyring is locked when you log > > in locally, as it normally syncs with your user password and logging in > > automatically unlocks the login based on your account password. > > > Cheers > > _______________________________________________ > > evolution-list mailing list > > evolution-list@gnome.org > > > To change your list options or unsubscribe, visit ... > > https://mail.gnome.org/mailman/listinfo/evolution-list > > >
_______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
