User Details
- User Since
- Jul 24 2020, 9:57 AM (258 w, 1 d)
- Availability
- Busy Busy until Jul 29 2030.
Thu, Jul 3
Closing. I don't think we need this "Klammer-Ticket" anymore and it's cluttering my task list.
I'm not working on this anymore. Kleopatra should be prepared for using VSD, GPD, and Gpg4win in parallel (provided they use different homedirs). What's left is the actual parallel installation which might be solved in part by using NSIS for Gpg4win and MSI for VSD/GPD. I'm not sure how the parallel installation of different versions of gnupg is solved, but I guess Werner has that covered.
For KF5-based builds this is resolved because the improved heuristic for detecting light high-contrast themes (like "Desert") is used for VSD 3.3 and Gpg4win 4.4.
For simplicity (and because I think entering tab characters isn't really essential for the notepad) I decided to go with the first solution.
Wed, Jul 2
Ready for testing.
Tue, Jul 1
A second patch fixes the problem with the button in the smart card view.
I have added a patch to disable recoloring of the status icons in Gpg4win. This ensures that the status icons in the selected rows don't get all-white.
Upstream bug report for invisible status icons: https://bugs.kde.org/show_bug.cgi?id=506434 (Icon coloring is inherently incompatible with colored Breeze status icons)
gpg --version?
gpg -K?
Mon, Jun 30
I guess that the missing formatting of fingerprint or key ID isn't restricted to v5 keys. -> separate ticket
Thu, Jun 26
This also happens on Linux. And even with the Fusion style.
Thanks for the Windows 11 screen shots.
Regarding the "unsure" findings:
- invalid state in cert list tooltip (red on black)
Wed, Jun 25
This will never happen on stock Linux.
Tue, Jun 24
This is more a technical ticket. There's not really something to test. Setting to Resolved/Done as discussed with ebo.
Most issues with icons in high contrast modes (of Windows 10) should have been fixed. Needs to be verified especially with the high contrast modes of Windows 11.
Setting to Testing.
Moving to QA. All changes should be in the latest beta.
Many issues have been fixed. Setting to Testing to check what I have missed.
Mon, Jun 23
The problem with the invalid certificates seems to be unrelated. Isn't there already a ticket for Okular for certificates which expire after 2038?
And in the first case, about 6 seconds are lost starting keyboxd:
2025-06-23 13:16:55 gpgsm[3252] DBG: chan_0x000000000000022c <- VERIFY 2025-06-23 13:16:57 gpgsm[3252] Kein aktiver keyboxd - `C:\\Program Files\\GnuPG\\bin\\keyboxd.exe' wird gestartet 2025-06-23 13:16:59 gpgsm[3252] Warte bis der Keyboxd bereit ist ... (8s) 2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- # Home: C:\Users\g10\AppData\Roaming\gnupg 2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- # Config: [none] 2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- OK Keyboxd 2.5.6 at your service, process 4748
The keylisting hangs ticket for Kleopatra: T6623
Mon, Jun 16
Can be tested with next VSD 3.3.x build.
Fri, Jun 13
Thu, Jun 12
I have added the changes/patches to the vsd-3.3-branch of gpg4win
If Kleopatra is already running then running
- kleopatra --help shows the help in a window
- kleopatra --help-all shows an error
- kleopatra --version, kleopatra --author, and kleopatra --license open the About window