Your message dated Fri, 01 Mar 2019 14:48:24 -0500
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#923068: pinentry-gtk2 takes more
than twenty seconds to appear
has caused the Debian Bug report #923068,
regarding pinentry-gtk2 takes more than twenty seconds to appear
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
923068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923068
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pinentry-gtk2
Version: 1.1.0-1+b1
Severity: important
When pinentry-gtk2 is started, the input window appears after more than
twenty seconds. For comparison pinentry-gnome3 and pinentry-qt appear in less
than two
seconds for the same request.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pinentry-gtk2 depends on:
ii libassuan0 2.5.2-1
ii libc6 2.28-6
ii libglib2.0-0 2.58.3-1
ii libgpg-error0 1.35-1
ii libgtk2.0-0 2.24.32-3
ii libncursesw6 6.1+20181013-1
ii libsecret-1-0 0.18.7-1
ii libtinfo6 6.1+20181013-1
pinentry-gtk2 recommends no packages.
Versions of packages pinentry-gtk2 suggests:
pn pinentry-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
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
--- End Message ---
