Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ungoogled-chromium 92.0.4515.159 crashes with wayland flags #137688

Closed
colemickens opened this issue Sep 13, 2021 · 6 comments
Closed

ungoogled-chromium 92.0.4515.159 crashes with wayland flags #137688

colemickens opened this issue Sep 13, 2021 · 6 comments

Comments

@colemickens
Copy link
Member

Describe the bug

~
❯ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[281477:281477:0913/134642.439438:ERROR:cursor_loader.cc(115)] Failed to load a platform cursor of type kNull

(chromium:281477): Gtk-WARNING **: 13:46:42.481: Theme file for capitaine-cursors-white has no directories
[281513:281513:0913/134642.514926:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is egl
[281513:281513:0913/134642.519897:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[281477:281477:0913/134642.591404:ERROR:platform_shared_memory_region_posix.cc(47)] Descriptor access mode (0) differs from expected (2)
zsh: trace trap (core dumped)  chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

~
❯ which chromium
/etc/profiles/per-user/cole/bin/chromium

~
❯ readlink -f $(which chromium)
/nix/store/ilhrxff0xz1dfh3jlr8hr7yvngyj4l0w-ungoogled-chromium-92.0.4515.159/bin/chromium

cc: @primeos

@colemickens
Copy link
Member Author

seems like this might just be upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1246834

@berbiche
Copy link
Member

berbiche commented Nov 8, 2021

Looks like the fix is available in Chromium beta (tested 41dbc0a)

@ja0nz
Copy link

ja0nz commented Nov 16, 2021

Aaaand in the stable a39908a

@danielphan2003
Copy link

Does this also apply to electron? I hit the same thing and have to use Xwayland instead.

@teutat3s
Copy link
Member

teutat3s commented Mar 31, 2022

It seems it does, at least I'm in the same boat. But for electron_17 with version 17.3.1 a fix is in sight: #166587 and upstream: electron/electron#33499

EDIT: sorry for hijacking this issue about chromium, I guess we can close this one?

@primeos
Copy link
Member

primeos commented Apr 1, 2022

I guess we can close this one

Yes, seems like it :)

Does this also apply to electron?

#158175 ;)

@primeos primeos closed this as completed Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants