Re: [Evolution] Can't get credentials from gnome-keyring when using x2go or vnc

[D Ducky <suffsuccotash gmail com>]

Sorry for the multiple emails.

Even though disabling pcscd stops the prompts, evolution produces the same error.

When I open seahorse, it does not see default keyring,  It does when logged in locally, but not through x2go or vnc.

Is this a seahorse issue?

On 10/1/19 2:27 PM, D Ducky wrote:

Sorry, more this:

https://bugzilla.redhat.com/show_bug.cgi?id=1478345

However, it never accesses the default keyring so that evolution can get the creds.

On 10/1/19 2:05 PM, D Ducky wrote:

Maybe similar to this?

https://github.com/TurboVNC/turbovnc/issues/52

Maybe it's not an evolution issue at all, I just know evolution is not getting the default keys.

On 10/1/19 1:39 PM, D Ducky wrote:

Hello,

So when I log in locally, I get a prompt saying "password for default keyring." I put my password, and then everything is OK and evolution is fine.

When I log in remotely, I get a prompt from pc/scd daemon, asking for the same password, but once I put it and open evolution, nothing happens.

I DO use a CAC card, but it's not in the reader and has nothing to do with this.

--

If I open seahorse locally, it shows passwords, and under that, login and default keyring. I think default keyring is the one I'm talking about.

When I open seahorse from x2go or vnc, it again prompts me for pc/scd password(which is gnome-keyring password), and then it doesn't have a password listing. It just shows certificates, pgp keys and secure shell.

On Tue, 2019-10-01 at 08:37 +0200, Milan Crha via evolution-list wrote:

On Mon, 2019-09-30 at 20:49 -0500, D Ducky via evolution-list wrote:

I have noticed now with Fedora 30, that if I access my desktop

through x2go or VNC, I cannot use evolution properly because it does

not connect to gnome-keyring-daemon.  It's still running, but it's

not trying to connect or something.

	Hi,

I think we met on IRC few days ago. I still do not have any answer on

this. The thing is that evolution (eventually evolution-source-registry 

process) talks to gnome-keyring-daemon through libsecret, which uses

D-Bus (if I'm not mistaken). If you can run seahorse, then there might

not be any issue to run also evolution. I doubt evolution talks to some

isolated/stale evolution-source-registry process.

I do not know how to debug what is going on in the background, I'm

sorry. I'd probably start with libsecret debugging, if there's any

such. Maybe someone else here has an idea and/or an experience either

with x2go or VNC.

	Bye,

	Milan

_______________________________________________

evolution-list mailing list

evolution-list gnome org

To change your list options or unsubscribe, visit ...

https://mail.gnome.org/mailman/listinfo/evolution-list