Description of problem: This might be a NetworkManager bug, but it most related to ModemManager. I don't have a modem or need ModemManager, but every 2 minutes, NetworkManager pings ModemManager to activate it leaving these messages in the logs: Nov 21 11:05:18 Parkes dbus-daemon[3038]: dbus[3038]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Nov 21 11:05:18 Parkes dbus[3038]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Nov 21 11:05:18 Parkes dbus[3038]: [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. Nov 21 11:05:18 Parkes dbus-daemon[3038]: dbus[3038]: [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. Redhat has this bug at: https://bugzilla.redhat.com/show_bug.cgi?id=1018017 Redhat lists upstream bug at: https://bugzilla.gnome.org/show_bug.cgi?id=703040 Reproducible: Steps to Reproduce:
Possible solutions adapted from here: https://bugs.archlinux.org/task/34971 1.Manually start the service # systemctl start ModemManager1.service && systemctl enable ModemManager1.service 2. Disable modem-manager by removing its D-Bus service file # rm -f /usr/share/dbus-1/system-services/org.freedesktop.ModemManager1.service This seems to be a widespread problem with entries in Bugzillas for several distros.
CC: (none) => hoyt
CC: (none) => mageia, olav
Actually the real fix for this is in upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=703040#c5 Currently testing that, will commit and push out an update if it works as intended. Also added to Errata: https://wiki.mageia.org/en/Mageia_4_Errata#modemmanager_spamming_the_logs @dams: OK for me to commit the fix if it works? You may also want to include this in the mga3 update for https://bugs.mageia.org/show_bug.cgi?id=9718 ...
Keywords: (none) => PATCH, Triaged, UPSTREAMStatus: NEW => ASSIGNEDCC: (none) => doktor5000, mageiaAssignee: bugsquad => doktor5000
Fix seems to be effective. Before: [doktor5000@Mageia4 ~]$ journalctl -ab | grep -ci modem 1940 After: [doktor5000@Mageia4 ~]$ journalctl -ab | grep -ci modem 4 (The 4 occurences appear during boot) @dams: OK to commit for Cauldron and 4?
Thanks for the test Florian. Yes, go ahead on this update please.
Submitted networkmanager-0.9.8.8-4.mga5 for Cauldron, working on mga4 update.
Submitted update candidate for Mageia4: networkmanager-0.9.8.8-3.1.mga4 Suggested advisory: Every 2 minutes NetworkManager tries to ping ModemManager via dbus, filling the logs with 4 messages. This updated adresses this issue. References: https://bugzilla.gnome.org/show_bug.cgi?id=703040 ======================== Updated packages in core/updates_testing: x86_64 lib64networkmanager-gir1.0-0.9.8.8-3.1.mga4.x86_64.rpm lib64nmclient-gir1.0-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-glib4-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-glib-devel-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-glib-vpn1-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-glib-vpn-devel-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-util2-0.9.8.8-3.1.mga4.x86_64.rpm lib64nm-util-devel-0.9.8.8-3.1.mga4.x86_64.rpm networkmanager-0.9.8.8-3.1.mga4.x86_64.rpm i586 libnetworkmanager-gir1.0-0.9.8.8-3.1.mga4.i586.rpm libnmclient-gir1.0-0.9.8.8-3.1.mga4.i586.rpm libnm-glib4-0.9.8.8-3.1.mga4.i586.rpm libnm-glib-devel-0.9.8.8-3.1.mga4.i586.rpm libnm-glib-vpn1-0.9.8.8-3.1.mga4.i586.rpm libnm-glib-vpn-devel-0.9.8.8-3.1.mga4.i586.rpm libnm-util2-0.9.8.8-3.1.mga4.i586.rpm libnm-util-devel-0.9.8.8-3.1.mga4.i586.rpm networkmanager-0.9.8.8-3.1.mga4.i586.rpm Source RPMS: networkmanager-0.9.8.8-3.1.mga4.src.rpm
Hardware: x86_64 => AllVersion: Cauldron => 4
Assignee: doktor5000 => qa-bugsSource RPM: modemmanager-1.0.0-3.mga4.src.rpm => (none)
Yep much better.
Source RPM: (none) => networkmanagerWhiteboard: (none) => mga4-64-ok
Perhaps it would make sense to update ModemManager to the current stable 1.2 version at the same time, as it appears to have related bug fixes. http://cgit.freedesktop.org/ModemManager/ModemManager/
CC: (none) => bcm.alaska
(In reply to Brian McNeil from comment #8) > Perhaps it would make sense to update ModemManager to the current stable 1.2 > version at the same time, as it appears to have related bug fixes. Nope, not for Mageia 4. See our updates policy: https://wiki.mageia.org/en/Updates_policy#Version_Policy
"Bug fix only release. There is no point in shipping all the fixes as patches if the new version does not contain any new feature." MM 1.2 appears to largely be a bug fix release of MM 1.0 , at least by reviewing the "commit messages" anyway. Although it does add a feature related to turning A-GPS on/off. I mention this because ModemManager is an integral component of NetworkManager, and a pretty important one if you have a mobile broadband modem you're hoping to get working.
Testing complete Mageia 4 i586. I could reproduce the bug described in comment 0 and test that the update candidate fixes it. -- Validating update. Could someone commit the advisory suggested in comment 6 and push the update from core/updates_testing to core/updates in Mageia 4?
Keywords: (none) => validated_updateWhiteboard: mga4-64-ok => mga4-32-ok mga4-64-okCC: (none) => remi, sysadmin-bugs
Advisory uploaded.
Whiteboard: mga4-32-ok mga4-64-ok => mga4-32-ok mga4-64-ok advisory
Update pushed: http://advisories.mageia.org/MGAA-2014-0028.html
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED