NetworkManager don't start automatically

Bug #365471 reported by map on 2009-04-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

After upgrading to Jaunty today, NetworkManager won't start automatically. I have to invoke the command "NetworkManager" manually through console, to be able to connect to a network using nm-applet.

dmesg | grep Network
[ 2.978678] e1000e: Intel(R) PRO/1000 Network Driver -
[ 3.095334] 0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
[ 13.249737] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[ 15.272885] type=1505 audit(1240479716.988:6): operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" name2="default" pid=1976

This does not happening by suspending the system.

Ben Koerner (koernerb) on 2009-04-24
affects: ubuntu → network-manager (Ubuntu)
map (map+) wrote :
description: updated
tags: added: network-manager
Alexander Sack (asac) wrote :

reboot and attach your complete syslog after reproducing.

Changed in network-manager (Ubuntu):
status: New → Incomplete
map (map+) wrote :

I restarted and attached syslog after restarting (syslog_before.txt) and syslog after invoking NetworkManager (syslog_after.txt)

map (map+) wrote :
Victor Vargas (kamus) wrote :

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

map (map+) wrote :

This bug do not exist in Karmic.

Changed in network-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers