On 17/10/16 21:01, Simon McVittie wrote: > On Mon, 17 Oct 2016 at 12:35:21 -0400, Daniel Kahn Gillmor wrote: >> On Mon 2016-10-17 09:27:14 -0400, Ondřej Kuzník wrote: >>> Hmm, for some reason I have two dbus-daemons running and the one started >>> by ck-launch-session is the one where pinentry is having problems. > > What is in their argv? (/proc/*/cmdline) > > Is ck-launch-session something to do with ConsoleKit? If so, it's probably > a bad idea at this point.
Yes, this comes from a time when suspending the system and network-manager operations wouldn't work otherwise since the session wouldn't know how to authenticate me. Apparently that hack is not necessary anymore. > Is there anything interesting in syslog (or equivalently the systemd > Journal)? Recent dbus versions log a lot more there than they used to. > > I hope something here has pointed you in an informative direction. Thanks for the hints, making sure that I don't start the second daemon lets everything use the right one and pinentry comes up immediately. This was then self-inflicted and not a problem in any software involved. Cheers, Ondrej
signature.asc
Description: OpenPGP digital signature
