Hello,
Since upgrading to Vivaldi 6.7.3329.17-1 yesterday, it does’nt start anymore, and, in Wayland, fails with :
❯ vivaldi
libva error: /usr/lib/dri/i965_drv_video.so init failed
[0427/094435.575420:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.575673:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.575765:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.576728:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.578172:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.583825:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.583938:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.585403:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.586148:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0427/094435.586273:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Erreur de segmentation (core dumped)
It also fails in X11 with the same errors, except for the first one.
Similar issues appear aswell, but I did not get segmentation faults.
Instead a blank window opened
Resetting .config/vivaldi-stable.conf did not help.
Might also be updates to nvidia / mesa (dual GPU setup)
libva error: /usr/lib/dri/nvidia_drv_video.so init failed
[2654:2654:0427/095353.425001:ERROR:gl_display.cc(515)] EGL Driver message (Critical) : eglCreateImage failed with 0x00003009
[2654:2654:0427/095353.425085:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_BAD_ALLOC
[2654:2654:0427/095353.425166:ERROR:native_pixmap_egl_binding.cc(109)] Unable to initialize binding from pixmap
[2654:2654:0427/095353.425230:ERROR:ozone_image_backing.cc(365)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[2654:2654:0427/095353.425284:ERROR:shared_image_manager.cc(229)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[2654:2654:0427/095353.425642:ERROR:gpu_service_impl.cc(1124)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[2613:2652:0427/095353.446443:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it.
[2613:2652:0427/095353.446458:ERROR:one_copy_raster_buffer_provider.cc(347)] Creation of StagingBuffer's SharedImage failed.
There is no issue with Vivaldi; at least, none that I can see - the same version starts here without issue after the update. The issue will likely be specific to your own configuration, and related to the very first libva error. There are a few (somewhat dated) similar issues with libva, which might give a few clues, however:
While your input is appreciated, in future, please start (your own) new thread and detail your problem so that others can help more effectively with your specific issue; rather than attempting to hijack another poster’s thread.
As a new user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit. To that end, some or all these links will be invaluable:
And last, but not least, the Stable Update Announcements, which you should check frequently for important update related information. Occasionally an issue might be directly related to a particular update; it’s always best to check those announcements.
Hello,
As I said, I get the “libva” error only in Wayland, in X11 it crashes the same, without the libva error.
I incriminate Vivaldi because my Manjaro system has been running for years without any issue, and Vivaldi started failing after one upgrade that involved only Vivaldi and not the kernel or any graphics library…
Also, a bit like @tobenderZephyr stated, when I start Vivaldi using the icon/menu, I get a blank Vivalvi Window that opens and immediately closes, but when I start it from the command line, I get the errors and no window even opens.
Hello and thanks for the introduction. Sorry for the interruption - I should really have had a look at those posts beforehand, but I was guessing, this issue was similar enough.
I really do not want to de-rail this thread since I just figured, that my errors are related to this change in chromium based browsers. I’m unsure if starting vivaldi with command line parameters helps the OP, just wanted to give a hint.
And yet, as already pointed out, Vivaldi has no issue here - I use Wayland exclusively. This strongly suggests the problem is not with Vivaldi (but perhaps something interacting with Vivaldi); something else.
In as far as I’m able to guess, the link that @tobenderZephyr has mentioned, which leads to this post is a likely candidate; which would also indicate it is not a Vivaldi issue. Vivaldi, being chromium-based, may only be exhibiting a symptom of the problem.
However, that post is from the Testing Update announcements. If you are using the Testing branch, then it becomes a possibility, however, you have not specified which branch you are using.
At least with this new information, the issue might be easier to diagnose. Unfortunately, not by me, as the errors are non-existent.
Cheers.
You’re already here, so there’s little sense in back-peddling now. The link you gave might well be related - in fact, it even seems likely, now that @petaramesh has added some more detail.
Cheers.
It harms nobody to spell things out.
Appendum:- I am error-free using Wayland and AMD graphics. Perhaps this only manifests on Nvidia (guessing).
I don’t expect to need typing specific command-line parameters for starting my browser, everybody does it by clicking on a menu icon, and the Vivaldi desktop menu entry file doesn’t use any option.
The issue appearing after years of no-issue just after a Vivaldi browser update, I’m quite confident the issue is with Vivaldi.
Chromium still works perfectly on my system, so it does not seem like an issue that “all chromium browsers” would have.
It complains about the i915, so the graphics driver is obviously Intel, not NVidia or AMD.
To what command-line parameters are you referring?
OK. Let me extrapolate. I (and others) am using the same Vivaldi browser; the same version; and just had the same update - yet, I (and others) are not experiencing the same issue. Good so far?
This indicates that it is not a problem with Vivaldi, but a condition specific to your machine (and likely a few others) that is triggered by something interacting with Vivaldi. If the problem was specifically with Vivaldi, I would have it too; unless it was something present on your machine that is missing from mine (thus my pondering interest in graphics). That also might indicate the ‘something else’ as the culprit.
Incidentally, both Chromium and Microsoft Edge (the only Chromium-based browsers I have apart from Vivaldi) also work without issue.
The links were found quickly, and may have served as an indicator to the problem, regardless of their age. As stated:
The link that @tobenderZephyr gave, nonetheless describes an issue similar to what you experience (as you volunteered after seeing the information):
I don’t know what more to add, that might allow you to follow the logic.
All I can do is to wish you luck.
Certain configurations may be necessary given certain system parameters.
Even if you ‘refuse’ to “need typing specific command-line parameters for starting your browser”, you may have things you need to put in place, or maybe as a troubleshooting step you could ascertain your current options or try new ones.
For example … as mentioned … wayland.
And look - you are using wayland.
Example of other chromium based browser … in this one brave;
Or here on the forums, as was already linked above;
Since you are on wayland you probably should set the wayland flags.
Or the other way around and force it to run on X11 using … the X11 flags.
Both can be set in the GUI and/or permanently.
But its still important.
Well, I said I had the issue in Wayland and I also said I also had the issue in X11.
As a side note, I don’t recall having had such unpleasant and harsh interaction on the Manjaro forums before today, and it started with answer #3.
That comes as a surprise to me.
People replying to other people they don’t know, from their heights, as if the others were complete morons, I’m not sure this fits with the forum guidelines.
Guys I’ve been an IT professional for more than 40 years and a Linux professional since 1996.
Hi petaramesh,
Since this thread was the first time ever posting here; I just want to hint into using the flags, perhaps you have set vivaldi with vivaldi://flags before to use wayland and you did not do that for chromium for whatever reason.
After launching vivaldi with the flag posted multiple times before, It started working for me again, and I was able to undo the vivaldi://flag setting. It might just be, that this option persisted the update to your browser and prevents you now from launching it without specific command line overrides.
I was unable to test the theory as my Vivaldi (v6.7.3329.17-1, on Wayland) simply does not exhibit any issue remotely similar to what was described.
It’s great to know that these flags mentioned (multiple times) do indeed solve the issue for you. Now, if the OP might also resolve to follow your lead, we might be able to mark this thread as solved.
To that end, and for convenience, here are the related links that support the conclusion:
The post from @tobenderZephyr (in this thread), finally confirming the resolution.
I’ll overlook the attempt, even though it was clearly aimed at me - I could easily be harsh, if it’s needed, but I’d prefer to simply help wherever possible, as I (and others) have been, despite your resistance.
If you’re happy to use the progressively proposed (and now, it seems confirmed) solution; and it solves your issue; may I suggest marking the post from @tobenderZephyr as the solution. It was he that kindly linked to the information in the first place (not bad, for a new member).
The link you gave might well be related - in fact, it even seems likely, now that 
)