Vivaldi failed to launch on macOS 14
-
Having the same problem since yesterday. Vivaldi stopped working and never can be launched again.
MBA 2020, M1 chip. Latest OS installed. Snapshot is working, Vivaldi isn't. I am using Firefox now, which is completely flawless.
As I see, problem still remains unsolved.
-
I've been having a similar issue, and I'm glad I found this thread! Like others, removing the Preferences file didn't help. What did help, however, was to leave Vivaldi closed and completely disconnect my Mac from everything (no dock, no monitor, no external devices) and then start Vivaldi. Once it's started, it's running fine, which lends weight to the theory that it's a device enumeration issue. Hopefully that helps someone at least get going until the Chromium team can sort out a fix!
-
I've had the same problem for a few days now! When I click on the Vivaldi icon in the Dock, the icon jumps twice, then stops. I first suspected Sophos, which we use in my company, but on this thread I see that I have a configuration that might be concerned: I have a MacBook Air M1 2020, it's closed and plugged into a Dell external display, with a Logi external camera and a Plantronics headset. I didn't have this problem before.
For the moment I'm using Firefox, but next week I'll be on the move, so just with the MacBook Air, without an external screen or anything, I imagine Vivaldi will open up again... To be continued!
-
Solved!
I couldn't find the Preferences folder in that directory ("~/Library/Application Support/Vivaldi/Default"). There was nothing there at all that I could delete. But I did manage to fix the problem! Uninstalling and reinstalling Vivaldi didn't work, the new installation would just bounce in the Dock and close. But then I used AppCleaner to fully erase Vivaldi and then reinstalled. Using AppCleaner must have erased the Preferences folder, and the new install worked!
The MacBook was a 2020 M1 MacBook Air, no external displays, no non-Apple hardware. I wish I could have diagnosed the issue better for the developers, but it looks like the problem was with whatever is left behind with a normal uninstall of Vivaldi. AppCleaner's total scrub of Vivaldi allowed me to reinstall a working version.
Thank you all! Super appreciated, and I love Vivaldi.
-
Good!
For the future and to run Backups, look below to find out the Prefs file, it's hidden.--
Avoid
Data loss
Follow the Backup | Reset links below
Vivaldi Backup | Reset + Extra Steps
-
Thank you very much @bulkington !
I couldn't open Vivaldi despite all my attempts, but thanks to AppCleaner, (which I hadn't used in probably ten years!), I was able to delete Vivaldi completely and start from scratch, and it's working again!
If other people have the same issue, here is the link for AppCleaner : https://freemacsoft.net/appcleaner/
Thanks again!
-
I used vivaldi before and gave it up because it's buggy. After quite some time, I finally decided to give it a try again. It literally failed me again in less than one day. I know how hard it is to maintain this project as a small team. But browser is just not something we can play with. It must satisfy our working needs.
-
@micen This is true. Of course it would be interesting to be able to discover what is going wrong at your end, since you are having an experience which is not at all typical for the browser. You state categorically, "it's buggy." For my part, though I volunteer daily to find and test bugs in Vivaldi, I hardly ever can find any sort of bug at all. Of course I don't install modifications to it, don't use extensions, and don't tweak my OS in any way, either. So I only get to find out what sorts of bugs any other Windows user might encounter, and that's almost none at this stage.
You're on Mac, and MacOS creates substantially more issues for Vivaldi devs to conquer, but when they can identify them, they slay them.
-
@micen I'm on a Mac (as noted in my sig, an i5 Catalina system...) and have relied on Vivaldi as my primary browser since version 3.7. While there have been occasional glitches -even one goof!- the browser has been dependable for me, despite an increasing array of new features!
I hope your problems with Vivaldi are sorted out and solved soon: You're missing out on an exceptional experience!
-
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
-
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
Is just asking what the user did.
-
This post is deleted! -
@Zalex108 said in Vivaldi failed to launch on macOS 14:
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
Is just asking what the user did.
So is there a better solution to this problem that has been going on for a few months?
-
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
So is there a better solution to this problem that has been going on for a few months?
well, ... maybe ...
Please install a separate snapshot from our Desktop Snapshot stream at https://vivaldi.com/blog/desktop/snapshots/ . See if that reproduces the issue, either immediately, or after repeating the steps that may have triggered it, or after copying the entire profile from your Stable environment.
The current snapshots are based on Chromium 120, same as the current Stable Vivaldi v6.5.
However, one of the next snapshots (probably not the next scheduled one) will have the new Chromium 122 code base, which includes a new feature (which we've enabled), introduced in Chromium 121, that is supposed use a new system for the camera that bypass the entire code path that is causing the (suspected) camera device enumeration crash.
We would be very interested (and I am sure the Chromium team is, too) in learning if that does fix the issue.
-
FYI, The first Snapshot based on Chromium 122 was released last week. Please see if that solves the crasher problem related to device/Camera enumeration .
-
If I worked with Linux I would certainly be happy with such experiments. Under MacOs I expect things to work. Common sense also says that if other Chromium-based browsers don't have this problem, it probably can't be due to Chromium. There's also the problem that the window appears somewhere on the screen every time you start Vivaldi since... more than a Year - do you also wait until Chromium sort that out?
-
@SchlimmGenug If you read my posts above, you will learn that one reason Chromium developed the new feature is that they had reports about the issue almost a year ago (one of the affected users was a Google employee), and that the problem was so deep inside MacOS that it wasn't practical to discover how to fix it (Apple can make mistakes, too; there was references to reporting a possible related issue to Apple all the way back in OSX 10.15 beta).
-
Then all other browser manufacturers have probably found solutions to the problem since Catalina.
-
@SchlimmGenug The point is that the problem was reported happening to a Google(!) employee less than 12 months ago. If you are interested, see the bug report
And the relevant code is entirely upstream Chromium, we made no changes to it. We suspect it has something to do with MacOS drivers for the Camera in certain system configurations, but AFAICT even Google never figured out what the trigger was (and none of our internal Mac users or the volunteers was ever able to reproduce).
So, no, they did not find a solution for it using the old Chromium code, they had to write an entirely new feature which has been rolling out to about 1% of Chrome users in the past month or so, and they are now preparing to roll it out to all users.
The currently released v6.6 Snapshot builds based on Chromium 122 include this new feature and it is enabled by default, and we (and probably the Chromium team) are very interested to discover if that fixes the crasher for users that have the crash.
-
Yep just had this happen to me. MBA m1 2020, i right clicked a link and click open in Private Window and then had the app freeze. Force closed it. Wouldn't open again, same as others here.
Uninstall reinstall did nothing. Even updating macOS to sonoma 14.3.1 didn't help. Someone in this thread said to get Appcleaner and I used that, now Vivaldi works again.
This was incredibly annoying and I lost a lot of work, and extension data. Given this bug has been around for ages, and continues to occur, I'm hoping the dev team knows whats causing it
