NetworkManager fails to connect at login; needs restart

Bug #405902 reported by Ken Lewis
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

On startup, often I find that no network connections are working and that NetworkManager needs to be restarted (via /etc/init.d/NetworkManager restart). At the same time, there's a segfault in my dmesg logs:

[ 30.988682] NetworkManager[2340]: segfault at 0 ip 00007fe88b9b10d0 sp 00007fffe64d4858 error 4 in libc-2.9.so[7fe88b931000+166000]

I connect with DHCP to a wired network at home. This bug happens relatively often, but I can't trace specific events which lead it to happen. Testing upstream kernels bring it about more often, but Karmic's kernel (this report should show Karmic with linux-image-2.6.31-4-generic) suffers from the bug, too.

ProblemType: Bug
Architecture: amd64
Date: Tue Jul 28 17:17:42 2009
DistroRelease: Ubuntu 9.10
Gconf:

Package: network-manager 0.7.1-0ubuntu1
ProcEnviron:
 LANGUAGE=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
SourcePackage: network-manager
Uname: Linux 2.6.31-4-generic x86_64
WpaSupplicantLog:

Revision history for this message
Ken Lewis (kenlewis) wrote :
Revision history for this message
mlindeblom (mlindeblom) wrote :
Download full text (3.4 KiB)

Haven't tried restarting networkmanager; however: find rebooting system works.

syslog messages:

Jul 29 19:25:52 karmic NetworkManager: <info> starting...
Jul 29 19:25:52 karmic NetworkManager: <info> (eth0): new Ethernet device (driver: 'r8169')
Jul 29 19:25:52 karmic NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_01_2e_0e_4f_1d
Jul 29 19:25:52 karmic NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties
Jul 29 19:25:52 karmic NetworkManager: <info> Trying to start the supplicant...
Jul 29 19:25:52 karmic NetworkManager: <info> Trying to start the system settings daemon...
Jul 29 19:25:52 karmic NetworkManager: <info> (eth0): carrier now ON (device state 1)
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: init!
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: update_system_hostname
Jul 29 19:25:52 karmic nm-system-settings: SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
Jul 29 19:25:52 karmic avahi-daemon[2838]: Found user 'avahi' (UID 109) and group 'avahi' (GID 116).
Jul 29 19:25:52 karmic avahi-daemon[2838]: Successfully dropped root privileges.
Jul 29 19:25:52 karmic avahi-daemon[2838]: avahi-daemon 0.6.25 starting up.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Successfully called chroot().
Jul 29 19:25:52 karmic avahi-daemon[2838]: Successfully dropped remaining capabilities.
Jul 29 19:25:52 karmic avahi-daemon[2838]: No service file found in /etc/avahi/services.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.107.
Jul 29 19:25:52 karmic avahi-daemon[2838]: New relevant interface eth0.IPv4 for mDNS.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Network interface enumeration completed.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Registering new address record for fe80::201:2eff:fe0e:4f1d on eth0.*.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Registering new address record for 192.168.0.107 on eth0.IPv4.
Jul 29 19:25:52 karmic avahi-daemon[2838]: Registering HINFO record with values 'X86_64'/'LINUX'.
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, autoconnect:0, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-0000-000000000000
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: autoconnect
Jul 29 19:25:52 karmic nm-system-settings: SCPluginIfupdown: management mode: unmanaged
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_01_2e_0e_4f_1d, iface: eth0): well known
Jul 29 19:25:52 karmic nm-system-settings: Ifupdown: get unmanaged devices count: 1
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: (27854176) ... get_connections.
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: (27854176) ... get_connections (managed=false): return empty list.
Jul 29 19:25:52 karmic nm-system-settings: Ifupdown: get unmanaged devices count: 1
Jul 29 19:25:52 karmic nm-system-settings: SCPlugin-Ifupdown: end _init.
Jul 29 19:25:52 karmic nm-system-settings: Loade...

Read more...

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I wonder if this is similar to my #404507 - although it hasn't happened for the last few reboots.
In my case I find NetworkManager isn't actually running at all.

Dave

Revision history for this message
mlindeblom (mlindeblom) wrote :

I had the same problem as described in bug 408773 today.

sudo /etc/init.d/apparmor stop
sudo dhclient eth0

fixed the problem.

Revision history for this message
Victor Vargas (kamus) wrote :

Can you try upgrade your Karmic system (up to date), network-manager package and check if this problem is still occurring?
Regards

Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 405902 and any other logs that are relevant for this particular issue.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.