User Details
- User Since
- Jul 24 2020, 9:57 AM (230 w, 3 d)
- Availability
- Busy Busy until Jul 29 2030.
Fri, Dec 20
Looks like gpg 2.2 doesn't emit a canceled status log message, but gpg 2.4 does if the problem only occurs with VSD but not with Gpg4win.
What components of Gpg4win other than GnuPG do you use?
Yes, that's by design. GnuPG is always installed in $INSTDIR\..\GnuPG by the gpg4win installer.
Wed, Dec 18
Backported for VSD 3.3.
Another data point:
$ locale LANG=de_DE.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL=
Are you sure that the translations for gnupg are installed? On Tumbleweed translations are usually in a separate package. After installing the gpg2-lang package I get this when I force the Turkish translation:
$ LANGUAGE=tr_TR gpg --version gpg (GnuPG) 2.5.2 libgcrypt 1.11.0 Copyright (C) 2024 g10 Code GmbH License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Tue, Dec 17
Mon, Dec 16
Backported for VSD 3.3
Let's backport this for VSD 3.3 even if https://dev.gnupg.org/T7227#195685 is just a cosmetic issue. The first impression counts.
Apart from checking the gpgme logs to see if validation is enabled for the key listing this can be tested indirectly by verifying that the Status column isn't too narrow after generating a new certificate in an empty keyring in a VSD version (see https://dev.gnupg.org/T7227#195685).
There's the VERSION file that is used for customizing the About data for VSD and GnuPG Desktop. It's an ini format file that's read with QSettings.
Thu, Dec 12
Which dialogs? pinentry? If yes, then your assumption is correct. pinentry also gets the texts from GnuPG.
I'm not sure what we need for the clipboard that's not already in the SignEncryptWidget. I think the SignEncryptFilesDialog mostly adds functionality for the file handling. It might make more sense to try to share code that's implemented for the Notepad and then wrap this in a simple dialog.
There were three parties involved:
- gpgconf --launch gpg-agent
- gpg -k ...
- gpgsm --server followed by LISTKEYS command
Wed, Dec 11
Backported the latest change for VSD 3.3
Tue, Dec 10
Maybe we could join the two dialogs, i.e. add the additional text and the Certify button to the import result window.
The title says "notepad". The description says "clipboard". What do you want?
Mon, Dec 9
We'll do this with QGpgME 3. And it's easy to add new functions by using the NVI pattern and, if needed, virtual functions in the attached private classes. I've been using this technique for quite some time now.
I think we have to use multiple different texts instead of assuming that we can use something general as "Detailed import results from %1" which fits all cases in all languages.
Fri, Dec 6
My comment referred exclusively to Tobias's "In the future [...]" comment.
"Tags" are stored with certifications. Therefore, I think it's useful and makes sense to show the Tags column in the Certifications view.
Isn't the name of the tab showing the imported certificates "Imported Certficates" or something like that? The filter "All" shows all imported certificates. And when you select the filter OpenPGP you see the subset of imported OpenPGP certificates. Therefore, I don't think it makes sense to add a custom filter.
Wed, Dec 4
This doesn't happen anymore now that we offer all valid user IDs and not just the primary user IDs.
I have created two subtasks for the two changes we could make in Kleopatra to avoid the gpg-agent startup race.
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.
Tue, Dec 3
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?
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.
This is long done, but only for Qt 6-based releases. Andre's comment T6663#175481 has also been addressed.
This is long done, but only for Qt 6-based releases.
Backported for VSD 3.3 / Gpg4win 4.4.1.
I'll backport this for VSD 3.3 / Gpg4win 4.4.1. Regression risk is minimal.
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).
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.
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 [...]
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
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
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'
T6109 is also closely related and I think it would be addressed by this ticket.
Backported for VSD 3.3.x / Gpg4win 4.4.1
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.
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.)
Mon, Dec 2
This also happens if one activates the Kleopatra main window, then activates the Windows Explorer and then starts a decrypt&verify 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
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.
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.
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.
I assume the problem has been resolved because we never got feedback that the problem persists.
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.
This doesn't look like a problem in Kleopatra.
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.
Kleopatra now let's gpg deal with I/O directly. This makes decryption with Kleopatra as fast (or slow) as with gpg on the command line. Hence I'll remove the Kleopatra tag.