nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Starting today LastPass is not filling in log-in info

bsmithgg

Out of nowhere LastPass is not working correctly and is showing new behavior that I have never seen before.

I go to q website, for example this site, it opens to the login page.

The two fields for name and password have the familiar red LastPass icon.

I click on the icon which typically allows me to tell it to fill in the data.

Instead of the data filling in, a pop-up appears in the upper left, below the tab bar. It is from LastPass.

The message says "Start Typing"?

There is a pop down menu that has a few options including Open the Vault. This option works.

Also theLastPass icon to the right of the URL address bar at the top similarly does not let me proceed.

That means I have to locate the website in the vault. View the login and password and copy/paste them to get into the website.

What is going on?

I'm on the current version of Chrome and useLastPass Premium.

Find more posts tagged with

Accepted answers

Erin Anderson

Go to your Vault, and click Advanced Options, and disable the Use Improved Save and Fill. Per the rep I just spoke with, this has been a known issue since it was introduced in the latest extension update. Doesn't affect 100% of people, but disabling it does fix the issue for people experiencing problems like this. Should be fixed in an upcoming update to the extension, but he did not know the exact ETA. I tested it here, and it did fix the issue for me.

All comments

Erin Anderson

Same thing started happening to me around the same time. I am waiting for a call from LP support right now to see if they can provide any better insight.

Erin Anderson

Go to your Vault, and click Advanced Options, and disable the Use Improved Save and Fill. Per the rep I just spoke with, this has been a known issue since it was introduced in the latest extension update. Doesn't affect 100% of people, but disabling it does fix the issue for people experiencing problems like this. Should be fixed in an upcoming update to the extension, but he did not know the exact ETA. I tested it here, and it did fix the issue for me.