Bugzilla

(In reply to Marek Marczykowski-Górecki from comment #29)
> In short, add to `/etc/qubes-rpc/policy/qubes.Gpg` a line like this:

Ok, with that I confirm I no longer prompts.

> Try adding `echo "$@" >> /tmp/gpg-wrapper.log` at the beginning of `/usr/bin/qubes-gpg-client-wrapper`.

With this, I was able to find a difference between my working and non-working scenarios.
It isn't about "strace", but rather it was about the fact that I'm redirecting the output using |&

In the failing scenario (running Thunderbird directly, WITHOUT output redirection), then the command arriving at the qubes-gpg-client-wrapper INCLUDES "--ttyname /dev/pts/1 --ttytype xterm-256color".

Full command when running TB directly:

--enable-special-filenames --batch --no-sk-comments --status-fd 105 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --ttyname /dev/pts/1 --ttytype xterm-256color --logger-fd 107 --decrypt --unwrap --output - -- -&110


In the working scenario, WITH output redirection  (eg: ./thunderbird | grep -vi bla), then the command arriving at the wrapper does not have any tty detail configuration. Full command seen:

--enable-special-filenames --batch --no-sk-comments --status-fd 105 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --logger-fd 107 --decrypt --unwrap --output - -- -&110

In other words: When starting Thunderbird from the terminal prompt (gnome terminal) then the command sent by GPGME includes TTY configuration and that apparently breaks qubes-gpg-client-wrapper. Redirecting output fixes the problem.

(In reply to Marek Marczykowski-Górecki from comment #29)
> In short, add to `/etc/qubes-rpc/policy/qubes.Gpg` a line like this:

Ok, with that I confirm I no longer get prompts.

> Try adding `echo "$@" >> /tmp/gpg-wrapper.log` at the beginning of `/usr/bin/qubes-gpg-client-wrapper`.

With this, I was able to find a difference between my working and non-working scenarios.
It isn't about "strace", but rather it was about the fact that I'm redirecting the output using |&

In the failing scenario (running Thunderbird directly, WITHOUT output redirection), then the command arriving at the qubes-gpg-client-wrapper INCLUDES "--ttyname /dev/pts/1 --ttytype xterm-256color".

Full command when running TB directly:

--enable-special-filenames --batch --no-sk-comments --status-fd 105 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --ttyname /dev/pts/1 --ttytype xterm-256color --logger-fd 107 --decrypt --unwrap --output - -- -&110


In the working scenario, WITH output redirection  (eg: ./thunderbird | grep -vi bla), then the command arriving at the wrapper does not have any tty detail configuration. Full command seen:

--enable-special-filenames --batch --no-sk-comments --status-fd 105 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --logger-fd 107 --decrypt --unwrap --output - -- -&110

In other words: When starting Thunderbird from the terminal prompt (gnome terminal) then the command sent by GPGME includes TTY configuration and that apparently breaks qubes-gpg-client-wrapper. Redirecting output fixes the problem.