[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
I reported similar issues as bug #1172967, so I will close that one. The upgrade from 12.10 to 13.04 was not smooth. After restarting at the end of the process, the boot hung with a black screen. I rebooted in failsafe mode and after enabling networking I resumed in low graphics mode and was successful. After rebooting, I had high resolution graphics but no internet connection. I rebooted again and used the 'old kernel', which is odd as it was supposedly deleted during the upgrade. My system shows that it's running 13.0.4 and I obviously have an internet connection. I have had the same issue on three different computers with different graphic cards. When I next reboot I'll try the current kernel again. --next day... After rebooting into 3.8.0-19, I get an internet connection for about 30 seconds, then it drops and won't re-connect unless suspended and woke again, where I get a fresh 30 seconds before it disconnects again. The network manager applet reports that both wired and wireless are working when they clearly aren't. The 'phantom' kernel 3.5.0-28 in Raring is still the only one I can use to stay connected. This is the case on both this laptop and my desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Raring Ringtail on every boot (with U+1 I do a lot of boots) does not automatically connect to WPA wireless. Raring Beta 2 invariably disconnects on boot. Systems Settings Network says out of range obviously tried to connect without the encryption key it already has. Manually select drop down window, shows the correct network, select it, and after a while presents a drop down with all the required info, and waits for me to select it. I do, and after a while it connects. Syslog has some network manager messages about secrets required and is oblivious to the secrets network manager already has. Pangolin on the same pc and netowrk connects autmatically, might take a couple seconds. Raring doesn't connect, as a matter of Network Manager policy. Android tablets on the same network (7 and 10.1) set up encryption once and they connect immediately. Every time. Raring doesn't. Chromebook boots, zooms up, connects, and bam into the internet. Once encryption is set up always boots right up, using the info, no manual intervention required. Raring doesn't compete with Chromebook on boot and ease of getting to internet. Apparently Network Manager doesn't consider this a bug, just the way network manager has decided to slow down boot. My other wireless products are set up for user convenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
25 February disconnects from wireless encrypted network on boot. That's the latest daily build update. Select System Settings network it says Out of range. It is not. Select connect to hidden networks and after a delay, displays the network, has the encryption key already, and when selected connects. Not out of range at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
As of 26 January build, either amd64 or i386, network manager detects the network, sees that an encryption key is needed, and then disconnects. Manually connect to the hidden network, it's got the key already, click thru the drop downs and connects fine. Obviously the network manager needs to put 2 and 2 together: 1. Hidden network.] 2. NM has the name of the network. 3. NM knows on a hidden network a key is required. 4. NM knows what the key is. 5. NM should enable wireless and connect but instead quits. Bug in the NM connection code. 6. Lost sight of how many times I had to manually connect today on two different pc's, one with Intel the other with Broadcom, same problem Only thing NM is better at is going through the drop downs which was deadly slow. Now just slow. BTW, Pangolin just goes ahead and connects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
As of 23 January, Raring still disconnects. Sees the hidden wireless network. NM reports that secrets required so it disconnects. Then NM discovers it has the secrets i.e. the encryption password. Does not even try to connect. Pangolin, Mint14, etc. have no problem. Raring's NM won't connect at boot, Manually, select the network which is displayed, NM says out of range. It is not out of range. NM tried to connect without using the secret password, which of course won't work don't even try it, then falsly concluded must have been out of range. Manually select connect to hidden network. NM magically fills in all the secrets which it had stored. Manually connect just fine. It is not out of range. The NM logic for connecting is wrong. 1. If the network that has been set up is a hidden encrypted network, don't even try to connect without the encryption key. That's the mistake in the NM logic. 2. Since it's the same network I always use, do connect on every boot, using the already stored encryption key. Im set up to connect automatically, then do it. Any suggestions on how to connect automatically? In development, with unstable Raring, I boot a lot. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
network out of range message from Network Manager. Same bug on Aspire 1 netbook with Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] as on the Broadcom reported previously. Network Manager sees the hidden network, knows it requires WPA key, then tries to connect without the WPA encryption key and of course it won't connect. Then posts out of range when the bug is network manager didn't use the encryption key. Manually go through the drop down menus, select hidden network, select the same network, network manager already has the encryption key, and connects just fine. Network Manager on Pangolin has no such problem. Is there any way to try the Network Manager from Pangolin on Raring? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Actually, Raring has been rebased to upstream v3.8-rc3 now. Can you apply the latest updates and see if this bug still exists? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Just submitted bug 1099976 where network manager is falsely reporting out of range. Anyway let me see if I can try the latest upstream kernel. All these bugs are pointing right at a network manager logic failure, but I'll try the kernel anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Installed latest upstream kernel I could find: 3.8.0-030800rc3-generic #201301092235 SMP Thu Jan 10 03:36:25 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux That didn't help the network manager logic bug at all, got the same disconnect. Do note I filed a bug #1099976 where the syslog clearly shows: Jan 15 14:13:31 Aspire-5253 NetworkManager[785]: info Auto-activating connection 'LAUREL'. Jan 15 14:13:31 Aspire-5253 NetworkManager[785]: info Activation (wlan0) starting connection 'LAUREL' Jan 15 14:13:31 Aspire-5253 NetworkManager[785]: info (wlan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Jan 15 14:13:31 Aspire-5253 NetworkManager[785]: info Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: info (wlan0): device state change: prepare - config (reason 'none') [40 50 0] . Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: info Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. So there it sits, with network disconnected. Network manager has the secrets but isn't even bothering to use tem. them. Manually select Settings Network, shows the network Out of Range which it is not. I do connect to hidden network and voila, connects O.K. with the secrets it already had. Note the time stamps: Jan 15 15:18:02 Aspire-5253 NetworkManager[885]: info Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. ... Jan 15 15:18:03 Aspire-5253 kernel: [ 115.088454] wlan0: authenticated Jan 15 15:18:03 Aspire-5253 NetworkManager[885]: info Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'LAUREL' Connect then proceeds O.K. Syslog attached. ** Attachment added: Syslog with latest kernel still shows NM logic problem. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+attachment/3484218/+files/syslog_kernel030800rc3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc3-raring/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
I'll give the mainline kernel a try tomorrow. Do note, looking at the syslogs, every time the mainline kernel is asked to authenticate by the Network Manager it does connect just fine. The problem is, the Network Manager is not asking for the authentication. I'm no developer, but having thrashed around with this bug for some time on two different pc's, I don't think the Network Manager is in the mainline kernel. Is there some way to patch the Network Manager scripts to put a message in syslog on why it is stopping short instead of connecting? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Today, raring detected the right wireless network ssid, then said out of range. Does NM check for hidden network encryption before issuing that message? I'd guess not. Did manual settings network hidden network and connected right up since NM had all the info it needed. No problem with out of range, so it is a false message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Raring 3.8 still has problem. Here's relevant syslog entries from Acer 5253 amd64 notebook. At 15:23:45 NM decides to disconnect. At 14:23:50. I started manual connect to hidden network which went through just fine, see the entries. As a user since Dapper Drake Beta, why has Network Manager decided to deactivate device at 15:23:45?? There are no new secrets needed so why does it disconnect anyway? At 15:24:45 after I started manual connect to hidden network it says. Jan 12 15:24:47 Aspire-5253 NetworkManager[805]: info Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. then goes right ahead and authenticates. Why doesn't NM just go ahead and connect like Precise does? Why didn't NM do the connect at 15:23:45?? instead of me having to do a manual connect? Jan 12 15:23:45 Aspire-5253 cron[976]: (CRON) INFO (Running @reboot jobs) Jan 12 15:23:45 Aspire-5253 kernel: [6.254504] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0): preparing device. Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0): deactivating device (reason 'managed') [2] Jan 12 15:23:45 Aspire-5253 kernel: [6.259191] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jan 12 15:23:45 Aspire-5253 dbus[401]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper) Jan 12 15:23:45 Aspire-5253 kernel: [6.271985] cfg80211: World regulatory domain updated: Jan 12 15:23:45 Aspire-5253 kernel: [6.271995] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jan 12 15:23:45 Aspire-5253 kernel: [6.272000] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Jan 12 15:23:45 Aspire-5253 kernel: [6.272004] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Jan 12 15:23:45 Aspire-5253 kernel: [6.272007] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Jan 12 15:23:45 Aspire-5253 kernel: [6.272011] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) Jan 12 15:23:45 Aspire-5253 kernel: [6.272014] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Jan 12 15:23:45 Aspire-5253 acpid: 33 rules loaded Jan 12 15:23:45 Aspire-5253 acpid: waiting for events: event logging is off Jan 12 15:23:45 Aspire-5253 NetworkManager[805]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:15.3/:07:00.0/bcma0:0/net/wlan0, iface: wlan0) Jan 12 15:23:45 Aspire-5253 NetworkManager[805]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:15.3/:07:00.0/bcma0:0/net/wlan0, iface: wlan0): no ifupdown configuration found. Jan 12 15:23:45 Aspire-5253 dbus[401]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info wpa_supplicant started Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0) supports 4 scan SSIDs Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: warn Trying to remove a non-existant call id. Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0): supplicant interface state: starting - ready Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0): device state change: unavailable - disconnected (reason 'supplicant-available') [20 30 42] Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0): supplicant interface state: ready - inactive Jan 12 15:23:45 Aspire-5253 NetworkManager[805]: info (wlan0) supports 4 scan SSIDs Jan 12 15:23:45 Aspire-5253 ntpdate[1049]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Jan 12 15:23:45 Aspire-5253 ntpdate[1049]: no servers can be used, exiting Jan 12 15:23:45 Aspire-5253 acpid: client connected from 1054[0:0] Jan 12 15:23:45 Aspire-5253 acpid: 1 client rule loaded Jan 12 15:23:45 Aspire-5253 anacron[1082]: Anacron 2.3 started on 2013-01-12 Jan 12 15:23:45 Aspire-5253 anacron[1082]: Normal exit (0 jobs run) Jan 12 15:23:46 Aspire-5253 dbus[401]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper) Jan 12 15:23:46 Aspire-5253 accounts-daemon[1202]: started daemon version 0.6.29 Jan 12 15:23:46 Aspire-5253 dbus[401]: [system] Successfully activated service 'org.freedesktop.Accounts' Jan 12 15:23:47 Aspire-5253 dbus[401]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) Jan 12 15:23:47 Aspire-5253 dbus[401]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Jan 12 15:23:47 Aspire-5253 dbus[401]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Jan 12 15:23:47 Aspire-5253 dbus[401]: [system] Successfully activated service 'org.freedesktop.UPower' Jan 12 15:23:48 Aspire-5253 anacron[1433]: Anacron 2.3 started on 2013-01-12 Jan 12 15:23:48 Aspire-5253 anacron[1433]: Normal exit (0 jobs run) Jan 12 15:23:49
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
So you mean the bug is present in Quantal as well? Are you sure it is working fine in Precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Yes, Quantal doesn't connect and must be manually connected through system settings, even though it remembers the network name, encryption, etc. When it boots up, where it should connect, it says disconnect which does show up in the many many messages from network manager on the syslog. Once network manager (or the kernel, I wouldn't know) asks for authenticate it goes right through. Since Raring is all setup to recognize hidden wireless, the network, and the encryption key it should try that first off. Instead it seems to do a knee jerk disconnect and then never even tries to connect with the information it already has. Where is the spot in the nm script that says go do the connect and authenticate? Why isn't it being issued? Let me go check Precise again. I usually run Raring but do have backup Quantal and Precise partitions. Thanks for looking at this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
** Tags added: quantal regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Here's Precise. Booted up, I looked closely, there was a Disconnected message followed shorty by Connected. Attached is syslog showing that. All I had to do is wait a few seconds. Raring today, there was a Disconnected and when I finally got tired of waiting, systems settings network manager said out of range. Is that what it would get if it was trying to connect to hidden wireless without doing the encryption key etc.? Went through the drop down menus, nm eventually put up the network name which it had already, then nm put up the encryption key which it had already, and connected. It had all the information. It's as if there is nothing in the raring nm boot script to even try to connect to the already configured hidden wireless WPA network. Why doesn't the raring nm boot script connect automatically like it does in precise? I can't read nm scripts. Conceptually, raring nm should look at the configuration on boot, see there is a hidden wireless network configured, authenticate and connect. For some reason raring nm totally ignores the configuration then decides to disconnect without even trying to connect to the configuration that is already set up. Precise can do it, what changed (lots)? It's like Raring looks around, does not see any public network and gives up even though it does have all the info for connecting to hidden wireless WPA. Precise can do it, what got dropped out of Raring? Thanks, Jerry ** Attachment added: Precise syslog does automatic connect. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+attachment/3476984/+files/syslog_precise_autoconnect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
To determine if this is a kernel or network manager issue, would it be possible for you to try to install a kernel for precise and see if that solves the issue? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Actually, on Quantal, I even installed a Debian kernel, upstream looked at the result and said as soon as the kernel gets the authenticate signal it promptly connects. As you can see from the syslogs, once the NM gets around to issuing the authentiate, the kernel goes right ahead and connects. The problem is, the NM does not bother to send the authenticate to the kernel. No way the kernel can connect if NM doesn't ask it to. Where in the NM scripts is it supposed to issue the authenticate and connect? Is it possible to patch the NM to put a tell tale syslog message in the NM scripts to say it is going to connect, or why it won't issue the connect? I can try to apply a patch, but I'm not a developer so I don't know how to write a patch for NM to find out where it decides not to connect, or why NM stopped before issuing the authenticate. Thank you for looking at this. BTW, linuxmint14 based on Quantal has no such trouble. Use settings to set up hidden wireless and works every time thereafter. I don't know how to compare the mint14 nm scripts to the quantal nm scripts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Please test with a Quantal live CD, so that we know where the regression was introduced. ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097002] Re: On every boot, raring 3.7.0-7 fails to connect to wireless WPA
Tried with an installed Quantal, Release:12.10 Codename: quantal Linux version 3.5.0-17-generic (buildd@allspice) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 Set up wireless WPA was working fine. Shutdown, booted, Quantal disconnected instead of connecting. Used Systems Settings Network. Response sluggish, it did remember the network, and did remember the WPA encryption. Very sluggish but did then connect. Network Manager had the network name, had the encryption key, but disconnected anyway until I got it going again manually thru systems settings. Attached is syslog. ** Attachment added: Syslog from wireless WPA disconnect instead of connect https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+attachment/3476538/+files/syslog_quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
