Weird issue with Chromium based browser from Flathub

Ask Fedora
, , , , , ,
1

Hi Community,

I am facing a strange problem on my FSB41 machine: all Chromium based browsers got an update to version 135 and it looks like all browsers are facing the same bug: It looks like all cookies are being deleted on application exit, so i have to accept them every time i visit a website. affected browsers:

  • Chromium
  • Edge
  • ungoogled-chromium

All browsers are installed from Flathub. It doesn’t happen when I install the browser through the toolbx (tested with Chromium). I did a fresh install of Silverblue in a VM and couldn’t reproduce this. I guess there is something nasty that only happens when upgrading. I have already tried removing the app directory in .var/app/org.chromium.Chromium/ (for example) so that I start with a fresh profile, but to no avail. I have also tried uninstalling and reinstalling Chromium, also to no avail. Downgrading to the previous Flatpak commitment fixes the problem. But why is this happening on my FSB41 installation and not on a fresh install? I’m a bit lost…

1 Like
3

I have just found the cause. I had an old keyring called “Default Keyring” stored in ~/.local/share/Default_keyring.keyring and another file called default in the same directory, pointing to the Default_keyring.keyring file. I suspect this is from an older Fedora release; the file was a plain text file, unlike the binary file login.keyring. I simply removed them. After that, all browsers behave normally again.

2 Likes