Issue metadata
Sign in to add a comment
|
Highlight in Chrome does not modify X selection buffer |
||||||||||||||||||||
Issue description
Chrome Version : Version 54.0.2816.0 beta (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox: OK 47.0
IE:
What steps will reproduce the problem?
(1) Start Chrome on Linux. I'm using XMonad as a window manager (NO gnome, not running a clipboard manager, etc.)
(2) highlight some text
(3) try to middle-click paste somewhere (terminal, editor, whatever)
What is the expected result?
The X selection buffer was modified when I highlighted and the text that I highlighted is pasted somewhere.
What happens instead?
The selection buffer is not modified and whatever was in the buffer previously is pasted when I do middle-click. If I explicitly copy, then things are OK.
Please provide any additional information below. Attach a screenshot if
possible.
This is, as far as I can tell, not related to 68886 (that's about pasting *into* chrome, I think). I just restarted to pick up a new version of Chrome, this definitely worked before restarting/upgrading chrome. I'm going to try restarting chrome and see if it fixes it, and if not, I'll try restarting the machine.
,
Aug 10 2016
So highlighting text on a page does not work to modify the selection buffer, but highlighting parts in the address bar *does* still work. Strangely, when I mouse out of the window, the selection changes from blue to grey inside of the page, but from light blue to invisible on the address bar, but I don't think that's related to this issue. I thought I might have some flags set that were causing issues, so I went to about:flags and reset all to default, no luck. Going to try this in gnome.
,
Aug 10 2016
Using Cinnamon (not gnome, sorry about the confusion!), this still reproduces on this beta version. My icon in Cinnamon was pointing to /usr/bin/google-chrome-stable which was 52.0.2743.116 (64-bit), and everything worked fine there, so I'm relatively confident it was a change in Chrome. Unfortunately I do not know what version I just upgraded from before 54, I suspect it was a 53 version, but don't know how to easily prove that. It'd been a while since I restarted chrome, I imagine it's likely that several versions got installed (via dpkg?) between restarts, so dpkg.log is not going to be super helpful. In case it is, here's the most recent upgrade from dpkg.log: 2016-08-02 17:21:58 upgrade google-chrome-beta:amd64 53.0.2785.34-1 54.0.2816.0-1
,
Aug 10 2016
Downgraded chrome (sudo apt-get install google-chrome-beta=53.0.2785.46-1, since that was the version that was available in my package manager, which is *not* the same version that it supposedly upgraded from!) and it's working again.
,
Aug 10 2016
And I just now found 634148 which this is a duplicate of, going to try to figure out how to mark it as such.. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by spectral@google.com
, Aug 10 2016