On Thu, Sep 10, 2020 at 5:54 PM Michael Catanzaro <mcatanzaro@gnome.org> wrote:

On Thu, Sep 10, 2020 at 9:36 am, Kamil Paral <kparal@redhat.com> wrote:
> On Thu, Sep 10, 2020 at 8:54 AM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>> # authselect apply-changes
>> [error] [/etc/authselect/nsswitch.conf] has unexpected content!
>> [error] Unexpected changes to the configuration were detected.
>> [error] Refusing to activate profile unless those changes are
>> removed or overwrite is requested.
>> Some unexpected changes to the configuration were detected. Use
>> 'select' command instead.
>
> I see the same error.

I'm a bit concerned that two different people are seeing this. I don't
think we have any scriptlets tha writes to /etc/nsswitch.conf or
/etc/authselect/nsswitch.conf on its own. But maybe, for non-live
installs, that could happen if the systemd RPM gets installed before
the authselect RPM? Then systemd would think /etc/nsswitch.conf is not
managed by authselect. Hm....

Anyway, if you can find a way to get to this state from a clean
install, without touching those files manually, then please do report a
bug. That shouldn't be happening.

I did edit /etc/nsswitch.conf manually, because obviously I needed a working system :) The confusing part here is that the error message claims that **/etc/authselect/nsswitch.conf** has unexpected content. So this doesn't seem to be related to /etc/nsswitch.conf having been edited by hand. Is it? If it is, what is the proper way to revert back to upstream defaults in this case? Should I append "--force" to the command? (I don't want to destroy my system, that's why I'm not simply trying it. All of this seems awfully complex and fragile).