Bug 701868 - NetworkManager does not start on boot after F14-15 upgrade
Summary: NetworkManager does not start on boot after F14-15 upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 678553
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 06:26 UTC by Klaas Vantournhout
Modified: 2011-05-05 17:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-05 17:46:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Klaas Vantournhout 2011-05-04 06:26:40 UTC
Description of problem:
After upgrading F14 to F15 by means of yum, the NetworkManager service is not started. I have to restart it manually

service NetworkManager restart

I would say I will give you some information from /var/log/messages, but that file does not seem to be updated anymore. The last entries are from before the update.

dmesg gives me the following:

[  316.509787] dbus-daemon[877]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
[  316.510121] dbus-daemon[877]: [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' for details.

and repeats this a couple of times

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

NetworkManager-0.8.998-4.git20110427.fc15.x86_64

How reproducible:
start from a recently updated F14 x86_64

yum update yum
yum --releasever=15 --disablerepo=updates upgrade
yum --releasever=15 --disablerepo=updates distro-sync
yum groupupdate Base

reboot

Actual results:
No NetworkManager started

Expected results:
The opposite!


Additional info:

Comment 1 Jirka Klimes 2011-05-05 17:46:51 UTC
It's a duplicate of bug 678553.
The empty /var/log/messages issue is here: bug 699198

See also bug 696278

*** This bug has been marked as a duplicate of bug 678553 ***


Note You need to log in before you can comment on or make changes to this bug.