Code change:
Describe the bug from should have fledgling Ozone/wayland support. Users on other distros are having success. However, I am not. Looks like it might be a Nix-y thing: and no window opens.
I had it working once: (didn't re-test lately tho) It might also be a hardware/driver thing (changing might also help if it's related to any local state). Do you get any additional output (I usually get way more output)? Or it might be due to one of the many upstream bugs (). But if this is indeed related to Nix investigating/fixing it would be very nice.
too, saw it working once. , local state does affect it. I was having a totally different crash until I deleted . used to get more output, but no, that's everything, verbatim what I get from launching yesterday. It very well could just be upstream, but I'm getting jealous of adhoc reports of those builds working on other distros. Unfortunately I don't have a lot of time/ideas.
Ok, strange. I just tried this again with 87.0.4280.66 and got the following output (in my case this looks as with previous versions that crashed though). <details<summaryConsole output (the 2nd time no browser window appeared anymore)</summary<pre[nix-shell:~/google-chrome]$ which google-chrome-stable /nix/store/j3v003nw7mkhdzys4wih1zvw2lsvm8cq-google-chrome-87.0.4280.66/bin/google-chrome-stable [nix-shell:~/google-chrome]$ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland [(43)] (initialize): ANGLE Display::initialize error : Could not open the default X display. [(773)] EGL Driver message (Critical) eglInitialize: Could not open the default X display. [(1322)] eglInitialize OpenGL failed with error EGLNOTINITIALIZED, trying next display type [(43)] (initialize): ANGLE Display::initialize error : Could not open the default X display. [(773)] EGL Driver message (Critical) eglInitialize: Could not open the default X display. [(1322)] eglInitialize OpenGLES failed with error EGLNOTINITIALIZED [(20)] GLSurfaceEGL::InitializeOneOff failed. [(150)] Exiting GPU process due to errors during initialization [(621)] Failed to call method: org.freedesktop.DBus.Properties.Get: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(621)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(621)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(374)] InitializeSandbox() called with multiple threads in process gpu-process. [nix-shell:~/google-chrome]$ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland [(621)] Failed to call method: org.freedesktop.DBus.Properties.Get: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(621)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(621)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: objectpath= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [(43)] (initialize): ANGLE Display::initialize error : Could not open the default X display. [(773)] EGL Driver message (Critical) eglInitialize: Could not open the default X display. [(1322)] eglInitialize OpenGL failed with error EGLNOTINITIALIZED, trying next display type [(43)] (initialize): ANGLE Display::initialize error : Could not open the default X display. [(773)] EGL Driver message (Critical) eglInitialize: Could not open the default X display. [(1322)] eglInitialize OpenGLES failed with error EGLNOTINITIALIZED [(20)] GLSurfaceEGL::InitializeOneOff failed. [(150)] Exiting GPU process due to errors during initialization [(374)] InitializeSandbox() called with multiple threads in process gpu-process. [(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsgCreateCommandBuffer. </pre</detailsYou're right, I just tried the exact same version but with instead of and it works pretty flawlessly (videos don't play but the rest seems fine). So this issue only seems to affect Google Chrome. Also: With Chromium I don't get any of those error messages on the console that I get with Google Chrome (only the usual ones as in your initial post, not the ones related to ANGLE/EGL/X11).
Since we will lose some Google account related stuff in chromium quite soon[1], I am looking into using Chrome for some stuff. At the moment I am using Chromium via and it is wonderfully fast and smooth (sway, nixos-unstable, intel-gpu), even though I have to disable something about video acceleration[2]. None of the three Chrome builds start with as reported in this Github issue. When also adding it runs (as a Wayland window), but the performance is bad. [1] ,-By%20Joey%20Sneddon&text=Users%20of%20the%20Chromium%20web,builds%20from%20March%2015%2C%. [2]
could you also report your Wayland compositor and GPU? Maybe that's related. I did test this on Sway and Weston (IIRC) with an old AMD Radeon HD 6950 GPU (Mesa's Radeon R600 Gallium3D Driver). I've also started following a few upstream issues that could be related: (seems Nvidia specific though) (reproducible on wlroots-based compositors) I'm still not sure if this is an upstream issue, GPU driver or Wayland compositor related issue, or Nixpkgs specific (either due to our Chromium packaging, due to some specific system dependencies, or due to issues with our Nix store paths). if you want you could also try to investigate this with e.g. (IIRC I briefly had a look but it's not a priority for me since I don't use Google Chrome).
I am on sway/wlroots/intel-gpu. I'll look into strace, but I fear my Linux debugging skills are a bit rusty.
I am not able interpret the output in any meaningful way, but I was able to get some more log output: conincides with
Wayland works on latest unstable chrome, but rendering falls back to software. Log Messages
It stopped showing window once I close and re-run chrome, but after removing it starts working again.
Current output, just for the record (GPU driver: , flags: ). Current output of (only works via ): Note: This obviously shouldn't try to open the X display. Current output of (doesn't work at all):
I have it working on stable 91.0.4472.114 with just the ozone platform flags, but there's no hardware acceleration at all.
that might be equivalent to the case then (which also works reliably but without hardware acceleration). For M92+ the situation is currently even worse as the GPU acceleration seems to be broken. I need to use to even launch Chromium or Google Chrome (unfortunately I lack time for a proper investigation but at least there are already some upstream bug reports).
With Google Chrome M92+ the Ozone/Wayland support seems to be completely broken on NixOS (coredump during startup): Chromium is still fine though. I've opened since there's also a nasty GPU acceleration regression now.

Related discussion:
text: liberation_ttf curl util-linux xdg-utils wget flac harfbuzz icu libpng opusWithCustomModes snappy speechd bzip2 libcap at-spi2-atk at-spi2-core <del> libkrb5 libdrm mesa coreutils </del> <ins> libkrb5 libdrm libglvnd mesa coreutils </ins> libxkbcommon pipewire wayland ] ++ optional pulseSupport libpulseaudio ++ optional libvaSupport libva