Call for testing: chromium snap

[pop]

Thanks for the package! I just tested --candidate version on Ubuntu 16.04 with the latest (unreleased) snapd 2.27.2.

This gets printed when I launch it:

Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"

Also opening downloaded files and show in folder aren’t working (xdg-open).

Here’s the full log but other than this it seems to work well.

[2708:2855:0817/133911.887059:ERROR:udev_watcher.cc(60)] Failed to begin udev enumeration.
[2708:3426:0817/133936.724692:ERROR:object_proxy.cc(573)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.91" (uid=1000 pid=2708 comm="/snap/chromium/5/usr/lib/chromium-browser/chromium") interface="org.freedesktop.UPower" member="GetDisplayDevice" error name="(unset)" requested_reply="0" destination="org.freedesktop.UPower" (uid=0 pid=1342 comm="/usr/lib/upower/upowerd ")
[2708:3426:0817/134002.193913:ERROR:object_proxy.cc(573)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.92" (uid=1000 pid=2708 comm="/snap/chromium/5/usr/lib/chromium-browser/chromium") interface="org.freedesktop.UPower" member="GetDisplayDevice" error name="(unset)" requested_reply="0" destination="org.freedesktop.UPower" (uid=0 pid=1342 comm="/usr/lib/upower/upowerd ")
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.SafeLauncher was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.SafeLauncher was not provided by any .service files
[2708:2861:0817/134333.618247:ERROR:service_manager.cc(142)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser

[ogra]

@pop

Also opening downloaded files and show in folder aren’t working (xdg-open).

xdg-open inside snaps is currently limited to http/https and help protocols … details about a re-implementation are at:

Integrate snapd-xdg-open into snapd repository

Hey everyone, as part of my cross-distro work I am now also looking into snapd-xdg-open and wondering if it would make sense to integrate it directly into the snapd source tree similar to what we do for snap-confine. From my point of view this would simplify the maintenance process and we can release it together with snapd instead of keeping it separate and following its own release cycle. Currently we miss a proper test setup and release process for. The git repository was never tagged yet an…

[oSoMoN]

@ogra

xdg-open inside snaps is currently limited to http/https and help protocols …

Beside this limitation, there is also that bug that prevents xdg-open from working at all at the moment.

[ogra]

oh, right, i thought 2.27.2 was released already but it is only in beta/candidate yet…

[oSoMoN]

I have just pushed a new version of the chromium snap to the candidate channel, with a fixed setuid sandbox and additional fonts for CJK and Thai language support.

Please keep the useful feedback coming!

[om26er]

@oSoMoN

Also note that the snap is currently published under my personal account, but we will soon transition to a shared account for the Ubuntu desktop team, meaning that the snap will receive official support.

Can we do some diplomacy and get the packaging upstream, is there a chance for that ?

Also why is the size difference between candidate and beta version relatively huge ?

  candidate: 60.0.3112.101 (9) 244MB -
  beta:      61.0.3163.39  (1) 151MB -

[oSoMoN]

@om26er

Can we do some diplomacy and get the packaging upstream, is there a chance for that ?

That would be great (and AFAIK there is an ongoing conversation with upstream already), but the snap package in its current form relies on the debian packages in a set of PPAs, so not useable as-is for an upstream snap. But it wouldn’t be difficult to change that to actually build chromium as part of the build process.

@om26er

Also why is the size difference between candidate and beta version relatively huge ?

See my comments from 5 days ago: I added fonts-noto-cjk and fonts-thai-tlwg to the stage packages, because we currently don’t have a mechanism to share fonts between snaps, unfortunately.
I did that in candidate only, but I will update the beta channel today and will add the fonts there too.

[oSoMoN]

Thanks everyone for the useful feedback. I have now promoted version 60.0.3112.101 to the stable channel. Enjoy and keep the feedback and bug reports coming (see the original post for instructions on how to file bugs with all the relevant information).

[oSoMoN]

And the beta channel has been updated to version 61.0.3163.49.

[Syntist]

I don’t know but any app that uses chromium (blink engine) not working for me,

[syntist@archlinux ~]$ snap run chromium
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
*** stack smashing detected ***: /var/lib/snapd/snap/chromium/13/usr/lib/chromium-browser/chromium-browser --type=gpu-process --field-trial-handle=4255232481339090463,5380338833867286810,131072 --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=611B56BFA1976FDFE69D1F1690617D5A terminated
Received signal 6
Received signal 11 <unknown> 000000000000

just a chromium window with black screen,

and same error with discord not showing!

Edit: Using Arch Linux.

[popey]

Confirmed chromium on antergos in Virtualbox gives me an un-rendered (empty) window, later (if left long enough) followed by a usual Chromium “Page unresponsive” dialog, also un-rendered.

file:///home/alan/VirtualBox_Antergos_22_08_2017_14_00_13.png

[Syntist]

Yeah i also get “Page unresponsive” Error.

[Hilikus]

Will this package work in Ubuntu snappy core?

[Syntist]

After The update (snapd snapd-2.27.3-1) Thanks to @zyga-snapd.

Its working now but the one problem remains, no HW Acceleration on my side.

Canvas: Software only, hardware acceleration unavailable
CheckerImaging: Disabled
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated but at reduced performance
WebGL2: Unavailable

[oSoMoN]

That snap currently requires X11, so I’m afraid not.

[Syntist]

I am using X11, gnome 3.24 x11 nvidia gpu.

[jdstrand]

@jdstrand

If, as a normal user, after adding the vmstat and udev rules

FYI, this will be in snapd 2.27.4: https://github.com/snapcore/snapd/commits/release/2.27

[Syntist]

Thats Cool , so maybe there can be steam snap also, it would be awesome as flatpak have it though.

would be great if this release support themes

[Kay]

I get a black window on Solus with Snapd version 2.27-4 and Nvidia proprietary drivers 340

Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
[10346:10437:0904/225759.744368:ERROR:udev_watcher.cc(60)] Failed to begin udev enumeration.

[popey]

Just tried chromium from edge on my nvidia machine and I get an un-rendered window now