Dear Maintainer, goldendict-ng (and also goldendict) ignores environment variables
pointing to wayland and starts with xcb.
$ env | grep wayland
CLUTTER_BACKEND=wayland
XDG_SESSION_TYPE=wayland
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/wayland-wm@sway.desktop.service/memory.pressure
WAYLAND_DISPLAY=wayland-1
WINIT_UNIX_BACKEND=wayland
QT_QPA_PLATFORM=wayland
SDL_VIDEODRIVER=wayland
GDK_BACKEND=wayland
When starting with unset DISPLAY (to exclude xwayland):
$ goldendict
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: wayland-egl, wayland, linuxfb, minimal, offscreen, vkkhrdisplay, xcb, eglfs, minimalegl.
Aborted
It only starts natively when explicitly run with an argument:
$ goldendict -platform wayland