Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tabs won't autosave. Ubuntu 19.1 #95

Open
coreycdm opened this issue Oct 2, 2020 · 4 comments
Open

Tabs won't autosave. Ubuntu 19.1 #95

coreycdm opened this issue Oct 2, 2020 · 4 comments

Comments

@coreycdm
Copy link

coreycdm commented Oct 2, 2020

I've tried many times to get autosave to work on my Ubuntu machine but to no avail. It works just fine on my Windows machine. Tabs will save if I manually save the session, but other than that, nothing shows in sessions or history.

@echristopherson
Copy link

That's true here too, using Firefox 83 on Pop!_OS (an Ubuntu variant) 20.04.

@coreycdm
Copy link
Author

This works for me now. I wiped/reinstalled to 20.04 as a part of my upgrade cycle. I'm running FF 84.

@ReDEnergy
Copy link
Owner

ReDEnergy commented Jan 28, 2021

It's broken even on Windows, and constantly happens for various users after Firefox update. Reason... well... seems that my code is not the problem and I will have no way to fix it because something is broken in the WebExtension API or it's caused by Firefox itself. Why I say this because the actual issues that prevent me from reading the history tab crashes in the API with a stupid reason

image

If the API's don't work... I have no idea what to do :| . And on top of that, the issues is fixed if you sometimes clear the Firefox profile or reinstall the addon but at that point you lose all the data from history because that's local storage to the addon and once the addon is reinstalled everything is wiped out. Some very smart decision on the API part 🤷‍♂️. And so I'm left with a broken addon that many think it's the fault of the developer Yeyyyy :(

Sorry guys, but can't do anything about this unless there is something caused by me not by the API itself from within Firefox.

P.S I just noticed it in my own case, it's no something that happens often and I was not able to even reproduce it for a months, and when I could I had no way to debug it properly. Now I understand why I was not able to find the issue within the code.

@coreycdm
Copy link
Author

Thanks for the update--I appreciate you explaining the reasoning. I still love the plugin, even when I was manually saving sessions. I'm glad that it's back to working automatically after my dev box rebuild!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants