- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 14 2022
It seems that we removed the support for the BOM at some point in the past. Probably because config files are anyway suppossed to be utf-8 encoded.
Here is my try:
Dec 13 2022
works
works: the process is canceled without any notification.
works
Fixed by reverting to 2.5.5
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.
Missed some, will post an updated patch.
Dec 12 2022
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.
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.