Bug 478720 - On a Wayland session, I need to copy text twice for it to be actually copied
Summary: On a Wayland session, I need to copy text twice for it to be actually copied
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.27.10
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2023-12-19 10:22 UTC by Marco
Modified: 2024-01-10 16:52 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco 2023-12-19 10:22:57 UTC
SUMMARY
When on a Wayland session, every attemp to copy some text does not result in the text being stored in the clipboard for later paste. I need to copy the text twice for it to work. The issue is present both using the CTRL+C/CTRL+V shortcuts or the contextual menus


STEPS TO REPRODUCE
1. Start a Wayland session
2. copy some text
3. paste the text

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
Linux/KDE Plasma: Fedora 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
This does not happend with X11. Moreover, I tried increasing the history size to 2 in Klipper, or even disabling Klipper altogether, but nothing changes. The issue seems to be related to the Wayland session. The problem occurs also when copy-pasting text within the same app like KWrite.
Comment 1 Marco 2023-12-19 13:22:35 UTC
P.S., this happens also with other data being copied, such as images. When I try to copy the screenshot made with Spectacle, this does not register unless I copy it again.
Comment 2 Nate Graham 2023-12-21 00:53:28 UTC
> I tried increasing the history size to 2 in Klipper
I gather this means you normally run Klipper with a history size of 1, right? Does that mean you've changed other settings as well? To make sure your settings aren't causing this, can you create a new fresh user account on the same machine and try in that account to see if it still happens?
Comment 3 Bug Janitor Service 2024-01-05 03:46:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Marco 2024-01-06 13:06:52 UTC
To be honest I don't know what was causing the issue. But I recently wiped my system and installed arch with a clean KDE Plasma wayland session, and everything seems to be working fine.
Comment 5 Nate Graham 2024-01-10 16:52:18 UTC
Cool, thanks for the update.