Bug 428521 - Copy/paste does not work sometimes between Clipboard applet and Firefox browser under Wayland session
Summary: Copy/paste does not work sometimes between Clipboard applet and Firefox brows...
Status: RESOLVED DUPLICATE of bug 428075
Alias: None
Product: klipper
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.20.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2020-10-31 16:50 UTC by Ahmed
Modified: 2020-11-13 12:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed 2020-10-31 16:50:38 UTC 
SUMMARY
Clipboard applet does not work properly sometimes under Wayland when I try to paste some text from Clipboard applet, and paste it to Firefox browser, when that happens I have to press "Edit contents" for that text, and copy it again.

STEPS TO REPRODUCE
1. Start Wayland session.
2. Choose any previous text from Clipboard.
3. Copy it to Firefox browser.

OBSERVED RESULT
Pasting that text to Firefox browser does not work, but when I open Kwrite, and paste this text, it works.

EXPECTED RESULT
Copy/paste to work between Clipboard applet, and Firefox browser.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User Edition 5.20.2
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Firefox version: 82.0+build2-0ubuntu0.20.04.1
Comment 1 Ahmed 2020-10-31 16:54:24 UTC 
Also, when I press "Edit contents", and copy the text again, it creates a blank entry at Clipboard applet.
Comment 2 Ahmed 2020-10-31 17:11:23 UTC 
I noticed also that copying text from Firefox to Clipboard sometimes does not work either under Wayland session.
Comment 3 Nate Graham 2020-11-04 19:41:35 UTC 

*** This bug has been marked as a duplicate of bug 424754 ***
Comment 4 Patrick Silva 2020-11-13 12:13:35 UTC 

*** This bug has been marked as a duplicate of bug 428075 ***