On 2026-03-06 Vincent Lefevre <[email protected]> wrote: > Control: retitle -1 pinentry-qt: immediate exit with a core dump if $DISPLAY > is unset or set but unavailable
> On 2026-03-06 13:41:14 +0100, Andreas Metzler wrote: > > Control: retitle -1 pinentry-qt: immediate exit if $DISPLAY set but > > unavailable > Note that this is more than a "normal" exit: it generates > a core dump. > > this works as expected (fallback to tty) if DISPLAY is unset > On my machine, it does *not* fall back to tty (contrary to > pinentry-fltk in this case): > qaa:~> unset DISPLAY > qaa:~> pinentry-qt > qt.qpa.xcb: could not connect to display > qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load > the Qt xcb platform plugin. > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though > it was found. > This application failed to start because no Qt platform plugin could be > initialized. Reinstalling the application may fix this problem. > Available platform plugins are: xcb, wayland, linuxfb, offscreen, minimal, > vkkhrdisplay, vnc, wayland-egl, eglfs, minimalegl. > zsh: IOT instruction (core dumped) pinentry-qt That seems to be a zsh issue: https://www.zsh.org/mla/workers/2023/msg00330.html it mixes up clean exit with SIGABRT and crashing. I do get the fallback for env -u DISPLAY pinentry-qt and invalid display "abort"s metzler@argenau:~$ env DISPLAY=invalid pinentry-qt qt.qpa.xcb: could not connect to display invalid qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, wayland, offscreen, linuxfb, wayland-egl, vnc, minimalegl, minimal, xcb, vkkhrdisplay. Aborted env DISPLAY=invalid pinentry-qt [...] > Perhaps some additional package is needed for this to work, which > would mean a missing dependency. > But I don't understand the error messages: > qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load > the Qt xcb platform plugin. > The libxcb-cursor0 package is installed on my machine. In there a > reason for the above message? > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though > it was found. > Note: I do not use any desktop environment, just plain X11 with > FVWM2 as my window manager. I think that is just a generic error message, communicating an at some point frequent cause for entering this code-path. [...] I will update the upstream bug report with your information. - Thanks! cu Andreas -- "You people are noisy," Nia said. I made the gesture of agreement.
