I can confirm this. I am also using Chromium and cannot access the web admin interface of my printer, via
http://HP18602408C229.local/ In Firefox this works. Same for the snap I am working on, to provide CUPS and cups-browsed in a snap: https://github.com/OpenPrinting/printing-stack-snap/ cups-browsed is also not able to resolve ".local" host names if the host is in the local network but not the local machine, exactly as Chromium. So it seems to be a problem for snapped applications in general. ** Summary changed: - [snap] Chromium does not work with .local mdns/avahi name resolution + [snap] Snapped apps do not work with .local mdns/avahi name resolution -- 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] Snapped apps do not work with .local mdns/avahi name resolution Status in snapd: Triaged 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
