Ok, I'm not asked, therefore I set this to done, but not resolved yet, as I'm not sure if the gpg version might have an influence.
Feed Advanced Search
Dec 6 2024
Dec 6 2024
• ebo moved T6894: Kleopatra improved drop behavior from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo added a comment to T7237: Kleopatra: reorder columns for tables in the new tabs in the certificate details.
Gpg4win 4.4:
Contrary to the task description are:
a) In the certifications tab the "tags" column is shown by default
b) in the UID tab, the "origin" column is shown by default (only the "tags" column is hidden)
• ebo closed T7252: Kleopatra: Improvements to columns in the search window, a subtask of T6935: Kleopatra: Key search and refresh related improvements, as Resolved.
• TobiasFella added a comment to T6894: Kleopatra improved drop behavior.
The only difference that you should see in the UI is that there is no longer a menu that pops up when you drop files, asking you what to do with the files. So I guess, if things works fine as you described them, you can consider the ticket done
• ebo closed T7155: Kleopatra: Show additional columns in search results by default, a subtask of T6935: Kleopatra: Key search and refresh related improvements, as Resolved.
• ebo moved T7132: Kleopatra: Trim whitespaces in search from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo added a comment to T6894: Kleopatra improved drop behavior.
This ticket description does not give me anything to test.
tested with Gpg4win 4.4
• ebo closed T6712: Kleopatra: When revoking a local certification do not ask to publish the revocation as Resolved.
tested with Gpg4win 4.4
• ebo edited projects for T6491: Pinentry-Qt: Password prompt for each subkey if password change is cancelled, added: gpd5x; removed Restricted Project.
This issue looks still the same from the user perspective as in the task description with Gpg4win 4.4. Therefore tagging it for gpd5x
Dec 5 2024
Dec 5 2024
• werner moved T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds from Backlog to QA on the gpd5x board.
• ebo closed T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog as Resolved.
Better a new ticket for the rest, see T7441
• ebo triaged T7441: Kleopatra: misleading representation of key with multiple uids while searching in the encrypt dialog as Normal priority.
• ebo moved T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog from Backlog to WiP on the vsd33 board.
• ebo edited projects for T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog, added: vsd33; removed vsd.
Dec 4 2024
Dec 4 2024
Works for me in an NSIS installer. The VSD beta thing also works with copied conf files.
(gpg4win-5.0.0-beta27 with some local mods)
• ikloecker closed T5944: Kleopatra: Recipient input is confused about secondary user IDs as Resolved.
This doesn't happen anymore now that we offer all valid user IDs and not just the primary user IDs.
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
I have created two subtasks for the two changes we could make in Kleopatra to avoid the gpg-agent startup race.
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Neither gpg nor gpgsm start gpg-agent if the keyring is empty. That's why Andre made Kleo start gpg-agent explicitly so that people could get going with an empty keyring after inserting their (PKCS#15) smartcard.
• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Kleo needs this only because it wants to directly talk to gpg-agent via Assuan. For example to get smartcard infos. What about delaying this part until you have received some data back from gpg or gpgsm? This makes sure that the agent has been started.
Dec 3 2024
Dec 3 2024
• ikloecker added a comment to T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog.
Looks like there's something not correct in the completion model. Or we use different criteria for showing the blue "i" (as "information") which doesn't make it better. Reopen?
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Yes, that's what happens. I did an experiment with waiting for gpgconf --launch gpg-agent to succeed, but the timeout of 5 seconds I used was too low and I didn't feel like increasing the timeout. Instead now we run gpgconf --launch gpg-agent detached.
• werner added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
Let me guess: Kleopatra starts the agent using gpgconf --launch gpg-agent which in turn uses gpg-connect-agent to actually start the agent if needed. Kleopatra does not seem to wait for the launch to succeed and fires up gpg and gpgsm. They both wait for the gpg-agent to be started and both use the same locking strategy. However, this involves a pseudo random wait which should avoid deadlocks. See gnupg/common/dotlock.c:next_wait_interval
• ikloecker moved T6663: Kleopatra: change option "publish on keyserver" from Backlog to WIP on the gpd5x board.
• ikloecker changed the status of T6663: Kleopatra: change option "publish on keyserver" from Open to Testing.
This is long done, but only for Qt 6-based releases. Andre's comment T6663#175481 has also been addressed.
• ikloecker changed the status of T6663: Kleopatra: change option "publish on keyserver", a subtask of T6626: Kleopatra: Improve certification and revocation, from Open to Testing.
• ikloecker moved T6627: Kleopatra: Add checkbox in certifications dialog from Backlog to WIP on the gpd5x board.
• ikloecker changed the status of T6627: Kleopatra: Add checkbox in certifications dialog, a subtask of T6626: Kleopatra: Improve certification and revocation, from Open to Testing.
• ikloecker changed the status of T6627: Kleopatra: Add checkbox in certifications dialog from Open to Testing.
This is long done, but only for Qt 6-based releases.
• ikloecker removed a project from T6553: Kleopatra: Expiry date issues and improvements: Restricted Project.
• ebo added a comment to T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog.
Tested Gpg4win 4.4:
Interesting, when you search for the UID, it looks as before, with the green check mark:
• ikloecker moved T7435: Kleopatra: Show Details does not work for certificates selected as Encrypt for others from Backlog to WiP on the vsd33 board.
Backported for VSD 3.3 / Gpg4win 4.4.1.
• ikloecker changed the status of T7435: Kleopatra: Show Details does not work for certificates selected as Encrypt for others from Open to Testing.
I'll backport this for VSD 3.3 / Gpg4win 4.4.1. Regression risk is minimal.
• ikloecker changed the status of T6409: Kleopatra: misleading representation of key with multiple uids in sign/encrypt dialog from Open to Testing.
I think this is resolved. In the Sign/Encrypt dialog we now offer the individual user IDs instead of the certificates, i.e. the two user IDs of the Udo certificate are both offered and one should be listed as certified and the other one as not certified (if one is certified and the other one isn't; for me both user IDs are ultimately trusted).
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
I'm wondering what happened (or why nothing happened) between the exit of gpg-agent[2816] at 10:11:12 and the start of gpg-agent[6492] at 10:12:00.
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
scdaemon logged this:
2024-12-03 10:12:02 scdaemon[6272] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.scdaemon' gehört 2024-12-03 10:12:02 scdaemon[6272] Handhabungsroutine für fd -1 gestartet 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK GNU Privacy Guard's Smartcard server ready, process 6272 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- GETINFO socket_name 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> D C:\Users\g10code\AppData\Local\gnupg\S.scdaemon 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- OPTION event-signal=28c 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 <- KEYINFO --list 2024-12-03 10:12:02 scdaemon[6272] DBG: chan_0x000002f8 -> OK [...]
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
gpgsm logged this:
2024-12-03 10:11:08 gpgsm[3940] enabled debug flags: ipc 2024-12-03 10:11:08 gpgsm[3940] enabled compatibility flags: 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # Home: C:\Users\g10code\AppData\Roaming\gnupg 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # Config: C:/Users/g10code/AppData/Roaming/gnupg/gpgsm.conf 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> # DirmngrInfo: C:\Users\g10code\AppData\Local\gnupg\S.dirmngr 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK GNU Privacy Guard's S/M server 2.4.7 ready, process 3940 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION ttyname=/dev/tty 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION enable-audit-log=1 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION allow-pinentry-notify 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION list-mode=1 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION with-validation=1 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION with-secret=1 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- OPTION offline=1 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 -> OK 2024-12-03 10:11:08 gpgsm[3940] DBG: chan_0x000001a0 <- LISTKEYS 2024-12-03 10:11:10 gpgsm[3940] Kein aktiver gpg-agent - `C:\\Program Files (x86)\\GnuPG\\bin\\gpg-agent.exe' wird gestartet 2024-12-03 10:11:10 gpgsm[3940] DBG: chan_0x000001a0 -> S PROGRESS starting_agent ? 0 0 2024-12-03 10:11:11 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:13 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:15 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:16 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:19 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:20 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:22 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:24 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:26 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:27 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:30 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:31 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:33 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:35 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:37 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:38 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:41 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:42 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:44 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:45 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:48 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:49 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:52 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:53 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:55 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:57 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:59 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:12:00 gpgsm[3940] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK Pleased to meet you, process 6492 2024-12-03 10:12:03 gpgsm[3940] DBG: connection to the gpg-agent established 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> RESET 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION ttyname=/dev/tty 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> GETINFO version 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- D 2.4.7 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> OPTION allow-pinentry-notify 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> HAVEKEY 46B01CFBE21A10B2CFF41ABBD1D6A03E3F364121 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- ERR 67108881 Kein geheimer Schlüssel <GPG Agent> 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> ISTRUSTED 22FF41AB501FD708D10B0931E6F72A5C64DCF10E 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- S TRUSTLISTFLAG relax 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- OK 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 -> KEYINFO 46B01CFBE21A10B2CFF41ABBD1D6A03E3F364121 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x00000294 <- ERR 67108891 Nicht gefunden <GPG Agent> [...] 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x000001a0 <- BYE 2024-12-03 10:12:03 gpgsm[3940] DBG: chan_0x000001a0 -> OK closing connection 2024-12-03 10:12:03 gpgsm[3940] secmem usage: 0/16384 bytes in 0 blocks
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
gpg logged this:
2024-12-03 10:11:08 gpg[3936] enabled debug flags: ipc 2024-12-03 10:11:08 gpg[3936] enabled compatibility flags: 2024-12-03 10:11:08 gpg[3936] verwende Vertrauensmodell pgp 2024-12-03 10:11:10 gpg[3936] Kein aktiver gpg-agent - `C:\\Program Files (x86)\\GnuPG\\bin\\gpg-agent.exe' wird gestartet 2024-12-03 10:11:11 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:13 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:15 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:16 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:19 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:20 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:22 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:23 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:26 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:27 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:30 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:31 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:33 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:34 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:37 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:38 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:41 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:42 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:44 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:45 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:48 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:49 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:52 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:53 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:55 gpg[3936] waiting for lock C:\\Users\\g10code\\AppData\\Roaming\\gnupg\\gnupg_spawn_agent_sentinel.lock... 2024-12-03 10:11:58 gpg[3936] Warte bis der gpg-agent bereit ist ... (8s) 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK Pleased to meet you, process 6492 2024-12-03 10:12:02 gpg[3936] Verbindung zum gpg-agent aufgebaut 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> RESET 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION ttyname=/dev/tty 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> GETINFO version 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- D 2.4.7 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION allow-pinentry-notify 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> OPTION agent-awareness=2.1.0 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> HAVEKEY --list=1000 2024-12-03 10:12:02 gpg[3936] DBG: chan_0000027c <- [ 44 20 07 af f5 9c 99 cf cd 72 e0 c7 a6 af 8f 94 ...(942 byte(s) skipped) ] 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c -> KEYINFO 950A511AA08C9A16C9FA3DD1AA8C1E4BF43E0B0F 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- S KEYINFO 950A511AA08C9A16C9FA3DD1AA8C1E4BF43E0B0F D - - - P - - - 2024-12-03 10:12:02 gpg[3936] DBG: chan_0x0000027c <- OK [...] 2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c -> KEYINFO 58C8BB90D9D8565156786B1F17C4C6E404237F3A 2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c <- S KEYINFO 58C8BB90D9D8565156786B1F17C4C6E404237F3A D - - - C - - - 2024-12-03 10:12:03 gpg[3936] DBG: chan_0x0000027c <- OK 2024-12-03 10:12:03 gpg[3936] secmem usage: 0/32768 bytes in 0 blocks
• ikloecker added a comment to T7434: Kleopatra: Initial keylisting hangs for ~60 seconds (gpg-agent: Socket ...S.gpg-agent cannot be bound).
gpg-agent.log starts with
2024-12-03 10:11:12 gpg-agent[2816] Der Socket kann nicht an `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gebunden werden: Unknown error 2024-12-03 10:11:12 gpg-agent[2816] secmem usage: 0/32768 bytes in 0 blocks
Looks like gpg-agent tried to bind the socket and immediately exited when this failed. The logs of gpg-agent continue 48 seconds later with
2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gehört 2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.extra' gehört 2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.browser' gehört 2024-12-03 10:12:00 gpg-agent[6492] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.ssh' gehört 2024-12-03 10:12:00 gpg-agent[6492] gpg-agent (GnuPG) 2.4.7 started 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- RESET 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION ttyname=/dev/tty 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION putenv=QT_QPA_PLATFORM=windows:darkmode=2 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- GETINFO version 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> D 2.4.7 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION allow-pinentry-notify 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- OPTION agent-awareness=2.1.0 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 -> OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x00000084 <- HAVEKEY --list=1000 2024-12-03 10:12:02 gpg-agent[6492] no running C:\\Program Files (x86)\\GnuPG\\bin\\scdaemon.exe daemon - starting it 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- OK GNU Privacy Guard's Smartcard server ready, process 6272 2024-12-03 10:12:02 gpg-agent[6492] first connection to daemon C:\\Program Files (x86)\\GnuPG\\bin\\scdaemon.exe established 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 -> GETINFO socket_name 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- D C:\Users\g10code\AppData\Local\gnupg\S.scdaemon 2024-12-03 10:12:02 gpg-agent[6492] DBG: chan_0x000002a4 <- OK 2024-12-03 10:12:02 gpg-agent[6492] DBG: additional connections at 'C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.scdaemon'
• ebo added a project to T7405: Kleopatra: Highlight if no valid encryption subkey exists: Feature Request.
Closing this as duplicate of T7405. That ticket has the better task description as it was made after discussing offline how it could best be done.
• ebo removed a project from T5950: Allow viewing expired certificates more easily: Restricted Project.
closing this as duplicate for the improvement part, the support part is solved, anyway.
• ikloecker added a comment to T7405: Kleopatra: Highlight if no valid encryption subkey exists.
T6109 is also closely related and I think it would be addressed by this ticket.
• ikloecker added a comment to T7405: Kleopatra: Highlight if no valid encryption subkey exists.
• ikloecker moved T5780: Kleopatra: Result dialog does not have focus after operation from Backlog to WiP on the vsd33 board.
Backported for VSD 3.3.x / Gpg4win 4.4.1
• ikloecker added a project to T5780: Kleopatra: Result dialog does not have focus after operation: vsd33.
I'll backport this because this issue is a really bad usability problem for people using the Windows Explorer integration to decrypt files. And the regression risk is minimal.
• ikloecker changed the status of T5780: Kleopatra: Result dialog does not have focus after operation from Open to Testing.
For me the change fixes the problem on Windows. (I haven't checked if there was a problem on Linux/X11, but I have verified that the change also works on Linux/X11.)
• ebo moved T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo edited projects for T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive, added: vsd33, Restricted Project; removed gpd5x.
I think you are right, it is fixed. I tried it now again with Gpg4win 4.4 with several cards and it works as you describe.
Dec 2 2024
Dec 2 2024
• ikloecker added a comment to T5780: Kleopatra: Result dialog does not have focus after operation.
This also happens if one activates the Kleopatra main window, then activates the Windows Explorer and then starts a decrypt&verify operation.
• ikloecker added a comment to T5780: Kleopatra: Result dialog does not have focus after operation.
I have seen this when doing the following:
- Start Kleopatra and minimize its window
- Start decrypt&verify operation for an encrypted archive in Windows Explorer with GpgEX
• ikloecker closed T5839: GNUPGEX Explorer File Encryption Tar Archive long Filename Bug as Resolved.
Gpg4win 4.4.0 has just been released. Creation of encrypted archives has been completely reworked with Gpg4win 4.3.0 already. I could create an encrypted archive containing the two files with GpgEX without problems.
• ikloecker removed a project from T5824: Kleopatra: Full accessibility support: Restricted Project.
• ikloecker added a comment to T7413: Kleopatra: Smartcard action buttons in case of p15 cards are sometimes not responsive.
I tried to reproduce this with Gpg4win 4.4.0, but it worked for all PKCS#15 cards I tried (dark blue R&S, Genua, ipt.fraunhofer). As soon as the certificates were imported from the card (and a "Do you trust this root certificate" dialog was canceled) the buttons became enabled.
Gpg4win 4.4.0 has just been released. I cannot reproduce unexpected results when doing a lookup on server. Unfortunately, many keyservers do not publish the user IDs (i.e. name and/or email address) anymore. Kleopatra does not list results without user IDs because GnuPG won't import them anyway.
This has been fixed in the meantime. If you should still experience this problem with Gpg4win 4.4.0 then reopen this ticket.
• ebo moved T6984: Kleopatra: Add icon for folder encryption from QA to vsd-3.3.0 on the vsd33 board.
Gpg4win 4.4.0 has just been released. I assume that this has been fixed in the meantime. In particular, "General error" should happen a lot less. If the problem still occurs with Gpg4win 4.4.0 then reopen the ticket.
• ebo moved T7078: Kleopatra: Add automatic offer of revocation certificate export to the revocation process from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Gpg4win 4.4:
When a keyserver is configured you can now check a box to directly upload the revocation there:
If no keyserver is configured, this is correctly not offered. Instead it is exported to the Documents folder, as the dialog then informs.
I assume the problem has been resolved because we never got feedback that the problem persists.
• ikloecker added a comment to T5006: Kleopatra: Display Names and Key-IDs for certificates after any attempt to import them..
Interesting. Just a few days ago I noticed that Kleopatra creates a new tab with the imported certificates except when the import is done via the notepad (or via the clipboard). I guess we could add an option to open a tab with the imported certificates to the import result window.
This problem has been fixed quite some time ago. See https://bugs.kde.org/show_bug.cgi?id=415168.
• ikloecker added a project to T4396: no connection to ui server kleopatra start up error: uiserver.
• ikloecker changed the status of T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well from Testing to Open.
We have to take the list of OIDs to ignore into account that can be configured for gpgsm with ignore-cert-with-oid.
We won't revert to the old UI which had its own share of problems. In the meantime Kleopatra supports certificate groups which should help if you often need to encrypt for the same keys.
Nov 28 2024
Nov 28 2024
• ikloecker changed the status of T7433: Kleopatra: Reloading smartcard does not import certificates from the card from Open to Testing.
Fixed.
• ikloecker triaged T7433: Kleopatra: Reloading smartcard does not import certificates from the card as Low priority.
• ikloecker changed the status of T7431: Kleopatra: Expired certificates not greyed out while loading card certificates from Open to Testing.
I also checked this on Windows 10 with light, dark and high contrast (theme No. 1) colors:
Nov 27 2024
Nov 27 2024
• ikloecker moved T7431: Kleopatra: Expired certificates not greyed out while loading card certificates from Backlog to WIP on the gpd5x board.
• ikloecker triaged T7431: Kleopatra: Expired certificates not greyed out while loading card certificates as Low priority.
• ikloecker changed the status of T7430: Kleopatra: After deleting expired card certificate text for corresponding card slot stays red from Open to Testing.
Fixed. After deleting the certificates belonging to the first two card slots the smartcard window shows
• ikloecker moved T7430: Kleopatra: After deleting expired card certificate text for corresponding card slot stays red from Backlog to WIP on the gpd5x board.
• ikloecker changed the status of T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well from Open to Testing.
Kleopatra does now read the certificates from the card and import them itself instead of relying on gpgsm --learn-card.
• TobiasFella raised the priority of T7429: Kleopatra: Importing certificate from Verification result dialog doesn't correctly re-verify the signature from Low to Normal.