Today
Adding a new column to the layout is now remembered.
The with of the newly added column (Key-ID, all others are shown by default) is not set to the width of the content. But I think that is ok, one can increase the width manually and that is then remembered.
I am surprised that the solution with the separate tab was chosen… Looks like this:
works in Gpg4win-5.0.0-beta476
Ok, only 2 confirmations after the one above any more (for a standard key), they look like this:
Thank you!
Ok, my fault, I missed that in the beginning there was logging in the background which consumed gpg's error message.
If no logging is running in the background (that's something that often trips me…) on consecutive runs:
with Gpg4win-5.0.0-beta476
Yes, Kleopatra quits again with the beta from yesterday:
Yesterday
Fixed in gpg4win-5.0.0-beta476
Fixed by applying a patch to our version of MinGW. This affected all Qt programs build with Qt 6.10.
This has likely a similar cause as T1794
Observations (confirmation wanted):
- If no other gpgol-client Window is currently showing, the newly created window will show on top
- With the config window showing (but nothing else)
- clicking on reencrypt the first time will fail to bring the window to the front
- cancel it and click on reencrypt, again -> window comes to the front
- Similar observations when clicking on view/decrypt, reply, etc. for the first / second time.
- Hypothesis: Windows might become whitelisted depending on their title
Merged, manually (e63f7c1a62bd94594c0d7cd4326b94afc0e5fe71)
Should be doable your QStandardPath::GenericDataLocation . See also T7987
I have been able to reproduce this on linux with gnupg 2.5.14.
I had two users (named Alice and Bob in the example), each generating a key pair.
These are the steps:
- Both users have the "use-keyboxd" option in their common.conf (i could not reproduce the bug without this option)
Sun, Dec 21
Sat, Dec 20
Fri, Dec 19
Thu, Dec 18
Back to WIP because I had to fix a regression.
Well, I tested this again. I created a new key and saved a copy. The I updated the expiration date to 2035 and sent the key to the LDAP server. Then I deleted the updated key locally and imported the old copy. Thus I have now:
Panel Used By
| Dashboard | Prajeen's Dashboard |
