Re: f32 upgrade breaks mdns/avahi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 9, 2020 at 8:04 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
>
> On Mon, Mar 9, 2020 at 6:55 PM Adam Williamson
> <adamwill@xxxxxxxxxxxxxxxxx> wrote:
> >
> > On Sun, 2020-03-08 at 12:54 -0600, Chris Murphy wrote:
> > > $ ls -l /etc/nss*
> > > -rw-r--r--. 1 root root 2405 Mar  8 03:51 /etc/nsswitch.conf
> > > -rw-r--r--. 1 root root 2402 Mar  8 00:26 /etc/nsswitch.conf.bak
> > > -rw-r--r--. 1 root root 2197 Feb  4 10:04 /etc/nsswitch.conf.rpmnew
> > >
> > > /etc/nsswitch.conf contains at the top:
> > >
> > > < # Generated by authselect on Fri Sep 20 09:47:27 2019
> > > < # Do not modify this file manually.
> > > <
> > > < # If you want to make changes to nsswitch.conf please modify
> > > < # /etc/authselect/user-nsswitch.conf and run 'authselect apply-changes'.
> > >
> > > And yet /etc/authselect/user-nsswitch.conf contents/policies don't
> > > match /etc/nsswitch.conf and neither file is correct.
> > >
> > > I also have /etc/nsswitch.conf.rpmnew and it's also not correct.
> > >
> > > I can't tell what stepped on /etc/nsswitch.conf
> > >
> > > And I'm not finding a release criterion that applies to this; I think
> > > it's a bad bug for Workstation to ship unable to resolve mDNS names.
> >
> > Meh, I mean, I've never relied on that stuff because it's broken half
> > the damn time anyway :P
>
> No it's supposed to work. Has worked for me on Workstation for years.
> Both clean installs and upgraded multiple times.
>
> it doesn't work out of the box on Server because nss-mdns isn't
> installed by default - which I think is a mistake. But whatever.
>
>
> > authselect-libs has a juicy %post script that does a ton of stuff; that
> > could be the culprit. The other thing I'd look at is sssd and related
> > packages...
>
> It's not reproducible from a new clean install of F31 without updates.
> So there's some update over the past six months that causes a state
> change in nsswitch.conf that then results in it being borked upon
> system-upgrade.
>
> Yuck.

Maybe if anyone else reports it, use Common Bugs it so a work around
has visibility?

-- 
Chris Murphy
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux