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

Chromium doesn't seem to work with wayland, can't find asahi driver #7

Closed
kahlstrm opened this issue Jan 22, 2023 · 17 comments
Closed

Comments

@kahlstrm
Copy link

kahlstrm commented Jan 22, 2023

While using the 22.10 Desktop on my M1 Pro, I can't seem to manage to get wayland and chromium working (or rather chromium working at all).
Here is what i get with running chromium --ozone-platform=wayland:
log.txt

Sorry for bothering with this but I tried quite a lot of things but couldn't manage to get it working myself.

Steps to reproduce:

  1. sudo snap install chromium
  2. chromium --ozone-platform=wayland
@tobhe
Copy link
Member

tobhe commented Jan 23, 2023

Thanks for the report, I have noticed this before but found no satisfying solution so far. My current hypothesis is that this happens because of the mesa version bundled with the snap which does not support the asahi gpu driver. Disabling the gpu sandbox via --disable-gpu-sandbox seems to get us around this crash but fails with a new error.

@tobhe
Copy link
Member

tobhe commented Jan 23, 2023

Another issue I encountered with snaps in particular is that they are being build with an older version of patchelf internally which produces non-16k-compatible binaries so the easiest way around this for now is probably getting a non-snap package.

@kahlstrm
Copy link
Author

Yeah, I figured that might be the issue but it was quite difficult find an arm64 version of chromium without building it myself.

@kahlstrm
Copy link
Author

kahlstrm commented Jan 30, 2023

Actually fedora seems to have a functional .rpm so that could be converted using alien.

@nullbert
Copy link

nullbert commented Feb 8, 2023

Hi! Did you try converting the .rpm? I just installed the 110 RC build, on the off chance it was built with an updated environment. No go...

@nullbert
Copy link

nullbert commented Feb 8, 2023

Downloaded the .deb from debian with dependencies. Had some trouble with libevent, but forced the install and it works. I can now use the laptop as my daily driver. Thanks @tobhe!

@vicjonesold
Copy link

Any updates here? I’ve been using —no-sanbox for my chromium based applications

@tobhe
Copy link
Member

tobhe commented May 14, 2023

I am currently waiting for the latest chromium beta at https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source to hit arm64. With that we could get graphics support working out of the box by supplying our own patched gnome-sdk snap with asahi-mesa included.

I am still trying to figure out a distribution mechanism because snaps don't have a PPA equivalent and I don't know too much about snaps in general, but I have someone from the Ubuntu desktop team who might be willing to help us with that.

@clementperon
Copy link

@tobhe not possible to distribute it as a .deb in the tobhe-asahi ppa?

@tobhe
Copy link
Member

tobhe commented Jun 18, 2023

@clementperon that would be a solution but I am hesitant to do it because chromium comes with a huge maintenance burden. Maintaining our own would mean we have to seriously track security fixes and make sure we distribute them in time. Getting the regular version to work would give us all this for free.

@clementperon
Copy link

sudo snap install chromium --beta

works without any hack :)

I have also enabled sync features following this tutorial: https://www.learningtopi.com/sbc/chromium-sync/

@tobhe
Copy link
Member

tobhe commented Jul 13, 2023

Yes, I can confirm that it does work with the newest beta version :) Thanks for sharing @clementperon!

@eslerm
Copy link
Member

eslerm commented Jul 17, 2023

After sudo snap install chromium --beta and launching chromium from command line I get the output:

MESA-LOADER: failed to open apple: /snap/chromium/2535/gnome-platform/usr/lib/aarch64-linux-gnu/dri/apple_dri.so: cannot open shared object file: No such file or directory (search paths /snap/chromium/2535/gnome-platform/usr/lib/aarch64-linux-gnu/dri, suffix _dri)
failed to load driver: apple
[67267:8:0713/193556.086415:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

/snap/chromium/2535/gnome-platform/ does not exist /snap/chromium/2535/usr/lib/aarch64-linux-gnu/dri/ does not contain apple_dri.so. Likely an issue in the upstream snap. Possibly related to #47

@tobhe
Copy link
Member

tobhe commented Jul 17, 2023

I think we need to build our own gnome-sdk snap with our mesa i+ driver ncluded. I remember talking to someone who managed to get that working for the Lenovo x13s which has a similar problem.

@clementperon
Copy link

Ok so it fallback automatically on swrast on Chromium but not on Electron app right ?

@clementperon
Copy link

With latest update snap gnome-42-2204 as change track to asahi/stable and it works fine!

Thanks a lot @tobhe

@eslerm
Copy link
Member

eslerm commented Oct 29, 2023

Thank you @clementperon :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants