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.
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: Bugs : chromium-browser package : Ubuntu
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:
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ā¦
January 2021. Chromium snap is still in a very bad shape:
All channels point to 88, but Edge. And Beta is even older than Stable (88.0.4324.87 vs 88.0.4324.96). Channels should represent actual Chromium channels and their versions: Beta is 89, Canary is 90 right now.
GPU acceleration doesnāt work and right GL patches arenāt applied, works in Chrome.
Video decode doesnāt work, now works in Chrome after enabling the flag (20% CPU utilization on 1440p@60 video).
Instead of one of the most important snaps we have a ā4KB Challengeā.
Thatās incorrect, beta on linux is currently 88.0.4324.96, and dev is 89.0.4389.9, which is what the edge channel is tracking (see https://omahaproxy.appspot.com/). There is no canary for linux.
Yes, Iāve made a mistake and 89 is Chrome dev (not beta), but it doesnāt discard my point. Chromeās definition of canary (a bleeding edge version) is what SnapStore usually names as edge. SnapStore supports custom channel names, why not to make dev? And if thereās really no way to build canary, then just build master as edge. And remove the candidate if it isnāt used.
Shouldnāt be the stable the same as previous beta release, but without the suffix in name? Not sure if it makes sense to keep an entire channel purely for testing this build step.
The candidate channel is often used by developers to push a build before going to stable. It allows them to make a public āreleaseā to a limited set of enthusiasts who are happy to test it before it reaches a wider audience where errors might be found. Itās up to the publisher which channels they use, each to their own.
I thought that Chrome names this channel as beta and the snap could following naming convention from the original project. Iām okay with additional step, but there should be also dev, edge should follow nightly master to resemble its name and/or canary.
, so maybe there can be steam snap also, it would be awesome as flatpak have it though.
