and for certification revocation (and some other places): https://invent.kde.org/pim/libkleo/-/merge_requests/197

For card stuff: https://invent.kde.org/pim/kleopatra/-/merge_requests/400

For the tooltips: https://invent.kde.org/pim/libkleo/-/merge_requests/196

Works fine here.

I can't reproduce. Please check whether this works if you use gpg directly; it's a bit unlikely that this is kleopatra-specific, since kleopatra doesn't really care whether the key is on a smartcard or not.

since @ebo asked about this: the current state is that the first column of all tables can't be moved. This seems to be what we want, so nothing needs to be changed and nothing was done to change this. I guess this ticket can be closed.

The relevant changes have been merged to the gpg4win branches of kleopatra and libkleo. We can start creating a test build

Note: The Kleopatra in upcoming versions of Gpg4win 5 will have AboutData::version set to gpg4win-5.0.0 (or gpg4win-5.0.0-beta190 for beta versions). See T7666: Kleopatra: Rework versioning.

That screenshot is for kleopatra crashing, not related to okular.

The problem here is that the version number in kleopatra is still 4.0.0-something, which is then compared to 4.4.0.

Apparently KMessageBoxes do actually wrap, just at a larger width than we'd have expected. Lowering this width should be a trivial patch that we could do locally, if we want to