Known Issues
This document lists known commonly occurring issues and possible solutions.
On Windows, CopyQ does not print anything on console
On Windows, you may not see any output when executing CopyQ in a console/terminal application (PowerShell or cmd).
Workarounds:
Use different console application: Git Bash, Cygwin or similar.
Use Action dialog in CopyQ (
F5shortcut) and set “Store standard output” to “text/plain” to save the output as new item in current tab.Append
| Write-Outputto commands in PowerShell:& 'C:\Program Files\CopyQ\copyq.exe' help | Write-Output
See also
On macOS, CopyQ won’t paste after installation/update
CopyQ is not signed app, you need to grant Accessibility again when it’s installed or updated.
To fix this, try following steps:
Go to System Preferences -> Security & Privacy -> Privacy -> Accessibility (or just search for “Allow apps to use Accessibility”).
Click the unlock button.
Select CopyQ from the list and remove it (with the “-” button).
See also
On Linux, global shortcuts, pasting or clipboard monitoring does not work
This can be caused by running CopyQ under a Wayland window manager instead of the X11 server.
Depending on the desktop environment, these features may not be supported:
global shortcuts
clipboard monitoring
pasting from CopyQ and issuing copy command to other apps (that is passing shortcuts to application)
screenshot functionality
querying keyboard modifiers and mouse position
Workaround for most problems is to set QT_QPA_PLATFORM environment variable
and use Xwayland (e.g. xorg-x11-server-Xwayland Fedora package).
For example, launch CopyQ with:
env QT_QPA_PLATFORM=xcb copyq
If CopyQ autostarts, you can change Exec=... line in
~/.config/autostart/copyq.desktop:
Exec=env QT_QPA_PLATFORM=xcb copyq
Note
Mouse selection will still work only if the source application itself supports it.
See also
Wayland Support command reimplements some features on Wayland through external tools (see README for details on how to add the command.