Jump to content
Enpass Discussion Forum

_Sascha_

Members
  • Posts

    1
  • Joined

  • Last visited

_Sascha_'s Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • First Post

Recent Badges

0

Reputation

  1. For me on a , Mac Mini M1 2020 with 16GB with MacOS 12.4, Enpass works great. But on the Mac Mini M1 2020 8GB with MacOS 12.4 of my brother a similar issue (which was mentioned in this thread) showed up already the second time. The issue As soon he logged in, the Dock on the bottom fills up with multiple Enpass instances/icons: First attempts: To close all these 1. My fist idea was to close all Enpass instances via Terminal with the following command (without success): killall Entpass 2. Then I looked into the activity-monitor for Enpass, but didn't found anything mentioning Enpass. 3. Afterwards I tried to find Enpass mentioning somewhere in the terminal (without success) with the command: ps aux Second attempt: To close all these Because I wasn't able to find Enpass via terminal/activity-monitor, I decided to close all these instances/icon by hand. Most of them disappeared already when you clicked on one of them (means, they didn't opened anything). At the end only 4 instances/icons opened the window which asked for the master-password. What was suspicious, these 4 instances/icons even stayed in the bar (as if you put them there for quick access) even after the window/instance was closed. Afterwards when logged in with at least one master-password prompt/window, Enpass behaved normal like usual. My guess: When tried to reproduce this Could it be, that Enpass doesn't started on Startup and just the Firefox or Chrome plugin toggled these instances multiple times? I just got the idea, because there isn't any clue about Enpass in the activity-monitor when so many instances/icons are running. I tried to keep the Firefox instance open (one time without any windows, one time with two pages) and restart MacOS with remembering last session (opened apps). Sadfully, without any result. I couldn't reprodurce/trigger the bug! Now: Debug time Enpass got installed the usual way once. We could delete Enpass completely (and remove all installed extensions) and maybe with some luck solve the issue. But this wouldn't help the Enpass community, so I think we will wait until the issue shows themself the next time, for further inspection. And there is my question, what do you guys need for the next time? - I'm developer and admin, so I can crawl every additional informations together when this happens again. - Enpass logging is now enabled.
×
×
  • Create New...