I waited until the final release before upgrading. But it's good to
know this is actually a bug and has already been found.
Thanks.
On Wed, 2020-05-06 at 13:03 +0200, francis.montag...@inria.fr wrote:
> Hi.
> On Tue, 05 May 2020 19:48:22 -0400 Kevin Becker wrote:
> > It turns out mdns4_minimal
Hi.
On Tue, 05 May 2020 19:48:22 -0400 Kevin Becker wrote:
> It turns out mdns4_minimal had been removed from host resolution in
> nsswitch.conf.
This is a known bug:
https://fedoraproject.org/wiki/Common_F32_bugs#mDNS_.28multicast_DNS.29_breaks_on_upgrade_to_Fedora_32
This is resolved
Well, my printer was autodiscovered and configured via mDNS, so with
the mnds4_minimal entry missing, it was not able to resolve the name. I
could've gone an manually added it by IP address or a static DNS name
but I liked the simplicity of it working "automagically" and I never
remember the
On Tue, 05 May 2020 19:48:22 -0400
Kevin Becker wrote:
> It turns out
> mdns4_minimal had been removed from host resolution in nsswitch.conf.
> I restored the nsswitch.conf.bak on both machines and my printer is
> back in business.
Files like nsswitch.conf seem to be configured by the new
I've been using Fedora on my laptop for a few years now, and on a newly
built desktop for since just last summer. I've never had an issue
upgrading, but I only recently became aware of the recommended post-
install steps.
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
So
