I just attempted to reproduce this issue with: - snapd 2.24~pre2 on Ubuntu 19.04 - chromium snap revision 861
I installed apache2 locally via apt and opened the link "fyke.local" in both Firefox and Chromium. Note that Firefox accepted just fyke.local and did the right thing while Chromium would search google unless I spelled the link as "http://fyke.local";. Perhaps this issue has been fixed since, marking as incomplete. ** Changed in: snapd Status: New => Incomplete -- 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/1838038 Title: [snap] Chromium does not work with .local mdns/avahi name resolution Status in snapd: Incomplete Status in chromium-browser package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chromium-does-not- work-with-local-mdns-avahi-name-resolution/12483) The current chromium snap does not allow to open any .local urls. This is most likely caused by https://forum.snapcraft.io/t/no-mdns- support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603. With the removal of the chromium deb and the switch to a snap-only deployment for this browser this is a pretty solid regression that should be addressed… To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1838038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
