On Fri 2019-03-01 16:54:45 +0100, fulvio ciriaco wrote: > I opened another session from VT with startx and > exec dbus-launch awesome > and the delay reappeared. > > The delay does not reappear with > exec awesome
ok, so it works without "dbus-launch". in the scenario where you are *not* using dbus-launch, what does: systemctl --user status dbus.service show you? if it's "active (running)" then i suspect the issue is that you were running multiple dbus user sessions, and gpg-agent was connected to a different dbus user session than the active gpg process. In general, you want a single dbus user session. so it sounds like simplifying your .xsession is the way to go :) I'm closing this bug report (though you can still comment on it if you've got more followup) because it sounds like the diagnosis is: Deliberately running multiple concurrent dbus user sessions will confuse gpg-agent and gpg. and the resolution is: Do not start up a separate dbus user session! If you find that the removal of dbus-launch from your ~/.xsession is a problem, and not something you can sustain going forward, please re-open this bug report and explain what incompatibilities you're running into, so we can try to figure it out further. thanks all for your testing and diagnosis and feedback here! --dkg
signature.asc
Description: PGP signature