Description of problem: NetworkManager writes two log messages every three seconds about the hostname (see below). I was able to stop the messages by doing sudo hostname NAME but the messages start to show up again later (I'll have to check why). Nov 03 10:01:02 localhost NetworkManager[1263]: <info> [1604415662.6654] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:02 localhost NetworkManager[1263]: <info> [1604415662.6671] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:05 localhost NetworkManager[1263]: <info> [1604415665.7389] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:05 localhost NetworkManager[1263]: <info> [1604415665.7408] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:08 localhost NetworkManager[1263]: <info> [1604415668.6049] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:08 localhost NetworkManager[1263]: <info> [1604415668.6061] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:11 localhost NetworkManager[1263]: <info> [1604415671.6763] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:11 localhost NetworkManager[1263]: <info> [1604415671.6782] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:14 localhost NetworkManager[1263]: <info> [1604415674.7501] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:14 localhost NetworkManager[1263]: <info> [1604415674.7519] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:17 localhost NetworkManager[1263]: <info> [1604415677.6173] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Nov 03 10:01:17 localhost NetworkManager[1263]: <info> [1604415677.6191] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost' Version-Release number of selected component (if applicable): NetworkManager - 1.26.4-1.fc33 systemd - 246.6-3.fc33 How reproducible: Steps to Reproduce: 1. Fresh install of Fedora 33 2. Connect to wi-fi 3. Check journalctl Actual results: Log is completely filled with these entries and they continue being written as long as NetworkManager and systemd-hostnamed are running together. Expected results: A couple of log messages Additional info: Changing the hostname via Gnome Settings-->About or hostnamectl doesn't stop the constant messages. Nov 03 10:36:49 abcde NetworkManager[1263]: <info> [1604417809.8140] policy: set-hostname: current hostname was changed outside NetworkManager: 'fedora' Nov 03 10:36:49 abcde NetworkManager[1263]: <info> [1604417809.8141] policy: set-hostname: set hostname to 'abcde' (from system configuration) Nov 03 10:36:52 abcde NetworkManager[1263]: <info> [1604417812.8862] policy: set-hostname: current hostname was changed outside NetworkManager: 'fedora' Nov 03 10:36:52 abcde NetworkManager[1263]: <info> [1604417812.8863] policy: set-hostname: set hostname to 'abcde' (from system configuration) Nov 03 10:36:55 abcde NetworkManager[1263]: <info> [1604417815.9568] policy: set-hostname: current hostname was changed outside NetworkManager: 'fedora' Nov 03 10:36:55 abcde NetworkManager[1263]: <info> [1604417815.9568] policy: set-hostname: set hostname to 'abcde' (from system configuration) Nov 03 10:36:58 abcde NetworkManager[1263]: <info> [1604417818.8236] policy: set-hostname: current hostname was changed outside NetworkManager: 'fedora' Nov 03 10:36:58 abcde NetworkManager[1263]: <info> [1604417818.8236] policy: set-hostname: set hostname to 'abcde' (from system configuration)
Same problem for me with NetworkManager-1.26.4-1.fc33.x86_64 System is an upgrade from Fedora 32 and I dont use WiFi but Ethernet.
I use gnome-shell and i have some doubt about "device name" in gnome-control-center-3.38.2-2.fc33.x86_64
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I just had the same problem on Fedora 35, but the problem disappeared when disabling IPv6 as described here: https://forums.fedoraforum.org/showthread.php?327134-How-to-disable-ipv6-in-fedora-34