If the high-contrast mode is active (on Windows), then we disable the usage of custom colors in Kleopatra. This avoids problems with too low contrast due to the custom colors.

Hi there!
I can confirm this regression on my yubikey 5 Nano with 2.2.36 (2.2.35 works) - on archlinux. Yubikey firmware 5.4.3, ed25519 keys too. Some more info:

Note to self: On Windows, we need to check whether the high-contrast mode is enabled. If yes, then we must not use any custom colors. KColorScheme doesn't help here.

I'm going to backport this to 2.2, as it found useful.

Yes, I am using ECC keys:

Key attributes ...: ed25519 cv25519 ed25519

Please use the feature in 2.3.7 of T5099, instead.

It's in 2.3.7.

It's in 2.3.7.

It's in 2.3.7.

Changed the tags and the title.

Fixed in 2.3.7.

And 2.3.7.

Fixed in 2.2.36.

Perhaps, rG53eddf9b9ea0: scd: Fail when no good algorithm attribute. should be backported to 2.2.

It's in 2.3.7.

It's in 2.3.7.

It's in 2.3.7.

It's in 2.3.7.

It's in 2.3.7.

It's in 2.3.7.

Fixed in 2.3.7.

Thank you. I learned that there is new firmware, version 5.4 series.

The user id table is not accessible at all (neither the whole rows nor the individual cells).

We have KWatchGnuPG for watching the log files.

@gniibe Thanks - mine's 5.43. (And the working 4Nano is 4.34.)

In gnupg/common/ttyio.c, the function w32_write_console does:

• Call WriteConsoleW, and when it fails, it calls
• WriteConsoleA

Please let us know, your firmware version number (in bcdDevice) by lsusb.

Due to vacation the review may take some time.

I suggest to submit a patch with the changes you'd like to see. Please read
https://dev.gnupg.org/source/gnupg/browse/master/doc/HACKING
for information how to contribute to gnupg.

I can confirm this issue with a 5C Nano returning the error, but a 4C working successfully. Downgrading to 2.2.35 does resolve the issue.

It will hopefully be fixed in 2.2.37.

Hello,
thanx for fixing this issue ...

Any chance someone is able to review the posted patch?

I wouldn't call that particular thing technical specification, because it really has potentially a strong user visible impact (i.e. expected passphrase works or not - both cases, whether any other newline characters are included or not, as well as whether it would simply ignore any characters beyond a maximum length).

Pushed the change.

I'm not sure whether the manual page should be blown up to a full technical specification.

It looks like having it set will stop fallback from working entirely? Would you say that this cannot be fixed if WAYLAND_DISPLAY is set like I do above?

It looks like having it set will stop fallback from working entirely? Would you say that this cannot be fixed if WAYLAND_DISPLAY is set like I do above?