- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 6 2024
Nov 5 2024
If compliance is not active, the self-test dialog now shows the test for compliance with just "?" as the test name
Oct 31 2024
right. the installer needs to install kleopatradebugcommandsrc next to libkleopatrarc
Oct 30 2024
Oct 29 2024
Tested again on linux with current master (at 18081e2ecf43de2be6ad5a7ca3384e1e2b66914d) and 2.2 (at 5c0383d558cc9112c4c0984a3b2a6c98b29a92ca) - still same behavior.
Oct 28 2024
Oct 17 2024
Implemented in https://invent.kde.org/pim/kleopatra/-/merge_requests/290
Oct 16 2024
Oct 15 2024
I'm still seeing the same problems both with current master and 2.2
Oct 14 2024
Summarizing out-of-band discussion (please correct where i remember things wrong):
Thinking about this some more, I don't think we can anything different from what's done in my patch:
Both subkeys belong to Alice from gpg's point of view
We have this data already. The problem on kleopatra's side is that in the key cache, we add the ADSK subkey for each key that has it as an ADSK, causing a somewhat broken index and ultimately the problem seen here.