No tray presence, or output shown on Windows 11, CLI or graphic UI start

[bedge]

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:

PS C:\Users\edgeb1> choco install copyq
Chocolatey v2.3.0
Installing the following packages:
copyq
By installing, you accept licenses for the packages.
Downloading package from source 'https://community.chocolatey.org/api/v2/'
Progress: Downloading copyq 6.4.0... 100%

copyq v6.4.0 [Approved]
copyq package files install completed. Performing other installation steps.
The package copyq wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): a

Automatically start with Windows
Create desktop icon
Installing copyq...
copyq has been installed.
WARNING: No registry key found based on  'copyq'
copyq installed to 'C:\Program Files (x86)\CopyQ'
copyq registered as copyq
  copyq can be automatically uninstalled.
 The install of copyq was successful.
  Deployed to 'C:\Program Files (x86)\CopyQ\'

Chocolatey installed 1/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Expected behavior Some window, message, anything

Screenshots

C:\Users\edgeb1>cd "\Program Files (x86)\CopyQ"

C:\Program Files (x86)\CopyQ>copyq

C:\Program Files (x86)\CopyQ>

Version, OS and Environment See install log above

Edition
Version
Installed on
OS build
Experience
Windows 11 Enterprise
22H2
5/30/2024
22621.3593
Windows Feature Experience Pack 1000.22700.1003.0

Additional context

[bedge]

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

[bedge]

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?

[bedge]

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!