Hi, I m having a problem with Ubuntu-frame and Chromium. I m using Ubuntu core and tried launching chrome but its not working. If i use flags i get this:
chromium --ozone-platform=wayland
[5621:5621:1114/152048.911254:ERROR:wayland_connection.cc(205)] Failed to connect to Wayland display: No such file or directory (2)
[5621:5621:1114/152048.911531:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform
[5621:5621:1114/152048.911541:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
I got it to work with sudo chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-dev-shm-usage --no-sandbox but this disables the sandbox.
I m really out of ideas on how to fix this so if someone has any ideas i would really appreciate that xD
I’m guessing that you are using the chromium snap?
Packaging applications for use on Ubuntu Core is a different proposition to packaging them for use on desktop. In particular, the snap needs to include a daemon app that starts the application.
The chromium snap is intended for desktop use and doesn’t have such a daemon and therefore won’t work as you hope.
In theory, someone could repackage Chromium for this usecase, but I’m not aware of anyone doing this.
The only browser snap I know of that support this usage is:
Hi @alan_g thx for the answer. I want to run the connect Signage chromium extension. Somehow i got it to work on WSL ubuntu 24.04. I need to use chromium unfortunately. Could i repackage it with a daemon or do you maybe have a workaround for that? I m pretty new to snaps and Ubuntu Core. Thx for the help
@derechtepapst that is possible, but will need more work than just adding a daemon app to the recipe. I don’t know all the problems you would encounter, but…
there will be issues because the daemon mode is different to running as part of a desktop session; and,
using browser-support with a daemon app needs approval from the store team. That includes both proving it is necessary and publisher vetting.