As the title says, FF seems to selectively forget cookies and thus requires me to constantly re-login.
I’ve had the exact same issue on two separate machines both running Ubuntu. My best guess is, that snap is at fault here, but I have no idea, why.
To reproduce the issue, I just have to perform the arcane ritual of “closing the app” and whoosh, cookies are gone. Plugins and settings persist, no “delete on close” option whatsoever is active. Vanilla Ubuntu shows exactly this behavior.
You must log in or register to comment.
Have you tried installing a non-snap version to confirm the theory?
@bahmanm @agressivelyPassive why is there so many issues with snap? I have ran into some issues with snap installed apps in just 2 weeks of using linux
Not an Ubuntu user, but I think it’s all about how a snap uses filesystem, esp directories which are not writable by the “world”, such as your home directory.
Yes, and that does not have the issue.
Would it make sense to stick to the good old DEB package instead of the snap then?
The Mozilla Team PPA seems to be legit. If you’re not sure how to do it, please take a look at OMGI Ubuntu guide which uses the same PPA.
I thought the mozillateam PPA would start installing the snap too now, or has that change not happened yet?
I wanted to say “I’m not sure. I’m not on Ubuntu” but then I remembered about distrobox 😄
It took only a few minutes to confirm that the links I shared earlier (https://lemmy.ml/comment/3090571) do NOT install the snap version.
I just thought for sure I read somewhere, a few days ago, that the mozillateam PPA would start distributing the snap version instead, but either that was a lie or a joke, or it’s a thing that might happen in the future.
Thanks for checking!
I have a similar issue (also Firefox on [K]ubuntu 22.04) every time I open a link on a logged-in site in a new tab, but in my case merely refreshing the page is enough to get me logged back in.
I assume is most likely the fault of the fairly aggressive mix of extensions I’m running rather than Firefox itself, but I haven’t actually tried to troubleshoot it yet.
I’m having a similar issue w/ Chromium on Debian 12. Only affects one out of three computers tho
I’ve noticed this exact same behaviour on my partners laptop and when comparing each and every single setting of her browser with mine, to find no difference.
I ran both installations (Mint), with no issues.
