Call for testing: chromium snap


#41

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

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

#42

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


#43

I am using X11, gnome 3.24 x11 nvidia gpu.


#44

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


#45

Thats Cool :smiley: , 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 :stuck_out_tongue:


#46

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.

#47

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


#48

I’ve just installed the chromium snap on Solus and I only get a black screen. Anything I can do to debug this?

:slight_smile:


#49

Is this with nvidia hardware and proprietary drivers?

Can you look for apparmor denials in the syslog?


#50

Sometimes, by chance, I don’t know if it happens after an update, I find myself a tab open on the dock and a card not visible on the dock.
A little while ago I discovered I had another chromium open browser card, thanks to alt tab.
The problem never occurred in the “.deb” version.

Ubuntu 19.04

$ snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more stable way for all
Internet users to experience the web.
commands:

  • chromium.chromedriver
  • chromium
    snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
    tracking: stable
    refresh-date: today at 20:53 CEST
    channels:
    stable: 75.0.3770.80 2019-06-12 (750) 162MB -
    candidate: 75.0.3770.80 2019-06-06 (750) 162MB -
    beta: 75.0.3770.87 2019-06-11 (754) 162MB -
    edge: 76.0.3809.21 2019-06-12 (758) 160MB -
    installed: 75.0.3770.80 (750) 162MB -

snap connecionts: https://paste.ubuntu.com/p/wCyNMBwW5V/ -

Log: https://paste.ubuntu.com/p/XmD2GgJV6K/


#51

This is a known issue, which is actively being worked on.


#52

The GTK+ theme is not working for me in Ubuntu 19.04 with Yaru when not choosing not to show the system window border (CSD?).
Classic theme works fine, but when setting Chromium to use GTK+ theme, it displays a white window border where only the close button is displayed, the minimize and maximize buttons are only shown on hover.
See the attached screenshot. The mouse is hovering over the maximize button.

Interestingly, the theme work fine if the Chromium window is unfocused…


#53

This is also a known issue: bug #1800260.