StrangeNoises

Here with Enpass on macOS on a 2018 Macbook Air... which has TouchID. Enpass is inconsistent as to whether Touch ID is offered in the user interface. Sometimes it is, sometimes it isn't, and there doesn't appear to be a clear pattern to it. For instance it wasn't working earlier in this work-session (after the latest upgrade this morning, I am on latest version), but when I went to log into this site, suddenly it is working. Of course, sometimes the laptop is used in clamshell-mode with a thunderbolt dock and monitor, so it's not possible to use TouchID at those times. But often enough the lid *is* open, TouchID *should* be accessible, but Enpass doesn't offer it when I want to unlock it. I wouldn't be surprised if this is actually an issue with the Apple API for accessing these things, but thought at least let's register it and see what response there is. BTW partly because of this and partly because sometimes we do use it in clamshell mode, it would be nice to be able to set up *both* TouchID and a PIN, not have to choose one or the other.

BTW I just noticed Enpass (and Nextcloud FWIW) have the exact same issue on Windows - eg: if a 4K display that defaults to 150% is then set to 200%, Enpass and Nextcloud (QT apps both) again get left behind on the old scaling factor. So at least I guess we know us Linux users aren't being especially neglected in this regard OTOH I can see the Windows Store version of Enpass actually lets you specify its scale factor on a per-display basis in the Advanced tab of Preferences. That would be good in Linux too! Although of course in both places it's mitigation rather than a proper solution.

On 18.04, enpass 5.6.8 (but for several versions back from here too) I've been doing this: In /opt/Enpass/bin/runenpass.sh I added the line: export QT_AUTO_SCREEN_SCALE_FACTOR=1 above the exec line at the end. I have to do this after each time enpass receives an update. Note the 1 instead of zero. These days we *want* it to do it automatically. This at least means that enpass starts up with the right scaling. However, it takes no notice of when the gnome desktop scaling factor changes (such as when I dock my laptop and want to go from 300% scaling on my laptop's own screen to 200% scaling on the external monitor. It stays stuck on the scaling factor it started with, and has to be restarted. If you don't have cause to change your scaling factor during a session, that's not a problem for you, and the above is essentially your solution. This problem is shared by other qt apps. Dropbox and Nextcloud client do at least start up with the correct scaling factor without setting env vars like enpass, but they also get left behind by a scaling factor change. (In nextcloud-client's case, it gets the scaling wrong if it's auto-started on login, but I borrowed a fix from enpass in that case and set up an autostart delay.)