Jump to content
Enpass Discussion Forum

Enpass becomes transparent


Recommended Posts

Apple, iMac, Big Sur 11.2.1

For a few days now, I've been noticing that Enpass seems to have a display problem: When I move the Enpass window from one screen to another, the window becomes "transparent". Most of the time it stays like that until I restart Enpass, sometimes it restores itself after a few moves.

Does anyone have similar observations? 
Does anyone know advice?
Or does Enpass need a BigSur bugfix?

Thanks + greetings


Link to comment
Share on other sites

  • 2 weeks later...

I too experience this, it ALWAYS occurs when dragging the application from one screen to a second screen.

However, I found this workaround that does not require an application restart: simply:

  1. zoom/maximise/green button top left the window and then
  2. zoom/restore/green button top left it to the previous size.

I have 

  • Enpass 6.6.0 (772) from the Mac App Store
  • Mac OSX Catalina v10.15.7
Link to comment
Share on other sites

Same issue here. 

Using MacBook Pro 2016 on Big Sur 11.2.1, Enpass version 6.6.0 (772)

It happens for me after leaving Enpass for a while in locked state without moving between monitors.

Please Enpass, fix this!

Link to comment
Share on other sites

  • 4 weeks later...

Hi @nics,

Sorry for the inconvenience. Can you please confirm the complete version number of Enpass? The latest builds are (Store) and (Website). 

If the issue persists, let us know the following details so we can further investigate:

  • Are you using dual monitor?
  • Let us know if any particular scenario or step on which you are getting this?


Link to comment
Share on other sites

  • 4 weeks later...

I confirm that the problem has not been resolved. I have enpass 6.6.1 (804) Mac App Store. Mac os Big sur 11.2.2. And it also becomes transparent.
This trouble happens less frequently than in the previous version. But sometimes it does happen.
I use two monitors. 

Link to comment
Share on other sites

Hi @Gaudeamus,

I'm sorry to hear that the problem has not resolved.  We have tried to quick fix in last release. There might have remained some scenarios where this issue could still happen. We have received an official patch from upstream vendor (Qt) that will eliminate the root cause of problem.  Fix will be available in the next update.

Thanks for your co-operation.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...