GNOME Bugzilla – Bug 727783
nm tries to start the ModemManager service even when it is not installed.
Last modified: 2014-04-08 09:42:59 UTC
nm repeatedly tries to start the ModemManager systemd service, even after the first attempt to start it failed because the service doesn't exist, because ModemManager wasn't installed. It should stop trying to start the service the first time such an attempt fails due to the service not existing. Better yet, ModemManager's existence should be checked before any attempt is made to start it, since it is optional after all. I suppose this isn't a big deal, except that it unnecessarily clutters up systemd's log file. Here's a sample: Apr 07 17:03:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:03:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:05:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:05:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:07:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:07:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:09:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:09:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:11:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:11:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:13:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:13:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. Apr 07 17:15:23 vault dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Apr 07 17:15:23 vault dbus[238]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. As you can see, about every 2 minutes, systemd tries to start dbus-org.freedesktop.ModemManager1.service, most likely at the request of NetworkManager, since these start attempts disappear when NetworkManager isn't running.
*** This bug has been marked as a duplicate of bug 703040 ***