On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote: > Chris Murphy writes: > > > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy > > <li...@colorremedies.com> wrote: > > > > > > Maybe this bug: > > > > https://github.com/systemd/systemd/issues/13432 > > "opened this issue on Aug 29, 2019" > > I would not expect this to be fixed any time soon. The only solution > is: > > systemctl stop systemd-resolved > systemctl disable systemd-resolved > rm -f /etc/resolv.conf > ln -s ../run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf > > Hopefully, this fix will not stop working in the future, either.
Thanks for the suggestion. With those changes the flooding of the logs went away. I can connect to the VPN and name resolution works. BUT, I got five different SELinux errors instead rpmdb was denied read access on resolv.conf rpcbind was denied name_bind access on port 64866 chronyd was denied getattr access on no-stub-resolv.conf gnome-shell was denied getattr access on no-stub-resolv.conf geoclue was denied getattr access on no-stub-resolv.conf _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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/users@lists.fedoraproject.org
