Closed Bug 1344880 Opened 7 years ago Closed 7 years ago

LastPass 4.1.35 Toolbar on Firefox ESR 45.6 and 45.7 not saving present state on CentOS7

Categories

(Firefox :: Extension Compatibility, defect)

45 Branch
Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: kasai, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20161216132416

Steps to reproduce:

Update LastPass Toolbar for Firefox to latest version (4.1.35) from LastPass site with Firefox ESR version 45.6 or 45.7 version for CentOS 7.  Log onto LastPass with 'save email' checked.  Then log out, then back in.


Actual results:

LastPass does not remember User's email or previous state.  Going into Vault, LastPass goes through First time Tour every time.


Expected results:

Should remember previous state condition - IE: email/password being remembered.

Already reported this to LastPass.  Does not affect normal Firefox (51.0+), unique to Firefox ESR 45.6-45.7 on CentOS 7 build at this time.  LastPass states it is on Firefox end.

LastPass does not  have issues with Chrome running on CentOS 7 with above steps.

Suggests slight issue with how ESR is handling plugin configuration/permissions.

LastPass Add-on via Firefox Addon page is not affected, but when LastPass Toolbar is updated, functionality is broken.
Component: Untriaged → Extension Compatibility
OS: Unspecified → Linux
Running on Firefox 52.0 Linux build (64 bit) - LastPass Plugin for Firefox (Version 4.1.35) working as expected - ESR version 45.6 and 45.7 does not handle LastPass Plugin properly.
As LastPass is an add-on not owned by Mozilla and ESR 45 is going to be EOLed in 2-3 months to be replaced by ESR 52, I doubt Mozilla will fix this issue in ESR 45. In addition, it's technically not a security/critical issue which needs to be pushed in ESR. Let's close this bug as wontfix.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
No worries - Just reporting an issue in case it carries over to next version of ESR.  If Version 52 == ESR 52, should not present a problem, imho.
You need to log in before you can comment on or make changes to this bug.