*** This bug is a duplicate of bug 141233 ***
https://bugs.launchpad.net/bugs/141233
** This bug has been marked a duplicate of bug 141233
MASTER network-manager crashes when wpasupplicant ctrl socket is not
available
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/b
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/bugs/138917
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
Network manager leaves the card in a state where it is not easily usable
with iwconfig. It won't connect to the network even if it is configured
with iwconfig.
You have to deactivate roaming mode, then reboot, then manually
configure with iwconfig.
--
network-manager 0.6.5-0ubuntu11 broken
https
Probably importance of this bug should be set to 'high' since it may
make updates unavailable to those users who don't know how to configure
their network from console with wireless tools.
Also, it would be advisable to make everyone 'downgrade' to
0.6.5-0ubuntu10 in the meanwhile, so that the b0r
I can confirm this. It happens since ubuntu11. I also have a ipw2200.
Network is unusable.
Sep 11 17:42:34 localhost NetworkManager: eth1: Device is
fully-supported using driver 'ipw2200'.
Sep 11 17:42:34 localhost NetworkManager: nm_device_init(): waiting for
device's worker thread to star
Reading the patches that went into 0.6.5-0ubuntu11, its probably
41t_nm_device_wireless_index_ctrl_sockets_by_run_count.patch thats causing the
problems, more specifically the hunk:
@@ -2808,27 +2822,30 @@
wpa_driver = "madwifi";
else if (!strcmp (kernel_driver, "hostap_p
** Attachment added: "Working nm"
http://launchpadlibrarian.net/9233999/working-nm.log
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/bugs/138917
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
** Attachment added: "Segfaulting nm"
http://launchpadlibrarian.net/9233998/broken-nm.log
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/bugs/138917
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
The difference is in the lines:
Sep 11 13:55:46 localhost NetworkManager: SUP: sending command
'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant2^I'
Sep 11 13:55:46 localhost NetworkManager: SUP: response was 'FAIL'
(broken)
vs.
Sep 11 17:29:56 localhost NetworkManager: SUP: sending com
