Issue with KeePassXC Window on Extended Screens via WavLINK Docking Station

[rboerner]

Originally Posted by IngmarFranke

Could this be a compatibility issue with the docking station or DisplayLink? Are there any known workarounds or settings I can adjust to resolve this problem?

Thank you for your assistance.

Best regards,
IF

If you access the 'View' option within the menu bar for the KeypassXC application and enable the option for 'Allow Screen Capture', does that resolve the issue?

[dbienkowski]

Yes, then the problem will be solved and the application will be displayed correctly on DisplayLink screens.

[Michael B.]

Originally Posted by dbienkowski

Yes, then the problem will be solved and the application will be displayed correctly on DisplayLink screens.

IMHO this is only a terrible workaround, but not solution. The root cause is, that KeepassXC classifies DisplayLink as application, which is sharing the screen (see: https://github.com/keepassxreboot/ke...ent-2536529336). The screen sharing protection is supposed to prevent sharing the KeepassXC window with other people in video calls such as teams, webex, skype, slack etc.

But showing the KeepassXC window on external displays by using DisplayLink should though be possible without disabling the screen capture protection. Since this is not the case, the "complete setup" still is broken .. and the question is, where it can be fixed, in MacOS, KeepassXC or DisplayLink.

Some thoughts about this:
I saw this misbehaviour before in May after updating to MacOS 14.5 with DisplayLink 1.10.1.93. But it disappeared after installing DisplayLink 1.10.2.14 did not reoccur with MacOS 14.5, 14.6 and 15.0.
After updating to MacOS 15.1. it was back again (a few days before DisplayLink was updated to 1.11.0 on 15.0 without any negative effect).
For me this looks like the first time in May the misbehaviour has been fixed in DisplayLink from version 1.10.1.93 to 1.10.2.14.

==> So I would hope, that there will be a DisplayLink update again, which will fix the misbehaviour, that reappeared with MacOS 15.1.

Best regards,
Michael