Copying to clipboard is broken on Wayland

[mirenradia]

Steps To Reproduce

1. Launch with the flags --enable-features=UseOzonePlatform --ozone-platform=wayland (to enable native Wayland mode)
2. Log in.
3. Open an entry in Bitwarden.
4. Click the button to copy something (e.g. username/password).
5. Inspect system clipboard or attempt to paste copied item.

Expected Result

The item is successfully copied to clipboard.

Actual Result

The item is not copied to the clipboard.

Screenshots or Videos

No response

Additional Context

This was not a problem before I updated to 2023.10.0 (e.g. on 2023.9.3). I have tested the downgrading fixes the problem.

Here is some information about my system:

KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

I am using the RPM package downloaded from the release tab in this repo.

Operating System

Linux

Operating System Version

Fedora Linux 38 (KDE)

Installation method

Other

Build Version

2023.10.0

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[pffont]

Not sure if it's related, but in my case I can copy to clipboard but can't paste using mouse wheel, only with CRLT+V.
I noticed it after upgrade to version 2023.10.1

[mirenradia]

Still broken on 2023.10.1 for me.

[wpost]

For what it's worth, I see the same behavior (items are not copied to the clipboard) using 2023.10.0 and 2023.10.1 even though I'm on X11 (openSUSE 15.3, using AppImage). Like the original reporter, downgrading to 2023.9.3 fixes it for me.

[solopasha]

Works for me after enabling the wayland-data-control feature of the arboard crate. https://github.com/solopasha/bitwarden_flatpak/blob/build-from-source/wayland-clipboard.patch

[almereyda]

@solopasha Could you provide some instructions on how to build a release from your FlatPak, or offer those changes upstream in a Pull Request against flathub/com.bitwarden.desktop?

Apart from that, I can only confirm that downgrading and pinning helped to resolve the clipboard issue.

flatpak remote-info --log flathub com.bitwarden.desktop
sudo flatpak update --commit=d484e7474b902fb30a39acafd054b2027cf6ec4acca65266319e517a9fdce902 com.bitwarden.desktop
sudo flatpak pin com.bitwarden.desktop//d484e7474b902fb30a39acafd054b2027cf6ec4acca65266319e517a9fdce902

When looking at the commit log, it also became visible that there were many changes in the Wayland-related area, which each on their own could explain the regression observed here (https://github.com/flathub/com.bitwarden.desktop/commits/master).

1. 2023-10-20 Flatpak runtime upgrade from 22.08 to 23.08 flathub/com.bitwarden.desktop@0ba81cb
2. 2023-11-02 Bitwarden upgrade to 2023.10.0 flathub/com.bitwarden.desktop@e18bf45
3. 2023-11-07 Bitwarden upgrade to 2023.10.1 flathub/com.bitwarden.desktop@58755ae
4. 2023-12-12 Wayland by default, disable X11 socket, activate fallback-X11 flathub/com.bitwarden.desktop@1eef6b2

Any of these could have gone wrong, and two come with environmental side-effects, especially the Flatpak upgrade. I suspect it is a combination of the recent change of the underlying Flatpak runtime, the change to a new Bitwarden runtime and some configuration issues with the Flatpak sockets.

[ghisvail]

Works for me after enabling the wayland-data-control feature of the arboard crate. https://github.com/solopasha/bitwarden_flatpak/blob/build-from-source/wayland-clipboard.patch

Did you forward the proposed changes upstream?

[solopasha]

Did you forward the proposed changes upstream?

I didn't. Because I don't want to test it on X11 or other platforms.