[Bug 568267] Re: Wireless disconnects with No probe response

2010-11-13 Thread Vish
I'v updated to Maverick and I havent noticed this problem again.

Closing my bug report as there are no other subscribers

** Changed in: network-manager (Ubuntu)
   Status: Incomplete = Invalid

-- 
Wireless disconnects with No probe response
https://bugs.launchpad.net/bugs/568267
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 568267] Re: Wireless disconnects with No probe response

2010-10-21 Thread Jean-Baptiste Lallement
Thanks for your report. Is it still an issue with lucid final and/or maverick ?
You marked this bug as regression-potential, what was the last known good 
version ?

** Tags removed: regression-potential

-- 
Wireless disconnects with No probe response
https://bugs.launchpad.net/bugs/568267
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 568267] Re: Wireless disconnects with No probe response

2010-05-30 Thread Vish
Oddly I'm not facing much of this bug as i used to , setting it to
incomplete.

Will re-open when i have more information about the bug.

** Changed in: network-manager (Ubuntu)
   Status: New = Incomplete

-- 
Wireless disconnects with No probe response
https://bugs.launchpad.net/bugs/568267
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 568267] Re: Wireless disconnects with No probe response

2010-04-22 Thread Vish

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/45006428/Dependencies.txt

** Attachment added: Gconf.txt
   http://launchpadlibrarian.net/45006429/Gconf.txt

** Attachment added: IpAddr.txt
   http://launchpadlibrarian.net/45006430/IpAddr.txt

** Attachment added: IwConfig.txt
   http://launchpadlibrarian.net/45006431/IwConfig.txt

** Attachment added: NetDevice.eth0.txt
   http://launchpadlibrarian.net/45006432/NetDevice.eth0.txt

** Attachment added: NetDevice.lo.txt
   http://launchpadlibrarian.net/45006433/NetDevice.lo.txt

** Attachment added: NetDevice.vboxnet0.txt
   http://launchpadlibrarian.net/45006434/NetDevice.vboxnet0.txt

** Attachment added: NetDevice.wlan0.txt
   http://launchpadlibrarian.net/45006435/NetDevice.wlan0.txt

** Attachment added: PciNetwork.txt
   http://launchpadlibrarian.net/45006436/PciNetwork.txt

** Attachment added: RfKill.txt
   http://launchpadlibrarian.net/45006437/RfKill.txt

** Attachment added: WifiSyslog.txt
   http://launchpadlibrarian.net/45006438/WifiSyslog.txt

** Attachment added: nm-system-settings.conf.txt
   http://launchpadlibrarian.net/45006439/nm-system-settings.conf.txt

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Low

-- 
Wireless disconnects with No probe response
https://bugs.launchpad.net/bugs/568267
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 568267] Re: Wireless disconnects with No probe response

2010-04-22 Thread Vish
Hmm , that made the bug description too long :/
Adding the syslog snippet as an attachment

** Attachment added: syslog.log
   http://launchpadlibrarian.net/45007594/syslog.log

** Description changed:

  Binary package hint: network-manager
  
  Since update :
  network-manager (0.8-0ubuntu2) to 0.8-0ubuntu3
  
- or 
+ or
  network-manager-pptp (0.8-0ubuntu1) to 0.8-0ubuntu2
  network-manager-pptp-gnome (0.8-0ubuntu1) to 0.8-0ubuntu2
  
- I have been noticing the following errors and wireless just disconnects
- for no reason:
- 
- Apr 22 12:17:01 vish-laptop CRON[30546]: (root) CMD (   cd /  run-parts 
--report /etc/cron.hourly)
- Apr 22 12:48:26 vish-laptop kernel: [85758.502125] No probe response from AP 
00:14:6c:d0:d1:20 after 500ms, disconnecting.
- Apr 22 12:48:26 vish-laptop wpa_supplicant[1006]: CTRL-EVENT-DISCONNECTED - 
Disconnect event - remove keys
- Apr 22 12:48:26 vish-laptop NetworkManager: info  (wlan0): supplicant 
connection state:  completed - disconnected
- Apr 22 12:48:26 vish-laptop NetworkManager: info  (wlan0): supplicant 
connection state:  disconnected - scanning
- Apr 22 12:48:27 vish-laptop kernel: [85759.129626] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:27 vish-laptop kernel: [85759.129637] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:27 vish-laptop kernel: [85759.629037] iwl3945 :03:00.0: 
Error sending REPLY_SCAN_CMD: time out after 500ms.
- Apr 22 12:48:28 vish-laptop kernel: [85760.129145] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:28 vish-laptop kernel: [85760.129156] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:28 vish-laptop kernel: [85760.631750] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:28 vish-laptop kernel: [85760.631761] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:29 vish-laptop kernel: [85761.131013] iwl3945 :03:00.0: 
Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
- Apr 22 12:48:33 vish-laptop kernel: [85765.132430] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:33 vish-laptop kernel: [85765.132441] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:33 vish-laptop kernel: [85765.632330] iwl3945 :03:00.0: 
Error sending REPLY_SCAN_CMD: time out after 500ms.
- Apr 22 12:48:34 vish-laptop kernel: [85766.136110] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:34 vish-laptop kernel: [85766.136121] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:34 vish-laptop kernel: [85766.638541] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:34 vish-laptop kernel: [85766.638552] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:35 vish-laptop kernel: [85767.137475] iwl3945 :03:00.0: 
Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
- Apr 22 12:48:39 vish-laptop kernel: [85771.136855] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:39 vish-laptop kernel: [85771.136866] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:39 vish-laptop kernel: [85771.636086] iwl3945 :03:00.0: 
Error sending REPLY_SCAN_CMD: time out after 500ms.
- Apr 22 12:48:40 vish-laptop kernel: [85772.136043] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:40 vish-laptop kernel: [85772.136053] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:40 vish-laptop kernel: [85772.638124] iwl3945 :03:00.0: 
Error sending REPLY_RXON: time out after 500ms.
- Apr 22 12:48:40 vish-laptop kernel: [85772.638135] iwl3945 :03:00.0: 
Error setting new configuration (-110).
- Apr 22 12:48:41 vish-laptop kernel: [85773.138440] iwl3945 :03:00.0: 
Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
- Apr 22 12:48:42 vish-laptop NetworkManager: info  (wlan0): device state 
change: 8 - 3 (reason 11)
- Apr 22 12:48:42 vish-laptop NetworkManager: info  (wlan0): deactivating 
device (reason: 11).
- Apr 22 12:48:42 vish-laptop NetworkManager: info  (wlan0): canceled DHCP 
transaction, dhcp client pid 1506
- Apr 22 12:48:42 vish-laptop NetworkManager: WARN  check_one_route(): 
(wlan0) error -34 returned from rtnl_route_del(): Sucess#012
- Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Withdrawing address record for 
192.168.1.2 on wlan0.
- Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.2.
- Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Interface wlan0.IPv4 no longer 
relevant for mDNS.
- Apr 22 12:48:42 vish-laptop NetworkManager: info  Activation (wlan0) 
starting connection 'Auto Airtel'
- Apr 22 12:48:42 vish-laptop NetworkManager: info  (wlan0):