Just repeating what I said on the forum, I believe this could be
implemented through updates to the base snaps with no changes to snapd
or any application snaps.
The mdns4_minimal NSS plugin is an 18K binary (which compresses to about
6KB) that delegates its lookups to avahi-daemon using a single
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/1f6
Adding snap-core18 and snap-core20 tasks as it is a problem of core18
and core20 missing support for looking up host names via mDNS/DNS-SD.
The problem occurs also in other Snaps not only in the Chromium Browser
Snap. Therefore the fix for this bug is essentially important and
urgently needed.
Not
** Also affects: snap-core20
Importance: Undecided
Status: New
** Also affects: snap-core18
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838038
Now with nscd running and snapd restarted I have also cloded and re-
opened the Chromium browser and I can access my printer's web interface
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838038
I have to install nscd on the host machine and then restart snapd and my
snap:
sudo systemctl restart snapd
sudo snap restart printing-stack-snap
and after that cups-browsed succeeds to resolve .local host names.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
