After upgrade to 9.10 Network Manager failed to connect

Bug #379219 reported by crf
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Low
Unassigned

Bug Description

After upgrading from 9.04 to 9.10, network manager, although it could see my router's wireless network, wouldn't make a connection to it while in Gnome, but would connect in xfce. However, whereas I had had a static ip set up, in xfce it had created a new connection, and was using dhcp.

I tried repeatedly fiddling many settings in the edit connections dialog in the network connection applet in gnome, but nothing worked. I eventually deleted /etc/NetworkManager/nm-system-settings.conf, and restarted, but it still didn't work. It didn't seem to save settings when I had it set to DHCP, and it wouldn't let me save (the okay button was greyed out) when I tried to set things with a static ip.

Eventually I somehow got a keyring authorisation dialog can up, and after I entered my password, network manager then did work. I was able to reset things to have a static ip.

----

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 379219 ? It will attach the necessary information to this report. Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
zeubs (remi-pacifico) wrote : apport-collect data

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IpRoute:
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.74 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.1.254 dev eth0 proto static
Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RfKill:

Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare vboxusers video
XsessionErrors:
 (gnome-settings-daemon:2278): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nm-applet:2380): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (polkit-gnome-authentication-agent-1:2390): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2374): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2370): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.1/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

Revision history for this message
zeubs (remi-pacifico) wrote : Dependencies.txt
Revision history for this message
zeubs (remi-pacifico) wrote : Gconf.txt
Revision history for this message
zeubs (remi-pacifico) wrote : IfupdownConfig.txt
Revision history for this message
zeubs (remi-pacifico) wrote : IpAddr.txt
Revision history for this message
zeubs (remi-pacifico) wrote : IwConfig.txt
Revision history for this message
zeubs (remi-pacifico) wrote : NetDevice.eth0.txt
Revision history for this message
zeubs (remi-pacifico) wrote : NetDevice.eth1.txt
Revision history for this message
zeubs (remi-pacifico) wrote : NetDevice.lo.txt
Revision history for this message
zeubs (remi-pacifico) wrote : NetDevice.vboxnet0.txt
Revision history for this message
zeubs (remi-pacifico) wrote : PciNetwork.txt
Revision history for this message
zeubs (remi-pacifico) wrote : WifiSyslog.txt
Revision history for this message
zeubs (remi-pacifico) wrote : WpaSupplicantLog.txt
Changed in network-manager (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
josh g. (josh-thoughtlost) wrote :

I've had this issue after upgrading to 9.10 as well. Automatic DHCP fails, but if I set a static IP address then it works. (It only greys out the option until you have all the proper info filled in, eg. netmask and gateway.)

Only tried this at home; if dynamic DHCP fails everywhere I go then this effectively cripples wireless away from home.

Revision history for this message
Lex Jarrell (lexj) wrote :

I have had the same problem and was unable to connect with a static or dynamic ip address after upgrading to 9.10. The only way to connect was to switch to wicd.

Revision history for this message
praveen.sinha (praveen-sinha) wrote :

I am also seeing this issue in kde. In Gnome it works correctly but in kde it just shows me the available networks and does not connect automatically or let me connect.

Revision history for this message
nobodie (nobodie0) wrote :

i have this bug also on a Dell Inspiron 1490 with a centrino chip. i have tried using wifi radar (nope) network-admin-gnome (nope) nm-applet (nope) ifconfig (nope) (oh, used the ifup command (sudo ifup wlan0) and failed in everything. I cruised the forums(nope) and realized that this was a bug not just a stupid me issue. anything happening with it or suggestions with what to do about it before wife gets too cranky and makes me reload 9.04 until somebody does get it fixed?

Revision history for this message
nobodie (nobodie0) wrote :

after a bit of poking about and reflection on the mention of authorizations and keyrings at the top of this thread i remembered that i had had some problems with policykit on the beta I installed on another computer in this network a while back. Looking about from that perspective I find that the network connections dialogue console tells me that my wireless was last running 2 days ago (wrong, it has been over a week since it worked) that auto eth0 has never worked or been connected anyway (should be news to you since this is eth0 i'm using right now).

network admin does not run out of System>administration>Network, only by cli: $sudo network-admin. but even then it does nothing. Looked at from the policykit perspective it seems that I am being blocked by PK from actually doing these things, even when as su. Or, to be more precise, the programs are being blocked and the eth0 connection is happening because it is setup before policyket can block access to the controls. or something like that, maybe?

Revision history for this message
param (param-king) wrote : apport-collect data

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IpRoute:
 172.25.24.0/22 dev wlan0 proto kernel scope link src 172.25.25.215 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 172.25.24.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
param (param-king) wrote : Dependencies.txt
Revision history for this message
param (param-king) wrote : Gconf.txt
Revision history for this message
param (param-king) wrote : IpAddr.txt
Revision history for this message
param (param-king) wrote : IwConfig.txt
Revision history for this message
param (param-king) wrote : NetDevice.eth0.txt
Revision history for this message
param (param-king) wrote : NetDevice.lo.txt
Revision history for this message
param (param-king) wrote : NetDevice.wlan0.txt
Revision history for this message
param (param-king) wrote : NetDevice.wmaster0.txt
Revision history for this message
param (param-king) wrote : PciNetwork.txt
Revision history for this message
param (param-king) wrote : WifiSyslog.txt
Revision history for this message
param (param-king) wrote : XsessionErrors.txt
Revision history for this message
param (param-king) wrote : nm-system-settings.conf.txt
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Lucid and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

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.