Page MenuHome GnuPG

pinentry-gnome3 no longer functions in Wayland
Closed, ResolvedPublic

Description

After a recent system update Pinentry no longer displays on Wayland based systems.

pinentry-gnome3 -d <<EOT
SETDESC hello
GETPIN
EOT
No Gcr System Prompter available, falling back to curses
OK Pleased to meet you
OK
S ERROR gnome3.isatty 83918950
ERR 83918950 Inappropriate ioctl for device <Pinentry>

I have tried setting DISPLAY, setting WAYLAND_DISPLAY and I see the same response

Details

Version
1.1.1-1

Related Objects

Event Timeline

bagnaram created this object in space S1 Public.
werner triaged this task as Normal priority.Mon, Apr 26, 2:17 PM
werner added a subscriber: werner.

Please install the Gnome Key Ring prompter tool or use the plain GTK pinentry.

I have installed the Gnome keyring prompter and there seems to be a problem using the Wayland display

Apr 27 17:33:09 mbagnara-pc org.gnome.keyring.SystemPrompter[1952]: Unable to init server: Could not connect: Connection refused
Apr 27 17:33:09 mbagnara-pc gcr-prompter[1952]: cannot open display:

Also have tried pinentry-qt and pinentry-gtk-2 as a fallback to eliminate outside issues with gcr-prompter

$ ~ pinentry-qt -d <<EOT
SETDESC hello
GETPIN
EOT
OK Pleased to meet you
OK
S ERROR qt.isatty 83918950
ERR 83918950 Inappropriate ioctl for device <Pinentry>
$ ~ pinentry-gtk-2 -d <<EOT
SETDESC hello
GETPIN
EOT
OK Pleased to meet you
OK
S ERROR gtk2.isatty 83918950
ERR 83918950 Inappropriate ioctl for device <Pinentry>

FYI, for me, on a machine with Debian GNU/Linux, I use Sway, it works fine with pinentry-gnome3.

To set DISPLAY, dbus-update-activation-environment is your friend.

Thank you all for the help. I thought this was a bug with pinentry itself but appears to be dbus related based on the above command.

I added the above command to my Sway startup and it now works. Some other system update must have regressed this functionality because I previously didn't need to execute dbus-update-activation-environment