Bug 766164

Summary: Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service'
Product: [Fedora] Fedora Reporter: udo <udovdh>
Component: dbusAssignee: David Zeuthen <davidz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: davidz, dcbw, lpoetter, mclasen, mschmidt, walters, wdouglascampbell
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 08:41:18 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description udo 2011-12-10 13:16:30 EST
Description of problem:
dmesg has lines of text in summary and at the bottom the full line.

Version-Release number of selected component (if applicable):

How reproducible:
I just `yum update`d from F15 to F16. So all rpms were replaced.

Actual results:
See below.

Expected results:
No such logs.

Additional info:
dbus-daemon[3148]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Comment 1 Michal Schmidt 2012-01-12 16:10:11 EST
'dbus-org.freedesktop.NetworkManager.service' is an alias for NetworkManager.service that is created when NetworkManager.service is enabled.
From /lib/systemd/system/NetworkManager.service:

The message indicates that a D-Bus client attempted to communicate with NetworkManager and NetworkManager.service is disabled. There's nothing wrong about that and the occurrence of the message is normal.

The message may be confusing though. Reassigning to dbus.
Comment 2 Fedora End Of Life 2013-01-16 08:02:02 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 3 Fedora End Of Life 2013-02-13 08:41:21 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 4 wdouglascampbell 2013-02-21 20:44:54 EST
This bug should be re-opened as it occurs for me in Fedora 18.

NetworkManager version


I don't use NetworkManager service, so it is disabled.

Any other information I can provide?