jpenny84 Wrote:ikjadoon Wrote:You've misread that completely: I choose to log back in every time I notice I'm logged out, but others simply do not notice LP has logged out or do not care LP has logged out (because most websites retain cookies and you don't need to repeatedly log in, i.e., use LP). If you only login once after a logout, then you would only be "logged out once a day".
There has been a high number of reports that began around August 2017, which exactly coincides with my timeline. Maybe you are not well-versed in the community postings on this issue, so I've compiled them:
https://www.reddit.com/r/firefox/commen ... e_firefox/
https://www.reddit.com/r/Lastpass/comme ... hem_a_lot/
https://www.reddit.com/r/Lastpass/comme ... _password/
The very thread you have stumbled upon was started in October 2017.
I have been an unpaid contributor on this support forum for over six years, with over three of them being a moderator, which means that in part that I approve items in the moderation queue. I can tell you from experience that If there is a "widespread bug" with a LastPass browser extension, people flood this place to report it. Occasional reports over the course of several months contradict your assertion that random session terminations are a "widespread bug."
The fact that you state the behavior goes away with a new profile, but appears after adding on third party items seems to suggest that you need to test LastPass against those components.
victor676 Wrote:This isssue is going on for quite a while and is quite frustrating to have to deal with it. After months of denying the problem, finally I got a reply on the ticket opened on this subject that they could replicate the issue and that devs are investigating but there is no ETA for a fix.
You've reached LastPass Support! We’d be glad to assist you accordingly.
Upon checking, there is currently an ongoing report about this issue. We have yet to see any further resolution from the Development / technical team. But rest assured that they are doing their best to resolve this issue the soonest possible time. I will add your occurrence to the internal report, so our Development team will be alerted and to add severity to the ongoing issue.
David206 Wrote:Maybe, and this is just a guess, mind you, maybe when LogMeIn purchased LastPass they fired all the engineers who had been working on it. Maybe, just maybe, there is just one engineer working on LastPass, and he or she is a LogMeIn employee who knows some c and HTML but doesn't really want to learn about the internals of LastPass (they are probably pretty boring and messy). Think about it. This is the perfect explanation for why they are ALWAYS (rest assured) doing their VERY best to resolve this issue in the SOONEST possible time.
victor676 Wrote:This is the reply I got:
"Our team was able to replicate this issue on our end, so a report was submitted to our devs and an investigation into the matter is at hand. You may keep track of our timely extension updates here https://lastpass.com/upgrade.php?fromwe ... asenotes=1. The dev team has not shared an ETA for a fix. Our sincerest apologies for any inconvenience this may have caused. "
Users browsing this forum: Google Feedfetcher and 46 guests