Bug 353173 - URL only copied on second attempt when synchronize clipboard enabled
Summary: URL only copied on second attempt when synchronize clipboard enabled
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard widget & pop-up (other bugs)
Version First Reported In: 5.15.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-25 12:47 UTC by Robin Green
Modified: 2023-08-10 20:13 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Green 2015-09-25 12:47:57 UTC
When I select an URL in Chrome and press Ctrl+C, it is not copied the first time if synchronize clipboard is enabled in klipper. I have to reopen the tab if I close it, reselect it, and press CTRL+C twice.

Reproducible: Always

Steps to Reproduce:
1. Select URL in URL bar in Chrome
2. Press Ctrl+C
3. Go to a textarea in another tab in Chrome
4. Press Ctrl+V

Actual Results:  
Nothing is pasted.

Expected Results:  
Originally-selected URL should be pasted.
Comment 1 Niklas Laxström 2015-11-20 13:29:37 UTC
This bug is possibly related to 348169.

For me, often (but not always!) no matter how many times I try Ctrl+C the URL form address bar it just doesn't appear in the klipper history. But there seems to be an "empty" entry in the history.
Pasting works fine when there is the empty entry (most of the time anyway, sometimes it pastes an old text like if I didn't copy anything), but these empty entries have tendency to disappear from the history so you will need to go hunt for the tab again to copy the URL again.
Comment 2 Rex Dieter 2015-11-20 19:29:30 UTC
chrome does screwy things with their URL and selections anyway, see also:
https://code.google.com/p/chromium/issues/detail?id=424111
Comment 3 Noah Davis 2023-08-10 20:13:19 UTC
This bug is for 5.2.2, not 5.15.3. This appears to be fixed, so I'm marking it as such.