I've recently moved from Lastpass to using Pass[0] & BrowserPass[1], just as convenient and allows me to manage the storing of passwords myself. All files are PGP encrypted. Storing my passwords in my self hosted GIT allows them to be checked out on to my tablet and phone for convenience as well.
I'm not the user you were asking, but just as another perspective:
I've used LastPass for 7 years now. My Premium runs out next month, and I'm planning to switch away and not renew this time. Main reasons I'm switching:
* LastPass was acquired by LogMeIn. I don't know if this has had many major effects yet, but I don't trust them to be in charge of LastPass over the longer term.
* The browser extension (which is the main way to use it) has only gotten worse lately. Some of this is Firefox's fault, but not all of it. Some functions have disappeared, others have gotten harder to use, and both my wife and I have recently had it occasionally "lose" login info for new sites that we've signed up on. That may have been user error, but it never happened to either of us for years and we've both seen it in the last few months.
* They recently doubled the price of LastPass Premium.
not gp, but I did the same thing a few years back (well, lastpass->keepass->pass/git) primarily because I was sick of using a proprietary walled garden.
The main benefit of pass, for me, is that it's literally just gpg-encrypted text files. I can access my passwords even if I do not have pass installed, as long as I have my gpg private key. Using git to sync passwords makes it even better!
The android Password Store app (on f-droid) is a great graphical interface to my pass files, including handling git syncs.
+1 for the Password Store app, I happen to use an Android tablet and an iPhone and the "Pass" app on iPhone works just as well too (and includes touchID).
1) I didn't like that its approach seemed overly complicated (e.g. its database format, client apps, etc)
2) I was having a really hard time synchronizing passwords, especially if there was a sync conflict. When they happened, the entire database was a 'conflict'. There were also issues I had with the actual sync mechanism, which at the time I had the database on a seafile instance and had to enable various 'hacks' in keepass to get it to play nicely (e.g. file locking, etc).
Yes, it was exactly because of that, it could have been any password provider, there was nothing specifically wrong with Lastpass, the only reason I was using them was convenience.
There was a lot of fuss about migrating away from lastpass a while back but I always felt it was someone behind it, wanting to create fear so people would move away from them. Maybe lastpass is actually quite good and there are interests at play who wants people to move to less secure alternatives.
There's a rewrite of pass in Go[1] (because of course there is) that advertises multi user password management as a feature. It uses the same on disk format as pass, so it's compatible with all the addons and browser plugins that pass uses. It's been discussed here previously [2,3].
It is just plain text encrypted files in a GIT repo, so no reason why multiple people couldn't use it, I don't think there would be the ability to have segregation of folders for different people without some tweaks though.