Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Firefox on Linux has done this to me a few times and cost me a lot of progress and time.
I never had this issue. What were you using deb, rpm, flatpak or snap version?
I had it this week on my Mint laptop, with the bundled Firefox. I hadn't used the laptop for a few weeks, so I knew it needed updates, but I needed to get something done straight away.
I opened something in a new tab, and it opened as the restart to update tab. As well as breaking my train of thought, it restarted without opening the new link, but also warned me that it wouldn't reopen any private browsing tabs and another type of tab that I can't remember.
However they justify it, that's bad design.
That's not Firefox forcing you to update, you had Firefox open while you (/your package manager) was updating Firefox and after the update was done Firefox needs to be reopened. To prevent this you just have to ...not update Firefox while it is running.
I didn't say that it forced me to update. This set of replies is about apps that force close and don't let you do anything.
My Firefox updated in the background, because that's how I set my system up, but instead of letting me keep working and updating on the next app start, it forced me to stop what I was doing and update there and then, while telling me that it wouldn't be restoring any private tabs that I had open.
As a contrast, I was also running Chrome. That also updated, but waited for an app close before completing the update. It didn't interrupt me, and it didn't lose any of my open tabs.
Firefox has it wrong in this case.
I'm not near my computer to confirm right now, but I think I installed it manually from the tar file. I think there was an issue with the flatpak version on Pop!_OS, but I can't remember what, since it has been years since I originally encountered it. I can confirm tomorrow if you want.
It's weird that someone downvoted your question. I upvoted it to put it back at one. Idk why people downvote questions so often on this platform.
Firefox flatpak version had a lot issues. It has improved a lot, still a long way to go.
I have exclusively used Firefox flatpak for the last year and updates has been quite smooth. Never had my session closed automatically(to my memory) due to an update, usually waits for me close the session and when I reopen its updated.
My experience is limited to Ubuntu.
I'm going to guess user error
It's not. There are several threads about it online
Xbps on Void does it for sure.