Copy from Firefox Wayland fails to be pasted anywhere else

Status changed to 'Confirmed' because the bug affects multiple users.

Note: other people on the internet have reported the same issue:

On AskUbuntu: https://askubuntu.com/questions/1338970/copy-paste-from-firefox-88-0-1-not-working-properly-on-ubuntu-21-04-hirsute-hip

On Reddit: https://www.reddit.com/r/firefox/comments/myhfc5/copy_pasting_occasionally_breaking_on_ubuntu_2104/

Please let me know if you need any more information to further debug this issue.

I confirm this bug is still active on firefox 92.0+build3-0ubuntu0.21.04.1

I think I have occasionally observed this problem, although I wasn't sure which component was at fault. I cannot seem to find an upstream bug tracking this issue, would you mind filing one at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox, and sharing the link to it here? Thanks!

I confirm this bug on firefox 92.0 - ubuntu 21.04

I'm still seeing this bug (not every time, but multiple instances in a day) in Ubuntu 21.10 Wayland, Firefox 94.0.

I am experiencing this problem as well.
Initially when I just start FF I am able to copy from it to other apps, but quite soon (5-15 min) ability to copy text breaks.

Ubuntu 21.04 Wyaland
FF: 94.0+build3-0ubuntu0.21.04.1
XWayland: 2:21.1.1-0ubuntu1

I believe this is the same as this wayland/gtk+-3 bug: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1953694

Indeed, and this appears to be a GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/4340), for which a fix was merged a week ago.

For reference, the upstream firefox bug was https://bugzilla.mozilla.org/show_bug.cgi?id=1722369.

The git change is https://gitlab.gnome.org/GNOME/gtk/-/commit/e23b4dd2

This bug was fixed in the package gtk+3.0 - 3.24.30-3ubuntu2

---------------
gtk+3.0 (3.24.30-3ubuntu2) jammy; urgency=medium

  * debian/patches/git_wayland_clipboard.patch:
    - wayland: Ensure clipboard handling doesn't lock up in certain
      corner cases, fix copy from firefox being unreliable (lp: #1913775)

 -- Sebastien Bacher <email address hidden> Fri, 17 Dec 2021 16:09:39 +0100

Will there be a port of this fix to impish?

I would also like to request a port of this fix to impish and hirsute.

I've currently worked around this by upgrading gtk+3.0 in a probably slightly unorthodox way, but I'd much prefer if the package was offered through the official Ubuntu impish repository.

Unlikely to happen for hirsute, which will be EOL on January 20.
Tagging for consideration in impish.

untagging, I'm handling the SRU now

Hello Stefano, or anyone else affected,

Accepted gtk+3.0 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.30-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Excellent news.

I've previously installed:

libgtk-3-common/now 3.24.30-3ubuntu2

and its dependencies from jammy and I've not seen the problem re-appear for a while. Is this the exact same software? In that case I'd vouch for the bug being solved.

That said, I'd feel more comfortable installing from the impish-proposed repo, but I'm a little confused about how to, even with the guide. I've activated impish-proposed, added the preferences file, but I'm unsure what I should put or search for as the package name, so I put * which I assume stands for "all". Using aptitude, however, I couldn't find a package called "gtk+3.0". Should I just take libgtk-3-0_3.24.30-1ubuntu1.1_i386.deb?

And will this install nicely over my (newer?) 3.24.30-3ubuntu2?

bluppfisk, if you have installed the jammy packages on impish, enabling impish-proposed won't offer the update because the version is greater in jammy.

You will need to specify the version number to downgrade to the impish proposed update:

  sudo apt install libgtk-3-common=3.24.30-1ubuntu1.1 \
    libgtk-3-0=3.24.30-1ubuntu1.1 libgtk-3-bin=3.24.30-1ubuntu1.1 \
    gtk-update-icon-cache=3.24.30-1ubuntu1.1 gir1.2-gtk-3.0=3.24.30-1ubuntu1.1

Thanks. I also just wanted to be sure that I was installing the right packages. May I ask, how did you know that these are the ones you need to apt install?

I'm confused because the official package is called gtk+3.0 but when I use apt I need to specify all of those? Those are also fewer packages than listed in on the Launchpad page's "binaries built by this package".

Anyway I've now successfully installed the packages above. This doesn't require a reboot, does it?

Those are the packages that are typically installed by default for this specific source package. It is possible that you have installed additional binary packages (such as libgtk-3-dev or libgtk-3-doc), in which case you would need to manually downgrade those, too.

The source package is called gtk+3.0, and a number of binary packages are built out of this source package. What you install on your machine are binary packages, but Launchpad handles source packages.
If you need to know the source package for a given binary package, you can use e.g.:

    apt show libgtk-3-bin | grep Source:

This specific update won't require a reboot, but I'm not sure whether it requires restarting the current wayland session, or if the fix will be picked up by individual client applications.
@seb128 maybe that could be clarified in the test case?

We haven't got new reports since the fix landed nor visible regression so let's say the fix is working as intended.

All autopkgtests for the newly accepted gtk+3.0 (3.24.30-1ubuntu1.1) for impish have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.11-0ubuntu71 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/impish/update_excuses.html#gtk+3.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package gtk+3.0 - 3.24.30-1ubuntu1.1

---------------
gtk+3.0 (3.24.30-1ubuntu1.1) impish; urgency=medium

  * debian/patches/git_wayland_clipboard.patch:
    - wayland: Ensure clipboard handling doesn't lock up in certain
      corner cases, fix copy from firefox being unreliable (lp: #1913775)

 -- Sebastien Bacher <email address hidden> Wed, 12 Jan 2022 12:44:47 +0100

Yeah, ok.