Since today, the common practice of Ctrl+C (copy to clipboard) and Ctrl+V (paste from clipboard) does no longer work reliably. Some of the time, I can choose Copy from the Gedit or terminal context menu. But then, pasting only works when using the mouse’s middle click.
I know about the existence of several different X-clipboards, but really would like to restore the default behavior of a single, simple, ‘regular’ clipboard. I am very used to it, that way.
I’m using GNOME 41 as my desktop environment under X11
running kernel 5.15.8-200.fc35 (was pulled in yesterday, but did not fix the issue)
have tried booting both 5.15.7-200.fc35 and 5.15.6-200.fc35; the issue persists
After fresh reboot, Ctrl+C and Ctrl+V work inside a Gedit text window, or even in the Alt+F2 run-dialog.
As soon as I start Visual Studio Code (updated to v1.63.2 yesterday), the copy-and-pasting ceases to function properly. At this moment, I’m only able to copy-and-paste (in both Gedit and Terminal) using mouse-select, right-click-menu, Copy, then middle-click to paste.
I will have a try rebooting and switching Orca off - see if that helps…
UPDATE: the issue appears as soon as (and only when) I start Visual Studio Code. It doesn’t matter whether I enable the Orca screenreader or not. Since yesterday, VSCode gives me this error:
Unable to resolve your shell environment in a reasonable time.
Please review your shell configuration.
Is this perhaps related to my clipboard-issue? I really would like to keep using VSCode as my IDE. What can I do to fix this?
Hi, from where are you install VSCode? My suggestion is try VSCode flatpak version. With flatpak, my understanding, it will used flatpak version of Gnome environment (container). I believe it will prevent incompatibilities with your core system configuration.
I have removed the RPM version of VSCode and installed the Flatpak version, as you suggested.
Yes, the clipboard now works as expected. But the sandbox-environment the IDE runs in is far from ideal.
All my personal settings have to be imported and re-tweaked. VSCode complains about being unable to validate the path to the PHP executable (which is understandable, as it’s running in a container and can’t directly reach the host).
Rather than reinventing the wheel (by getting the Flatpak VSCode running smoothly), I would prefer to actually solve the problem in my ‘regular’ environment.
I remembered something. If you’re on VSCode, usually we can use some short cut key and VSCode will stated something like "waiting for other key”. Please check if cmd+cor cmd+v key combination have a key binding assigned in your VSCode.