Applied a Snap-side workaround to my Snaps which implements the fix presented in the snapcraft.io thread mentioned in my previous post:
CUPS Snap: https://github.com/OpenPrinting/cups-snap/commit/f241f3f02 PostScript Printer Application: https://github.com/OpenPrinting/ps-printer-app/commit/1f6ca389 Note that doing this on any Snap which needs it in the future is awkward, so we really need to fix core18 and core20. -- 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 snap-core18: New Status in snap-core20: New 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/snap-core18/+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
