Vivaldi working only for user installing it again…
OK, we've been here before, and it just happened again: the latest version (1.14.1077.41) installs correctly, works fine for the user who installed it, but the permissions are broken, so only this user has any access to it, any other user cannot open the application. I tried to fix the permissions by making all directories readable and navigable, and all files readable and executable if they need it, but it didn't work: now Vivaldi crashes at launch.
As I said, this has already happened a few versions ago, you should really systematically test it in a multi-user configuration. Not everybody has one administrator user with which they're doing everything…
I'm on macOS 10.9.5 (but I doubt it is relevant, since it's obviously a permission issue).
@eb303 I just downloaded Vivaldi 1.14.1077.41, took a quick look at the permissions in the app bundle, and they seem to be okay.
Did this happen after an upgrade? If so, please try downloading the latest version from https://vivaldi.com/download/ , delete your current Vivaldi.app and reinstall from the install dmg file.
@xyzzy Ah, I should have thought of that… This way, it works indeed. I did install 1.14 via auto-update, it looks like it is the update that was broken.
I had the same issue yesterday on my mac (10.13.3). I have 3 profiles: primary admin and backup admin (for installs/updates) and a normal user account for everyday activities. Upgraded to 1.14.1077.41 via autoupdate. All seemed fine. Rebooted and logged into secondary admin account. Could not launch Vivaldi. Said I did not have permission and to check with my admin (<g>). Checked permissions (Command-I) and found that while primary admin had read+write, everyone else was read only. Changed everyone to read+write. Still could not launch. Added secondary admin and user with read+write. Still no joy.
I will try later today (uninstall plus install from the fully-downloaded file).
I also have two WIn7 SP1 systems -- will it suffice for me to download the complete file for upgrade, or do I need to uninstall first?
luetage last edited by
@shadow55 The whole application is replaced on update, no matter if it's an autoupdate or a manual one, just download and then put the original one in the trash.
I'm sorry, but I'm a little confused: if it makes no difference whether the update is via autoupdate or manual download/install, then a failed autoupdate installation should not be rectifiable by using a manual download (no?). And, if the whole installation is replaced via either method then one should be able to install over a current installation (no?) Or, by uninstall, you mean more than drop dragging/dropping the executable into the trash (deleting files in ~/Library/Appication Support, Caches, etc.)??
It's not that I don't enjoy update troubleshooting (you understand<g>); it's just with 4 operating systems and 5 systems, I would rather, if at all possible, minimize the time spent re-doing already done installs/updates.
luetage last edited by
@shadow55 We are on the mac forum here, so I can only talk about the procedures on macOS.
Autoupdate: If you let the application update regularly, the new Vivaldi version is being downloaded, placed in your applications folder, and the old one you had running up until now can be found in the trash.
Manual update: You download the application from the Vivaldi site to your designated downloads folder as
.dmgfile. You unpack the file and drag Vivaldi.app to the applications folder. At this point you have to delete (move to trash) the old Vivaldi application residing in your applications folder.
So yeah, I don't know -- I don't really see the difference. It's the same procedure, just the unpacking, copying and deleting is automated in case of an autoupdate.
Ain't computers grand(<g>)?
Just to let you know: I did a complete uninstall of all Vivaldi files in all profiles. Installed from a manually downloaded .dmg. Vivaldi is now working (properly) again in all profiles. Of course, I had to re-customize each profile. Tedious, but it works.
It will probably be a week or so before I get back on my Win7 systems, so I won't worry about them now. Most likely, I will download the install file and install over the current installation. If that doesn't work, I'll know what to do.
Thanks for your help.