Open ghisvail opened 9 months ago
I have the same issue with KDE 5.27.9 Wayland on OpenSUSE Tumbleweed.
I downloaded the official Bitwarden AppImage to check, and copying works. So this is a Flatpak-related bug.
@ghisvail thanks for coping this into is own issue. I wasn't sure about it.
Today I updated into the 2023.12.0 v and the error persist.
Also if I try to re arrange the window with super+arrow key
I get a instant crash on the app.
Hi @ghisvail, just to know, if there any plan to solve this? there is anything I can do to help? Thanks
Unfortunately, I am neither a KDE user, nor do I know a KDE expert who can help. If you know someone, feel free to direct him or her here.
Same here. Does not work on Fedora kinoite 38/39 and Nobara 38. It did not work on GNOME some weeks ago, not sure if it does now, because I am using KDE right now, and on KDE it still does not work with Flatpak version.
can confirm this issue persists on fedora 39, KDE 5.27.10 on wayland. copying to clipboard doesn't appear to work for any field across the app (tested username, password, and TOTP).
this appears to be exclusive to the flathub version, so fellow fedora users can lean on the official rpm package listed on their download page (though they do warn this provides no automatic updates, so use at your discretion). the .appimage release also appears to work without issue, unsure about the .deb package.
This issue is still present in Arch KDE Plasma 5.27.10.
My current "workaround" is to run flatpak run com.bitwarden.desktop --ozone-platform=x11
to force it to use xwayland.
If it still tries to use Wayland, you'll need to disable socket=wayland
in the flatpak permissions. I recommend using Flatseal.
This issue is still present in Arch KDE Plasma 5.27.10.
My current "workaround" is to run
flatpak run com.bitwarden.desktop --ozone-platform=x11
to force it to use xwayland. If it still tries to use Wayland, you'll need to disablesocket=wayland
in the flatpak permissions. I recommend using Flatseal.
Thats a good one, do you know if there is any way of runing this with out making it an alias on the console? hahaha
This issue is still present in Arch KDE Plasma 5.27.10. My current "workaround" is to run
flatpak run com.bitwarden.desktop --ozone-platform=x11
to force it to use xwayland. If it still tries to use Wayland, you'll need to disablesocket=wayland
in the flatpak permissions. I recommend using Flatseal.Thats a good one, do you know if there is any way of runing this with out making it an alias on the console? hahaha
Just edit the starter in the KDE Menu Editor (right click on start menu -> Edit Applications) :
I am also running into this issue. When I disable wayland to resolve this the app does not start. What do I need to change in Flatseal to successfully run with the workaround?
[2:0201/151248.372697:ERROR:wayland_connection.cc(193)] Failed to connect to Wayland display: No such file or directory (2)
[2:0201/151248.372727:ERROR:ozone_platform_wayland.cc(259)] Failed to initialize Wayland platform
[2:0201/151248.372730:ERROR:env.cc(255)] The platform failed to initialize. Exiting.
I'm experiencing this issue on Gnome too. Someone created a patch to fix it, it would be nice if it was integrated into the this flatpak version.
https://github.com/solopasha/bitwarden_flatpak/blob/build-from-source/wayland-clipboard.patch
Someone created a patch to fix it, it would be nice if it was integrated into the this flatpak version.
This patch needs to be forwarded and integrated upstream to benefit all distributions.
Looks like there is a PR opened for a proposal for a fix:
As of the 2024.3.0
update https://github.com/flathub/com.bitwarden.desktop/commit/a0f1bd195e4da6df13fa905ebf4e1da8adf5b5cc, copying seems to be working fine. Although Bitwarden now takes a very long time to open.
As of the
2024.3.0
update a0f1bd1, copying seems to be working fine. Although Bitwarden now takes a very long time to open.
Confirmed, seems to be working properly again. I've also noticed it opens a tad bit slower than usual.
Works on KDE Neon running Plasma 6 on Wayland
@galloramiro, could you confirm whether the issue is fixed on your end?
Asking since you were the original reporter of the problem for your own KDE setup.
Hi @ghisvail today seems to be working. But last moth works for some days and then stop working again. I would check this week and if keeps working I would confirm here. Thanks!
Works on KDE 5.27 on Fedora 39
tested with flatpak edition
Working here!
You can close this @ghisvail
Problem
Copy not working
System specs
Current behavior
Expected behavior
Originally posted by @galloramiro in https://github.com/flathub/com.bitwarden.desktop/issues/147#issuecomment-1840881831