vivaldi://settings/passwords Frozen

  • I just migrated everything from a late-2012 iMac to mid-2017 iMac. Vivaldi functions perfectly and seems to have ported bookmarks, history, passwords and whatnot without a problem. But the vivaldi://settings/passwords screen (and also the chrome://settings/passwords) screen displays the information, but none of it is clickable.

    On the old Mac vivaldi://settings/passwords screen, I can click in the search bar, or the eye icons, websites, slide buttons and other stuff, but in the newly migrated computer all of that is completely non-functional.

    Here is the new install info:

    Vivaldi 1.14.1077.60 (Stable channel) (64-bit)
    Revision 44919e4fea5e7e6a209f00d1780f799bf211e559-
    OS Mac OS X
    JavaScript V8 6.4.388.46
    Flash /Library/Internet Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin
    User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.189 Safari/537.36 Vivaldi/1.95.1077.60

    Old Mac has Vivaldi 1.14.1077.55, as I have been reluctant to roll it forward. settings/passwords works fine on that computer.

    Any suggestions?

  • Moderator

    Did you basically copy the raw Vivaldi profile files from one computer to another?

    If so, that should work... but Vivaldi's passwords are stored encrypted... so you also have to transfer the decryption key as well. It's stored in the macOS Keychain in Chrome Safe Storage. You can use "Keychain" to display the original encryption password and to transplant the password into Chrome Safe Storage on your new Mac.

  • @xyzzy Regarding this - wasn't there the plan to change from "Chrome Safe Storage" to "Vivaldi Safe Storage" a few SS releases ago? As far as I remember, this was the reason that one or two SS releases were not available for Mac.

    So the switchover has not yet been implemented?

  • Moderator

    @morg42 No, the switch to "Vivaldi Safe Storage" has not been implemented yet. Some problems were discovered during testing which is why a Mac snapshot was withheld and the change got rolled back. You can't be too cautious when it comes to anything involving passwords and data.

    I think the revised code has been ready for release for a while now but this is also something that you would want to implement at the very beginning of a Snapshot cycle... and communicate in advance. With Sync also in place by the time this rolls out, it will provide an additional safety-net to mitigate potential and unforeseen risks as well.

  • Hi Folks,

    I used the Mac utility to transfer the entire computer from a Time Machine backup. Vivaldi is working properly, with bookmarks and settings remembered.

    The passwords are all present and functional in the new install. They are correctly remembered into various login screens and they work to log in. What does NOT work is ANY feature on the vivaldi://settings/passwords screen that should be clickable: search pw field, slide buttons, web page links, and the eye icons.

    It's like viewing a jpg image of the page rather than the interactive page itself. Very strange.

  • Moderator

    @stevek I checked in with the Vivaldi team this morning but they didn't have any immediate thoughts as to what could be causing this. They asked if your passwords were visible from the Vivaldi UI in "Vivaldi Preferences / Privacy / Passwords".

    The only other suggestion that I can offer is to verify that your Vivaldi installation transferred correctly:

    You can check the integrity of the Vivaldi application bundle using:

    $ spctl -a -vv /Applications/

    ... and you should see the following:

    $ spctl -a -vv /Applications/
    /Applications/ accepted
    source=Developer ID
    origin=Developer ID Application: Vivaldi Technologies AS (4XF3XNRN6Y)

    The spctl command performs the same checks as the macOS Gatekeeper. If you see an error such as:

    /Applications/ rejected

    ... then your Vivaldi installation got messed up; you should download Vivaldi again from (using Safari), delete /Applications/ , and re-install it.

    Since this is a "cloned" installation, you should double-check the "Chrome Safe Storage" entry in the macOS Keychain using /Applications/Utilities/Keychain -- the passwords stored on both systems should match and "/Applications/" should be in the Access Control list.

    The only other place where Vivaldi stores files (such as its Profile and Cache files) is in various subdirectories in ~/Library. There's no good way to validate their integrity. However, if the previous tests pass and a new Vivaldi installation works in a test account, then the problem is (most likely) something here.

    The only other remote possibility (if everything transferred properly) is something hardware-specific in your Vivaldi profile... although I don't know what that could be... and if this were the case, I would expect to see a different set of problems/errors, not a non-functional password management UI.

    Best of luck with your troubleshooting!

  • @xyzzy Thanks for the detailed suggestions.

    1 - Vivaldi Preferences/Privacy/Passwords shows only website and account (login ID) on both computers and on fresh install to test account. To my knowledge that has always been the case for the Mac version. No idea about Windows versions.

    2 - Integrity spctl check is 100% pass, shows everything above to the letter. No rejected errors.

    3 - shows identical passwords on both machines for Chrome Safe Storage

    4- Created test account on new iMac, did fresh download of using Safari. Installed, accessed FB account, asked it to save PW. Went into vivaldi://settings/passwords and everything worked.

    5- Logged back into main account. Closed, then Deleted from main account applications, did fresh download of Vivaldi using Safari. Copied into Applications folder. Started Vivaldi. Problem continues - no actions possible on vivaldi://settings/passwords screen.

    I note the devs are presumably doing something with this UI page (see comments in post below).

    I had enabled these 3 on the old iMac (they still are, but buttons gone as per comments in the post above):

    alt text

    Set to default, restarted, no change.
    Set to disabled, restarted, no change.

    Is this basically hopeless? Without this functionality, I shall have to abandon the browser entirely.

  • Moderator

    @stevek It's not hopeless at all. I think there's something in your Vivaldi profile that's causing Vivaldi to glitch on your new system.

    There are a few things that you can do to "reset" Vivaldi but first, make a backup. Vivaldi stores its files in the following places in ~/Library:

    • Application Support/Vivaldi
    • Caches/Vivaldi
    • Caches/com.vivaldi.Vivaldi
    • Preferences/com.vivaldi.Vivaldi.plist
    • Saved Application State/com.vivaldi.Vivaldi.savedState
    • WebKit/com.vivaldi.Vivaldi

    (The most important files, including your Profile, are stored in ~/Library/Application Support/Vivaldi)

    To double-check that there's nothing more on your system:

    $ cd ~/Library
    $ echo */Vivaldi */com.vivaldi.*

    Then, you can try whatever you want to "reset" Vivaldi and still be able to get back to exactly where you started. (Perform the backup after quitting Vivaldi.)

    Here are some options to consider:

    If you delete all of these files and directories, it will be like a brand new Vivaldi installation.

    You can also try to Clean/Refresh your profile:

    Another option is to wait until Vivaldi 1.15 gets released to the Stable channel. At that point, Sync should be available for everyone. You can then Sync all of your passwords and data on your old system, reset Vivaldi on your new system back to a clean state, then sync the Sync'ed data to your new system.

  • Moderator

    @stevek I just had another thought as to what might have caused some of your issues. It's likely that the Time Machine backup was made while Vivaldi was running. When the backup was restored to your new system, the Vivaldi profile was not in a clean state.

    Just a guess.

  • @xyzzy When the backup was made, Vivaldi absolutely was running. Any ideas how to correct? I can make a new TimeMachine backup with everything off, but I don't want to wipe the new machine, just reinstall Vivaldi. Not sure this is possible.

    Would manually copying all the Library directories to a drive and then writing them over the existing ones work?

  • Moderator

    @stevek It's probably enough to backup ~/Library/Application Support/Vivaldi

    On the new system, rename ~/Library/Application Support/Vivaldi to Vivaldi_save, then copy the directory from the old system to the new.

    It doesn't matter how you transfer the directory... you can make an archive of the directory to a backup file using either zip or tar, copy the directory to a USB stick, or copy the directory to the new machine over the network. The advantage to backing up with zip or tar and then transferring the archive file is that the file permissions and links will be preserved.

    Here's an example of how to do this:

    On the old system, Quit Vivaldi, then:

    $ cd ~/Library/Application\ Support/
    $ tar cvf /tmp/Vivaldi_backup.tar Vivaldi

    Copy /tmp/Vivaldi_backup.tar to a USB drive, then transfer the file to your new system.

    On the new system, Quit Vivaldi, then:

    $ cd ~/Library/Application\ Support/
    $ mv Vivaldi Vivaldi_save
    $ tar xvof Vivaldi_backup.tar

    Hopefully, that will be enough to get Vivaldi back into a good state again on your new system.

  • @xyzzy Sorry, no luck.

    Followed the process and used the tar file.
    It did set Vivaldi open windows/bookmarks/saved PW to the state on the old Mac, but still nonfunctional GUI on passwords.

    It was worth a try.

    I probably cannot keep the old Mac until 15 comes out - there is a person waiting for it. Not sure it would fix this particular issue anyway.

    Kinda feeling that the problem is embedded somewhere in the Vivaldi setup or config, as the test account new install seems to work (so not a HW or OS issue). And with export now non-functional, I'm looking at typing in 200+ entries, one browsed page at a time - if I wipe the setup and start with fresh Vivaldi. Not elegant, but a solution of sorts.

  • Moderator

    @stevek Are logins/passwords and bookmarks the most critical parts of your Vivaldi installation? (Bookmarks are easy to export and back up.) If so, a "last resort" option on your new system is to reset Vivaldi to a "like new" state, perform a basic setup, import your bookmarks, then copy...

    "~/Library/Application Support/Vivaldi/Default/Login Data"

    ...from your old system to your new system. If that doesn't work, then I'm totally out of suggestions.

    Before you give away your old Mac, I would definitely make a good backup copy of all the Vivaldi files in ~/Library and archive the "Chrome Safe Storage" password in your Keychain.

    I would also consider upgrading Vivaldi 1.14 (stable) to Vivaldi 1.15 (snapshot) and using that version to Sync your Vivaldi passwords and other data before wiping your old system clean. When Vivaldi 1.15 gets released, the data will be "in the cloud" ready to be sync'ed back.

    These are just ideas...

    Hopefully others will be able to offer you additional suggestions as well.

  • @xyzzy The answer is login/pw and bookmarks are indeed the most critical.

    Great news, this last suggestion to wipe Vivaldi libraries, start the app in clean state, import bookmarks, and copy over the Login Data file WAS SUCCESSFUL!

    I now have all bookmarks and login/pw data imported and functional and the vivaldi://settings/passwords screen is also functioning normally.

    I appreciate your patience and creativity in working the issue with me.

    Re-setting the window arrangements and 30-ish active pages for work is a much smaller task than accessing 300+ websites and redoing login/pw saves, so I am good with it.

  • Moderator

    @stevek Yay!!! I'm glad to hear that things are working for you again!

    Thanks very much for your patience as well.

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.