How can I pass from yast installed browsers to flatpack installed browsers without losing settings?

after the upgrade to 16.0 running KDE I would like to pass from some browsers (chrome, chromium, opera, firefox) installed via yast to the ones installed via discover/flatpack, I tried to uninstall them via myrlyn and reinstall via discover/flatpack but all the settings (opened windows, passwords, settings) disappeared, how can I recover disappeared settings and have the same browsers as before using discover/flatpack??

You may want to start with the basics and have a read about differences between packman and native solutions. The settings are completely seperated between packman and rpm.

What has Packman to do with this?

You mention several different programs. That they are all called “browser” by you is not relevant. Each of these programs may or may not have a way to export and import settings, etc… Thus you have to study each of these program’s documentation (and/or browse their menu items). And then maybe ask for one or more of these programs here for additional help in a thread that of course mentions the name of that program prominent it it’s title to draw the attentions of people that know more about that specific browser.

Yeah, typo. Flatpak was meant…

  1. I can only comment on browsers Chrome and Brave, which we use on all our machines (and smartphones).
  2. When I first execute the newly installed browser, and I log into my Google (or Brave) Account, they automagically import the passwords and some browser settings, based on the account I’m logged into.
    So, if I have six Google accounts, as I log into each of those accounts, all passwords are imported in the background. (this also happens with Chrome | Brave on our smartphones).

Unless functionality has changed, you’ll want to Export the Bookmarks, then Import into the new browser.
.
.
But if you prefer the technical route, the “native-installed” browser settings are found in your user’s “.config” and “.cache” sub-directories (they are hidden sub-dirs). See screenshot. And if you have different release-type (as I do), each of those different types (main, Beta, Unstable, etc) will have its own entry (see second screenshot).

So, you navigate down into each of those sub-directories and copy select files and sub-dirs for the browser.

Now, for the Flatpak version of the browser (and any other Flatpak app), the config files are found down in the user’s “.var” (hidden sub-dir). See third screenshot.

For each app, they have their “config” and “cache” sub-dirs under the app sub-dir. So now, you copy those saved files/sub-dirs into the appropriate config sub-dirs. You can see the config and cache sub-dirs for the VLC Flatpak app I use.
.
Sidenote: I recommend you add the repos from the browser’s vendor, then install the browser using zypper or Myrlyn … this way you’re getting the browser straight from the vendor (vs Flatpak) . See fourth screenshot, shows I have the vender repos listed (Brave and Chrome) … so when I run “zypper -vv up”, it will include any updates for the browser vendor.
.


.

.

.

I never actually had to do it myself but I think this should do the trick for firefox: https://support.mozilla.org/en-US/kb/firefox-backup

Backup to a location in your home folder from the native firefox and restore from your flatpak version.

You should be able to use FlatSeal and point the flatpak at the respective ~/. directory to pickup the configs.

Howdy @DuctTape … thanks for the reminder! :+1:

In Chrome and Brave , there is the “Sync” option in Settings. That’s what I was referring to in my previous Reply … when you log into a Chrome or Brave account (and Sync is ON), it automagically imports passwords and other settings in the background.

There is also sync for Firefox: Firefox sync