| Summary: | www-client/chromium-87.0.4280.20-r1 with wayland enabled doesn't work in wayland. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Justin W <gentoo.org> |
| Component: | Current packages | Assignee: | Chromium Project <chromium> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Justin W
2020-10-25 12:33:01 UTC
I'm running into this as well - [~]>chromium-browser Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not work as expected [605001:605001:1027/124552.993874:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization [605073:605073:1027/124553.036814:ERROR:egl_util.cc(89)] eglGetProcAddress not found. [605073:605073:1027/124553.047046:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization [605197:605197:1027/124553.084408:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Startup hangs there. That said I can the open chrome windows in a new terminal, but chrome://gpu has accelleration all disabled. Not sure what to make of this. (In reply to Joe Kowalski from comment #1) > I'm running into this as well - > [~]>chromium-browser > Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", > line 10: Having multiple values in <test> isn't supported and may not work > as expected > [605001:605001:1027/124552.993874:ERROR:viz_main_impl.cc(150)] Exiting GPU > process due to errors during initialization > [605073:605073:1027/124553.036814:ERROR:egl_util.cc(89)] eglGetProcAddress > not found. > [605073:605073:1027/124553.047046:ERROR:viz_main_impl.cc(150)] Exiting GPU > process due to errors during initialization > [605197:605197:1027/124553.084408:ERROR:sandbox_linux.cc(374)] > InitializeSandbox() called with multiple threads in process gpu-process. > > Startup hangs there. That said I can the open chrome windows in a new > terminal, but chrome://gpu has accelleration all disabled. Not sure what to > make of this. I think your issue is different, but need version and emerge --info at least. What wayland desktop are you using? AFAICS chromium does not honor GDK_BACKEND. Either run "XDG_SESSION_TYPE=wayland chromium" or "/usr/lib64/chromium-browser/chrome --ozone-platform=wayland". This is on sway - but now with www-client/chromium-87.0.4280.27 I can no longer reproduce and chromium works fine with all the gpu acceleration working. This remains an issue on 87.0.4280.66 with no other changes to the system. No permutation of GDK_BACKEND, XDG_SESSION_TYPE, nor --ozone-platform have any bearing on the outcome. (I am also using sway, and all other wayland-native apps work as expected.) |
