Wayland related problems
Details
Details
Description
Aug 11 2021
Aug 11 2021
• ikloecker added a comment to T3659: pinentry falls back to curses on wayland.
@fvogt I've now added a logging category. Thanks for the suggestion.
Aug 4 2021
Aug 4 2021
fvogt added a comment to T3659: pinentry falls back to curses on wayland.
As far as I understood, $WAYLAND_DISPLAY does not need to be set because there is a well-defined default, but I guess most of the time it's set anyway.
Aug 3 2021
Aug 3 2021
• ikloecker added a comment to T3659: pinentry falls back to curses on wayland.
QGuiApplication checks $XDG_SESSION_TYPE maybe to find out whether to use X11 or Wayland if $DISPLAY and $WAYLAND_DISPLAY are both set.
fvogt added a comment to T3659: pinentry falls back to curses on wayland.
I gave it a try and it works here now with $DISPLAY unset, thanks!
Aug 2 2021
Aug 2 2021
• ikloecker moved T3659: pinentry falls back to curses on wayland from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Should now work for pinentry-qt on Wayland even if DISPLAY is not set.
• ikloecker moved T3659: pinentry falls back to curses on wayland from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jul 26 2021
Jul 26 2021
fvogt added a comment to T3659: pinentry falls back to curses on wayland.
Huh, can't believe I somehow missed that this actually got a reply three years ago...
Aug 26 2020
Aug 26 2020
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
I am always glad to fix such bugs before a release (I am about to prepare 2.2.22).
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
I am always glad to fix such bugs before a release (I am about to prepare 2.2.22).
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
It worked! You were right!
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
Thank you for your prompt help. It's much appreciated.
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
rG4c8d5eb0bdd3: agent: Allow TERM="".
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
I see. Thank you @werner . For clarity could you please link the patch that was not backported to 2.2.?
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
Mails crossed ;-)
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
But @werner what's the value $TERM *supposed* to have? When gpg is invoked straight by Gnome? I can run the command sh -c 'env | grep TERM > ~/gnome-term.env' in Gnome's "Run Command: interface and then the file ~/gnome-term.env says TERM is set to nothing (It is set, but the contents is a "" string).
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
Ah wait. This has been fixed in master a year ago but was not backported to 2.2; see T4137. I'll add it to the forthcoming 2.2.22. Thanks for the report.
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
The warning above is harmless. Both strings are actually the same but stem from different versions of the autotools helper scripts
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
Unfortunately I've had some trouble compiling the latest git version of GnuPG for NixOS - I got this warning which turned out to be a blocker:
• werner added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
Without really looking at your report: May it be that this is because Pinentry does not get the WAYLAND_DISPLAY variable as reported in T5016? This will be fixed in 2.2.22 which I hope to release this week.
Aug 25 2020
Aug 25 2020
doronbehar added a comment to T5036: pinentry won't launch when gpg is invoked by Firefox when Firefox runs with native wayland support in a wayland DE.
I take some of my words back - using or not using MOZ_ENABLE_WAYLAND=1 doesn't make a difference eventually - If Firefox is launched by Gnome and not gnome-terminal, pinentry fails to launch with and without MOZ_ENABLE_WAYLAND.
Apr 17 2018
Apr 17 2018
Then please set DISPLAY ;-)