after a comment from jamesh in the forum discussion i found that installing nscd from universe works around the issue, but this does not change the fact that it is a regression of an ubuntu default feature, so there still needs to be some solution (snapd dependency on nscd and moving nscd back into main, fixing nssswitch.conf inside the core/core18 snap or some other new solution)
-- 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 chromium-browser package in Ubuntu: New 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/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
