Closed
Bug 1379752
Opened 8 years ago
Closed 7 years ago
Lastpass Extension becomes disable every few days
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jvarian, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170628075643
Steps to reproduce:
Install Lastpass Extension 4.1.53 from the addons site
Installs and runs
Use it for 2 to 5 days
Actual results:
Lastpass Extension is disabled, Firefox claims it's unverified
Expected results:
Keep working
Updated•8 years ago
|
Component: Untriaged → Extension Compatibility
Comment 1•8 years ago
|
||
The add-on is unpacked, so there's a possibility that something is being written in the installation directory, causing the signature to fail. It could be the add-on doing this, which would be a bug in the add-on, or some external process (like an antivirus) interfering.
| Reporter | ||
Comment 2•8 years ago
|
||
This is running under Mac OS 10.12.5 with no antivirus. I've filed several reports with LastPass to no avail, I just reopened a previous case with them including a link to this bug and your comment.
Comment 3•8 years ago
|
||
Have you opened the LastPass installation folder in your file viewer, by any chance? OS X can create hidden files and folders in directories if you do this, which could break the signature check.
| Reporter | ||
Comment 4•8 years ago
|
||
Haven't previously, I had to look up online to see where it is. How often does Frirefox check the signature?
Comment 5•8 years ago
|
||
Every startup, I think.
I am experiencing the same issue as OP. I also use an extension called FireFTP. It also appears to be an unpacked addon, but I've never had a problem with it getting disabled, even if I browse the installation folder.
Comment 7•7 years ago
|
||
This shouldn't happen with Firefox 57 and above, where unpacked extensions aren't supported (in normal install circumstances).
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•