Resolving hosts in Chromium stopped working after applying the changes
as described in: https://bugs.launchpad.net/ubuntu/+source/network-
manager-strongswan/+bug/1864256/comments/3
Firefox and Chrome still could resolve host names.
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876083
I'm marking this as medium as we should handle ipv6 better and this may
help to determine if there's a broad issue in the base snaps, either on
the configuration side or in the set of packages contained.
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance:
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Ken VanDine (ken-vandine)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876083
Title:
chromium snap from focal fails DNS
I tested the chromium snap (1165) on a focal machine with IPv6 and
couldn't reproduce DNS lookup problems. I did, however, find a
difference between this chromium and unconfined chrome when handling
IPv6 large packets (unconfined chrome works as expects and chromium
times out).
Unconfined chrome
It seems to be ipv6-related but I'm not using ipv6 so couldn't verify.
FWTW I played with chromium snap on focal with ipv4 and couldn't spot
any DNS lookup slowness, it was super fast. I've updated the title of
the bug report accordingly.
** Summary changed:
- chromium snap from focal fails DNS
