Everything posted by _Sascha_
I see what you are referring to. But I have only four login-items under April 2023 for recently used, which doesn't even fit to the logins where I copied passwords out from, it also doesn't fit to the amount of autofill logins, other login-entries were involved and used (they are used April but shown in March 2023). And Frequently Used items has six items show as frequently used, where I can tell, nope two of them are never used this much. But before I/we continue this thread and feedback/request, I will try a cleanup/reset by removing Enpass from the Desktop device, (+ Library data) and try to reset everything with a fresh reinstallation and sync afterward. Coming back to this topic then, in a month, with a result.
Request Enpass currently sorts entries by frequency, recency, title, creation date, and modification time. I propose adding "Last Interaction" and "Most Interaction" as additional sorting criteria. This change could be useful for users who primarily use Enpass on their (local) Host-System, to copy information to their guest systems (like remote desktops or virtualized and streamed computers). These users often rely on keyboard shortcuts and the Enpass Mini-App to copy logins, license keys, and passwords from the host system to the guest system. Currently, Enpass doesn't remember the last interacted item, which can be inconvenient when providing additional information like OTPs. By tracking the last and most frequent interactions within a 1-2 week period, Enpass could improve the user experience withthe two mentioned sort-criterias from aboth. Interactions could be counted, when the user confirming, copying content from, and editing an entry. Personal case/note: I'm developer, administrator and sometimes also a gamer. So I have a lot of remote-applications, virtualized environments and also playing games via Blade Shadow on a cloud computer. From my security perspective, I don't see any reason to install Enpass on the guest-environments. So I access it only via the global-hotkey of the host-operating-system. It's just a bummer, that it doesn't keeps last and most interacted items up in the list. Because it doesn't remembers my interaction (copying) with them. So most of the times I have always to repeat to search for the entry, before I can interact with it again.
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.