Open bedge opened 2 weeks ago
Tried the setup.exe install with the same result.
Tailed the log to see what was happening after enabling logging using https://copyq.readthedocs.io/en/latest/faq.html#how-to-enable-logging
& 'C:\Program Files\CopyQ\copyq.exe' exit
$env:COPYQ_LOG_LEVEL = 'DEBUG'
$env:COPYQ_LOG_FILE = [Environment]::GetFolderPath("MyDocuments") + '\copyq.log'
echo "Logs will be written to $env:COPYQ_LOG_FILE"
& 'C:\Program Files\CopyQ\copyq.exe
When running:
& 'C:\Program Files\CopyQ\copyq.exe' exit
The log showed:
CopyQ DEBUG [2024-06-14 06:53:22.640] <Client-12772>: Waiting for server to start
CopyQ ERROR [2024-06-14 06:53:23.646] <Client-12772>: Cannot connect to server! Start CopyQ server first.
Yet, when trying to start it using just:
& 'C:\Program Files\CopyQ\copyq.exe'
The log shows:
CopyQ DEBUG [2024-06-14 06:53:11.009] <Server-32784>: Another process holds lock file: C:/Users/edgeb1/AppData/Roaming/copyq/copyq.lock
OK, finally got a window up using
& 'C:\Program Files\CopyQ\copyq.exe' show
Looking through the config, the "Disable tray" is NOT checked and yet there's no tray presence.
I'm thinking now that that's the main issue - on my installation, there's no visible presence that it's running. That may have been compounded by a stale lock file.
Lastly, there were no keys shortcuts defined in the config. Is this expected?
Another observation is that even when pinning copyq to the status bar, clicking on it does nothing. I would expect this to show the main window. That would have made the hunt for the app's UI unnecessary.
All aside, this appears to be the best available windows clipboard manager!
Describe the bug
Regardless of how it's started, I see no output from
copyq
. Double clicking on the start menu icon, or running copyq from the powershell prompt, there is no output and it appears to terminate immediuately.To Reproduce
Install via Chocolatey:
Expected behavior Some window, message, anything
Screenshots
Version, OS and Environment See install log above
Additional context