libnns-mymachines update breaks local mdns discovery

Bug #1925761 reported by Givrix
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown.
Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf.

After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again.
So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines.

Revision history for this message
Dan Streetman (ddstreet) wrote :

> I downgraded systemd to 245.4-ubuntu3

there's a really large delta between that and 245.4-ubuntu3.6, and you very probably were running 245.4-ubuntu3.5 before, not 245.4-ubuntu3.

In any case, we'll need more data to look at your problem, can you attach at least your journalctl output from the time when the problem happened

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Givrix (geoffrey-mosini) wrote :

> there's a really large delta between that and 245.4-ubuntu3.6, and you very probably were running 245.4-ubuntu3.5 before, not 245.4-ubuntu3.

Yes I know, but I don't know any easy way to downgrade to 3.5, there is only choice between 3 and 3.6.

Full journalctl or only specific service ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.