-
Notifications
You must be signed in to change notification settings - Fork 23
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
Widevine Support #71
Comments
An Asahi only snap or asahi channel track in existing browser snaps are likely necessary, unless snaps are not used. We'll talk to the snap folks :) |
Is it not possible to manually copy the shared libs in the "chromium snap environement"? |
Something like that should work. For Ubuntu Asahi we want an upstream solution, and will help with that. From https://oftc.irclog.whitequark.org/ubuntu-asahi/2023-11-01 snaps based on core24 may be required for glibc dependencies. |
@eslerm I try to rebuild a proper chromium snap => switch to core24 => rebuilding gnome-sdk-asahi => rebuild gnome-sdk. So really not trivial, I think I will wait at least that gnome-sdk switch to core24 to go for the proper solution. For the dirty solution do I have to extract the squasfs -> patch the lib and repackage? Or do you see another solution? |
Manually copying should work. It can be done through snapcraft too. After unsquashing, you can rebuild and edit If there is a clean distribution system for asahi-widevine, there's a chance upstream browser's would o-k an asahi snap track. |
chromium flatpak should work (once you add Widevine in a place it is looking for) as it switched to a runtime with GLIBC 2.36+ (support for RELR, required by ChromeOS ARM64 Widevine) 3 weeks ago flathub/org.chromium.Chromium#346 |
Hi,
I have try the widevine installer from marcan with some fixes for sh, but it seems to not work with Chromium installed as a SNAP :(
https://github.com/clementperon/widevine-installer
Does someone try and had a success?
Thanks
The text was updated successfully, but these errors were encountered: