The self-test fails with
Could not connect to UiServer: Failed to start uiserver kleopatra
It turns out that this is a regression introduced with rKLEOPATRA87458c2a825d: Make sure helper apps we start are in path. The change assumes that the executable needs to be in PATH, but on Windows the executable is also found next to the calling process.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA61c5cad62ca2 Revert "Make sure helper apps we start are in path" | |||
| rW Gpg4win | |||
| rW1011f269f5da Revert to libassuan 2.5.5. | |||
The actual problem at hand is that the nonce is not correct. The UI-Server is actually started but if a client (or the self-test) connects the connection succeeded but then the server needs to check the nonce which does not match. Procmon shows that there is only one nonce writen - so the problem might be that the server has different copies of the nonce.
We need some more debug output - i.e. a hexdump of the nonce at the point it is checked.
The debug output is
[2560] org.kde.pim.kleopatra: Checking Ui Server connectivity... [2560] UI server not running, starting it [2560] org.kde.pim.kleopatra: UiServer: client connect on fd 1528 [2560] org.kde.pim.kleopatra: UiServer: nonce check failed [2560] org.kde.pim.libkleopatraclientcore: Could not find "kleopatra" in PATH.
which means that libkleopatraclientcore couldn't start kleopatra, but at the same time the UiServer seems to be running? Okay, maybe the lines are in wrong order and the connect doesn't fail because the server isn't running but because of the wrong nonce.
Problem is that Kleopatra uses the latest libassuan from Git and not the released version. Replacing the libassuan DLL with the one from the gnupg directory fixes the bug.