ruza

Same problem on Ubuntu 24.04.5 LTS, Enpass 6.12.6.2258. $ Enpass Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" 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. /usr/local/bin/Enpass: line 6: 5055 Aborted (core dumped) /opt/enpass/Enpass "${1}"

ENVIRONMENT - Enpass enpass-6.12.6.2258-1.x86_64 from the official Enpass yum repository - Fedora Linux 44, running as an AppVM on Qubes OS (X11 session provided by the Qubes GUI agent, no Wayland compositor available), Linux Mint 22 - XDG_SESSION_TYPE=x11, DISPLAY=:0, WAYLAND_DISPLAY unset PROBLEM After upgrading from 6.11 to 6.12.6.2258, Enpass aborts on startup: $ /opt/enpass/Enpass Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" 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. fish: Job 1, './Enpass' terminated by signal SIGABRT (Abort) ROOT CAUSE The 6.12.6 binary is a static Qt build and the only platform integrations compiled in are "wayland" and "wayland-egl". The "xcb" platform plugin is missing, so the application cannot run in any pure X11 session. Because the build is static, the plugin cannot be supplied externally via QT_PLUGIN_PATH either. $ QT_DEBUG_PLUGINS=1 /opt/enpass/Enpass 2>&1 | grep -iE 'platform|xcb|wayland' qt.core.plugin.factoryloader: ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. Available platform plugins are: wayland-egl, wayland. $ rpm -ql enpass | grep -iE 'platform|xcb|wayland' (no output, the package contains no platform plugin files) $ rpm -V enpass (no output, package files are intact) $ ls /opt/enpass Enpass crashpad_handler importer_enpass qt.conf wifisyncserver_bin ldd /opt/enpass/Enpass shows libxcb.so.1, libxcb-render.so.0 and libxcb-shm.so.0 linked, but no xcb QPA integration is registered. STEPS TO REPRODUCE 1. Install enpass-6.12.6.2258-1.x86_64 from the official repository on Fedora 44. 2. Log in to an X11 session (or any environment without a Wayland compositor, e.g. a Qubes OS AppVM). 3. Run /opt/enpass/Enpass. EXPECTED BEHAVIOUR Enpass starts on X11 as version 6.11 did. The same reproduction with 6.11 works without any changes. IMPACT Enpass is unusable on every X11-only setup, including all Qubes OS AppVMs, Xfce/Cinnamon/MATE X11 sessions and remote X11 sessions. Other users report the same regression, e.g. https://forums.linuxmint.com/viewtopic.php?t=474153 (resolved there only by switching to a Wayland session, which is not possible on Qubes OS). CURRENT WORKAROUND Downgraded to 6.11 in the template and pinned the version with dnf versionlock. REQUEST Please include the xcb platform integration in the static Linux build again (or ship Qt dynamically with both xcb and wayland plugins), so that Enpass keeps working on X11. If dropping X11 support is intentional, please state it in the release notes and keep 6.11 available in the repository.

Thanks for the response. Does this mean inter-extension communication is blocked in the browser by design and it's impossible to use some inter-extension messaging mechanism?

I dont think it has any relations to the specific versions. Much more likely is a general problem. Fedora Linux 40: Brave browser - Version 1.67.123 Chromium: 126.0.6478.126 (Official Build) (64-bit) + Alby 3.9.0 Windows 11: Brave browser - Version 1.68.131 Chromium: 127.0.6533.73 (Official Build) (64-bit) + Alby 3.9.0 URL is the internal browser URL for the Alby extension which is chrome-extension://iokeahhehimjnekafflcihljlcjccdbe

Is there a way how to fill password into a browser extension like Alby? Webform doesn't seemed to be supported. Having an Enpass record with URL=chrome-extension://iokeahhehimjnekafflcihljlcjccdbe doesn't sememd to work.