[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected

2021-02-16 Thread Stanislav Bocinec
So after further troubleshooting I found what was issue in my case - having `gnome-3-28-1804` snap installed, but disabled. After enabling it, `snap install chromium` now succeeds. For the reference adding list of the related installed snaps: ``` $ snap list |egrep '(gnome|core|chromium|gtk)'

[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected

2021-02-16 Thread Stanislav Bocinec
I'm experiencing the same error on Ubuntu 20.04, that started to occur suddenly a few months ago (don't have the version numbers). Since then I was not able to update chromium, nor able to install it after remove & purge as it fails with the reported error: ``` # snap install chromium error:

[Desktop-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-26 Thread Stanislav Bocinec
This isssue is not relevant to VPN connections only but also for normal workin local network. systemd-resolve and systemd-resolved stub listener are behaving differently - the stub does not accept the domain/search domains sent by DHCP. THis is really weird. Isn't the issue in domain/search