and drop the --ppapi-flash-path option when starting Chromium if ~/snap/chromium/current/.local/lib/libpepflashplayer.so doesn’t exist? (Please note that passing an empty value, i.e. --ppapi-flash-path=, breaks Chromium’s built-in ability to load the plugin from one of the ‘normal’ places.)
Is this something you already have considered and turned down, or would it be possible? I think it would be an improvement, and Flash would keep being as easy to enable during the rest of its (short) remaining life as explained at this page.
I haven’t really considered it, mostly because of the upcoming EOL of Flash. These paths could possibly be added to the browser-support interface, this would require input from the security team. @jdstrand, how does that sound?
I use the yaru theme and I don’t use “system title bar and border” in Chromium as it takes vertical space. In this case you get a grey “title bar” as in picture from mohan-ram.
This looks a little bit strange as the top bar is dark by default.
In case you set theme in Chromium to Classic, the “title bar” will be almost white and if set to GTK+ a little bit gray.
I have changed the theme in Chromium to “Modern Flat”, that looks quite OK.
19.10 no modification at all. Stock, and when I toggle on Use System Title Bar option it freeze, I have to hard reset my machine. Mind you Brave browser and LibreOffice both look fine. Though LibreOffice reversts to using Human mouse theme (white) and not Yaru mouse theme (black).
I wanted to ask about native messaging (https://developer.chrome.com/extensions/nativeMessaging). It’s a terrible idea where you register programs on the host with the browser in a json file and the browser than starts them and you can communicate with them.
The KeePassXC browser integration is making use of that, and this obviously breaks with snaps, whether Chromium or Firefox. I imagine it would be possible to write like a native messaging bridge and have a native-messaging interface in the snaps to support this, but I’m uncertain if anyone has looked at that at all.
[quote=“oSoMoN, post:7, topic:11179”]
Why would you want to not install the snap version? Does it break an existing workflow for you?[/quote]
Maybe because :
⋅ snap wastes disk space,
⋅ confinement is more pain than gain in « simple » desktop usage,
⋅ forces user to otherwise organize his⋅her personal data to make them still available through snap app’,
⋅ theming issues might also break some workflow or habits.
Snap can be installed without confinement --classic but then losing their safety benefit which sounds like a misuse.
IMHO backporting this change to the 18.04 LTS would undermine trust, there is no way to gauge whether LTS users signed up for snaps … indeed I’d say they absolutely did not. 19.10 of course still belongs to Canonical/Ubuntu, but 18.04 does NOT, it now belongs to its users.
I’m using 19.10. After the upgrade to snap I get this error message when I open the https://extensions.gnome.org/ page
“Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector.”
I don’t like the migration from deb to snap, but I packaged chromium myself and understand why you want to migrate to snap. But there are some important questions.
currently I’m able to take any deb package from Ubuntu and make a custom build of it with some modifications, e.g. I once rebuilt Chromium removing user agent patch when web.whatsapp.com stopped understanding Ubuntu’s default user agent. Also, there is a PPA with VA-API enabled builds. How can the same be done with snaps: rebuild, publish in my own repo and install on all machines?
I update all office workstations with Ubuntu (XFCE) automatically with system-autoupdate (https://gitlab.com/mikhailnov/system-autoupdate/) in day time, so, when migrating from deb to snap:
2.1) won’t the browser crash after files from deb are removed?
2.2) if the update is done when the browser is running, what will happen with Chromium’s profile? Will a locked version be moved to another directory? What will happen after the original profile in ~/.config/chromium-browser is deleted? Won’t the profile become damaged?
what about disk space, I have PCs working on 30 GB SSDs and would not like to keep multiple versions of Chromium alongside each other as snapd does by default
what about updating in chroot where snapd is not running, how will you handle it?
.