blueproximity compatibility issue with nm-applet wireless connections
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| blueproximity (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: blueproximity
*problem* (reproduction below)
When blueproximity cannot detect its paired device, nm-applet is unable to connect to wireless internet.
*background*
I recently purchased a wireless access point for my router and installed it as normal and it connected flawlessly with my ubuntu intrepid system. The next day I logged into my computer to find that it would no longer connect, and would repeatedly ask me for my WPA password only to fail at connecting again. Assuming it was a problem with a recent update, I searched through my synaptic history and many bug reports without any success. Then, after bringing my phone over to my computer to see if it could connect, the computer miraculously fixed itself.
*in short* - to reproduce this problem:
Turn off blueproximity's paired device and restart system. nm-applet will then be unable to connect to any wireless connections until: (a) the blueproximity paired device is switched on again, or (b) blueproximity is deactivated.
The issue may be with my particular driver set, as I have not checked any other computers to confirm, but this is the bug I experienced. I also have not tested whether this affects the wireless in general, or just the ability for nm-applet to connect. Also, as a side factor, I noticed small glitches in the wireless signal when my phone began to be out of range, but I can't confirm whether this is the same issue as not being able to connect, although I imagine it would be related.
To fix the problem, I've just disabled blueproximity for the moment
| boky (verynotbad) wrote | #1 |
| Felix (apoapo) wrote | #2 |
| Felix (apoapo) wrote apport information | #3 |
| tags: | added: apport-collected |
| Felix (apoapo) wrote Dependencies.txt | #4 |
I can also confirm this bug.
Hardware: Dell D830
Kernel: 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux
Wireless: iwlagn 0000:0c:00.0: loaded firmware version 228.61.2.24
BlueProximity: 1.2.5-4
Ubuntu: 10.04
The following is seen in syslog when BlueProximity is enabled:
Jul 3 22:57:40 PLAP11 wpa_supplicant[
Jul 3 22:57:40 PLAP11 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Jul 3 22:57:40 PLAP11 kernel: [ 26.290476] wlan0: deauthenticating from 00:18:39:bf:yy:yy by local choice (reason=3)
Jul 3 22:57:40 PLAP11 kernel: [ 26.290666] wlan0: direct probe to AP 00:18:39:c6:xx:xx (try 1)
Jul 3 22:57:41 PLAP11 kernel: [ 26.490239] wlan0: direct probe to AP 00:18:39:c6:xx:xx (try 2)
Jul 3 22:57:41 PLAP11 kernel: [ 26.690043] wlan0: direct probe to AP 00:18:39:c6:xx:xx (try 3)
Jul 3 22:57:41 PLAP11 kernel: [ 26.890054] wlan0: direct probe to AP 00:18:39:c6:xx:xx timed out
Jul 3 22:57:50 PLAP11 wpa_supplicant[
Jul 3 22:57:50 PLAP11 NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Jul 3 22:57:50 PLAP11 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Jul 3 22:57:52 PLAP11 wpa_supplicant[
Jul 3 22:57:52 PLAP11 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Jul 3 22:57:52 PLAP11 kernel: [ 38.068462] wlan0: direct probe to AP 00:18:39:bf:yy:yy (try 1)
Jul 3 22:57:52 PLAP11 kernel: [ 38.260073] wlan0: direct probe to AP 00:18:39:bf:yy:yy (try 2)
Jul 3 22:57:53 PLAP11 kernel: [ 38.460074] wlan0: direct probe to AP 00:18:39:bf:yy:yy (try 3)
Jul 3 22:57:53 PLAP11 kernel: [ 38.660039] wlan0: direct probe to AP 00:18:39:bf:yy:yy timed out
Jul 3 22:57:54 PLAP11 NetworkManager: <info> wlan0: link timed out.