Needs wayland support. No longer starts on plasma due to depreciation of xwaylandvideobridge.
Plasma desktops no longer have an x server the apps must use the xwayland libs or wayland native going forward. 6.8 Plasma intends on dropping X support entirely.
This is a stopper feature for me since it kinda don’t work at all.
Hello @lainlives and welcome to the community!
I am running the desktop application in version 2025.12.0 on KDE Plasma 6.5.4 using Wayland without any issues. What exactly does not work on your end?
@lainlives Welcome to the forum!
Thanks for your feature request. But based on what @marlin wrote, it seems that it is already implemented.
Therefore, I’m going to close this feature request – but with a delay for further clarification, if necessary or possible.
Could you clarify the behavior? Which package and version are you using? The desktop client defaults to Wayland with an X11 fallback.
Cannot launch it. Fails to find an X session.
If it’s supposed to default to Wayland then there appears to be a bug.
[2:0113/224650.608733:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:250] Missing X server or $DISPLAY
[2:0113/224650.608772:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
com.bitwarden.desktop 2025.12.0
Operating System: Fedora Linux 42
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.22.0
Qt Version: 6.9.3
Kernel Version: 6.17.12-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: ASUS
Does it help to set ELECTRON_OZONE_PLATFORM_HINT=waylandas proposed in another comment?
It seems to be working not noticing any obvious issues. I will add it to bitwardens flatpak env.
Is this a bug? Should I report this as a bug?
Since this is an issue with Electron rather than Bitwarden, I do not think reporting it as a bug would be helpful.