The profile is at /var/lib/snapd/apparmor/profiles/snap.chromium.chromium.
Beware that it is managed by snapd, and updating the snap to a newer revision
will re-generate it, so custom changes will be lost.
--
You received this bug notification because you are a member of Desktop
Packages, which
BTW, where is the apparmor profile for the snap chromium? I couldn't
find it in /etc/apparmor.d
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1850893
Title:
So, instead of a symbolic link, I created a hard link and it works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1850893
Title:
chromium-browser does not resolve any names
Chromium does not open the file that I have linked to /etc/resolv.conf
$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 18 Nov 6 10:53 /etc/resolv.conf -> resolv.conf.PUBLIC
$ ls -al /etc/resolv.conf.PUBLIC
-rw-r--r-- 1 root root 455 Oct 24 20:22 /etc/resolv.conf.PUBLIC
Messages below:
$
The nameservice apparmor abstraction allows read access to
/etc/resolv.conf. However apparmor doesn't resolve symlinks by default.
I suggest you bind mount /etc/resolv.conf.PUBLIC to /etc/resolv.conf,
instead of a symlink.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete =>
Chromium does not open the file that I have linked to /etc/resolv.conf
$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 18 Nov 6 10:53 /etc/resolv.conf -> resolv.conf.PUBLIC
$ ls -al /etc/resolv.conf.PUBLIC
-rw-r--r-- 1 root root 455 Oct 24 20:22 /etc/resolv.conf.PUBLIC
Messages below:
$
The key to the problem likely lies in the following:
« Regarding the DNS setup: YES my DNS setup is not the default. I
have disabled the systemd DNS crap and fallen back on /etc/resolv.conf -
in that way it is non-default. »
Can you run "journalctl -f | grep DEN" in a terminal, then run
Agree with comment #22 - however why does does the SNAP version not
work?
Just updated to the EDGE channel [Version 80.0.3962.2 (Official Build)
snap (64-bit)] - but to no avail.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
"chromium-browser/xenial-updates 78.0.3904.70-0ubuntu0.16.04.2 amd64
[upgradable from: 77.0.3865.120-0ubuntu1~snap1]"
xenial is ubuntu 16.04. It seems that you have mixed repos from
different ubuntu versions and chromium deb from older version overwrote
version from 19.10. Kixing repos from
Just ran a "sudo apt update" followed by "sudo apt list --upgradable"
...
chromium-browser/xenial-updates 78.0.3904.70-0ubuntu0.16.04.2 amd64
[upgradable from: 77.0.3865.120-0ubuntu1~snap1]
So, it seems that upstream has reverted to an DPKG instead of snap.
$ $ snap list
Name
I have run the apport command.
Regarding the DNS setup: YES my DNS setup is not the default. I have
disabled the systemd DNS crap and fallen back on /etc/resolv.conf - in
that way it is non-default.
However, every application: Firefox Browser, Google Chrome browser,
Thunderbird E-mail client,
apport information
** Tags added: apport-collected eoan snap
** Description changed:
OS:
===
Description: Ubuntu 19.10
Release: 19.10
Chromium Browser:
=
Version 78.0.3904.70 (Official Build) snap (64-bit)
DNS resolution does not work in Chromium
As requested by Chris, please run the following command in a terminal to
attach additional debug information to this bug report:
apport-collect 1850893
Is there anything special with your DNS setup? (something non-default
maybe)
** Changed in: chromium-browser (Ubuntu)
Status: New =>
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Ubuntu 18.04 LTS is intended to upgrade to Ubuntu 18.10
(https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes) or to Ubuntu
20.04 LTS (after 20.04.1's release), ie. the next release or next LTS
release. If you
14 matches
Mail list logo
