Profile decryption problem after last update
-
@yngve said in Profile decryption problem after last update:
@andrewsjon Please keep in mind that we added the warning so that users would be warned if they where about to lose their encrypted data.
Please keep in mind that the first time I started losing access to my encrypted passwords was AFTER the warning was added.
-
@yngve said in Profile decryption problem after last update:
AFAIK (I was not involved implementing it) what the code does is 1) Detect if the decryption of data failed before the profile is initialized,
So perhaps there is something going wrong with this step?
An example of the idea that observing something either changes it or in some cases brings it into being?
Maybe the OS functions/APIs called by Vivaldi either have a hitherto unknown bug and/or the Vivaldi code to detect if decryption of the data store has occurred has made assumptions that turn out to have unexpected/undesirable results.
-
@luetage said in Profile decryption problem after last update:
Additionally I haven’t found steps to reproduce it reliably, therefore I haven’t reported it. But something is afoot.
Same here. There seems to be no rhyme nor reason as to why it occurs. I have a fair few devices running debian based OSs and it has happened to a handful of those devices. With both Vivaldi stable and snapshot. In the case of one device it has occurred more than once.
-
@syklist As mentioned, I was not involved (and I don't normally work in a Linux Desktop environment, usually only in a terminal).
What I know is that a QA that was involved with testing says that every time the dialog showed up on Linux for any of the testers, it was caused by having switched to a different Window System that used a different keystore.
My suggestion to you and anyone else that repeatedly see this warning without having switched the Window System should file bugs with as many details as possible about you system and what happens and especially what was done to the system between exiting Vivaldi the last time, and seeing the dialog again.
-
@yngve As said, I’ll do so when I find steps. Might just be a coincidence, perhaps Chromium made a change concurrently and the Vivaldi changes are not the cause.
-
@yngve said in Profile decryption problem after last update:
@syklist As mentioned, I was not involved (and I don't normally work in a Linux Desktop environment, usually only in a terminal).
I am fully aware that you have stated that you were not involved in the development of this feature. By engaging with you I am not trying to imply that you have any in depth knowledge of the code nor the development process. Apologies if I seem to be implying that.
Perhaps you could ask a collegue is involved in Vivaldi for Linux development to come and "ta en titt" at this and other threads that can be found in the Linux Desktop section of the forum regarding the appearance of the problem.
What I know is that a QA that was involved with testing says that every time the dialog showed up on Linux for any of the testers, it was caused by having switched to a different Window System that used a different keystore.
As I have mentioned switching desktops is definitely not the cause in the cases I have experienced. All the devices I have experienced the problem with have only ever had one DE installed.
My suggestion to you and anyone else that repeatedly see this warning without having switched the Window System should file bugs with as many details as possible about you system and what happens and especially what was done to the system between exiting Vivaldi the last time, and seeing the dialog again.
The problem I and others have mentioned is that in order to file a bug report we need
a) to know what we did to provoke the problem and
b) repeatable ways of triggering the problem.In the cases I have seen it seems to be
a) open Vivaldi at some time after the new warning about keystore decryption problems was implemented
b) none -
@syklist What I can tell you is I haven’t had this issue since opening the keyring application and deleting all entries belonging to Vivaldi/Chrome. This includes Chrome Safe Storage, Chrome Safe Storage Control, and a third unnamed application entry with an app-id for either vivaldi‐stable or snapshot, depending on what you are running. You will lose your logins one last time and then it might perhaps be fine. No guarantees, but it’s worth a shot.
-
@daniel
So I am trying to use X-forwarding. Can I create a profile on this machine and sync it to my profile on the originating machine? I have sudo privileges on both.Art Edwards
-
This happened because my old mac mini was thrashing and the fan noise was annoying even though not acively using Vivaldi. So I migrated to a macbook Pro. I assumed, wrongly that syncing would transfer my workspaces, and 400 passwords. I uninstalled and re-install and got the same message inviting me to lose my data. It doesn't accept my existing gmail accounts that work OK on a macbook pro laptop.
Why can't syncing sort out the problem?
-
@lenand
Hi, you sync a empty system to an empty server.
Can you still reach the Mac Mini? -
I installed a fresh Sequoia 15.2 yesterday and found out after installing Vivaldi that sync wasn't working. I then used my fresh Time Machine backup I made just before formating the disk for a new OS installation . After new OS installation I copied the Vivaldi Backup folder back to Sequoia 15.2 and getting this when starting Vivaldi:
vivaldi Vivaldi could not unlock your secure key store. Without the key store, you will lose your saved logins, secure cookies, and some features like Sync, Mail, and Calendar will stop working. Please quit now, unlock or repair your key store, and then try again. Do you really want to continue, but lose data?
First. I have no clue what a secure key store is and how or where to repair it! No upfront documentation what so ever
This is redicilous. First there are issues with sync and then this. It is far too complicated with Vivaldi nowdays.
I decided yesterday to leave Vivaldi forever but thought this morning I should give it alast try. And this happens. I am not prepaired "finding out new things to fix what broke" when simply restoring from backups. So finally, time for an another browser!
-
So mac users are also experiencing this problem.
Does MacOSX use one of the same keystores that Linux distros use?
-
@syklist No, Mac uses the regular Keychain which has similar stability as the Windows credential store.
Only one implementation, access is always consistent with user login state.But only restoring parts of a backup will create the same inconsistency of browser data and encryption key there as well.
Here: Vivaldi user profile copied to essentially a new install without the required key in the User keychain. -
@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]