Profile decryption problem after last update
-
@syklist said in Profile decryption problem after last update:
Does MacOSX use one of the same keystores that Linux distros use?
No, keystores of different OS and Desktop Environment are are incompatible.
-
I seem to remember that the MacOSX networking menu and layout of the applet on the menu bar looked almost identical to the Gnome network manager applet. That is many years ago when I was still using MacOSX as well as Linux. Maybe the similarities were a set of serendipitous coincidences. I also understand that MacOSX has its own UNIX like kernel but makes use of BSD components for other parts of the OS. So that is why I felt that my question had some merit.
On the subject of multiple DEs my PinePhone Pro is running two DEs which are related. One is mobian/Phosh/Wayland the other is mobian/XFCE/X-org. XFCE is a GTK desktop and hence uses a lot of Gnome backend components. AFAIAA XFCE uses the Gnome keystore for example.
If I was running Plasma Mobile and XFCE then I can imagine that there might be two keystore components installed. So it does depend as to which DEs you are running as to whether or not you have multiple keystore systems installed.
-
@syklist said in Profile decryption problem after last update:
So it does depend as to which DEs you are running as to whether or not you have multiple keystore systems installed.
Yes or Yesno [as f.ex GNOME and KDE keystores not interchangeable]
-
I believe warning message is a good intent, but lacks clarity. If the warning would say: "You'll be logged out of all accounts, but all your other settings will stay", than people would have less panic attacks.
Got this on Fedora/Gnome today, just after normal startup. Read internet, decided I'd just "Lose data" instead of trying to find out what how to restore keys, especially if I don't have backup. Did backup of
~/.config/vivaldi, "lost data", re-logged, re-enabled sync. Job's done.
-
I had this issue today, at the latest version right now. In my case, it was because I moved the profile directory from another computer to the one I am using now. And I guess this was normal behavior but it still got me caught me off guard.
Because last month I moved to Linux (CachyOS based on Arch) from Windows for a test drive. But my open tabs, history and everything mattered a lot. So I followed a recommendation on this forum about moving the profile folder and that it won't cause a problem as long as long only one of them is actively used after moving. And to my surprise, it worked like a charm, without an issue.
So I happily enjoyed my new Linux test box. One month later I decided to move to Linux for good, with a new computer (that's yesterday) and today I tried moving my profile folder again (from exact same OS to exact same wallet to exact same version of Vivaldi) without knowing it would cause me this issue. Because in the end, it didn't cause me a problem when moving from an entirely different system, so why would it cause now when everything is the same, right? Vivaldi opened the profile selector with this warning. One of the team members say this indicates two separate problems but I don't know..
First I tried the data loss option, because I didn't care about the saved passwords and cookies (as I am already using a self-hosted password manager), but it wiped everything including my open tabs.
Then I saw this topic and imported the encryption key plainly from one computer (KDE Wallet) to the other and copied the profile folder again. This time it opened everything normally like I have been using it with the old computer.
I just wanted to share my experience to contribute a different case example.
-
@oelma Most users copy only the Vivaldi profile folder. But Vivaldi needs the old keyring secret to decrypt profile data.
I guess your forgot to transfer the KDEWallet keyring to new computer. -
@DoctorG said in Profile decryption problem after last update:
@oelma Most users copy only the Vivaldi profile folder. But Vivaldi needs the old keyring secret to decrypt profile data.
I guess your forgot to transfer the KDEWallet keyring to new computer.Yes I figured, that's why I said it was the normal behavior. The interesting part was moving from Windows to Linux without any data loss and without any key migration, although you said different OSs are incopatible. Guess that means Windows instance is unencrypted, isn't it? (By the way as I said, I transferred the key and that's how it worked anyway.)
Secondly, I shared this experience to show probably having this error along with the profile switcher doesn't have to imply two different problems at the same time.
