[Desktop-packages] [Bug 875424] Re: unable to connect to encrypted access point with r8712 driver

2012-07-22 Thread Thomas Hood
SJI wrote:
 If I ignore the dialogue box another will eventually appear, and another, 
 and... 

The duplicate password dialog boxes problem has been reported in bug
#912702.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/875424

Title:
  With USB Wi-Fi adapter, NM is unable to connect to any network with
  encryption; deleting connection details fixes the problem but it just
  happens again -- Realtek RTL8191S r8712u

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  Wifi was working without issue under Ubuntu 11.04. After upgrading to
  Ubuntu 11.10 Wifi will not connect if the access point has encryption
  enabled.

  r8712u module is being loaded for Wifi adapter.

  Output from lsusb:
  Bus 001 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191S WLAN 
Adapter

  Output from uname -a:
  Linux boron 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  Output from syslog during connection attempt:
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: starting - ready
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: ready - inactive
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) starting 
connection '42'
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation 
(wlan0/wireless): access point '42' has security, but secrets are required.
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:47:50 boron NetworkManager[950]:keyfile: updating 
/etc/NetworkManager/system-connections/42
  Oct 16 02:48:11 boron NetworkManager[950]: get_secret_flags: assertion 
`is_secret_prop (setting, secret_name, error)' failed
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: need-auth - prepare (reason 'none') [60 40 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation 
(wlan0/wireless): connection '42' has security, and secrets exist.  No new 
secrets needed.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'ssid' value 
'*'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'scan_ssid' 
value '1'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'key_mgmt' 
value 'NONE'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'wep_key0' 
value 'omitted'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 
'wep_tx_keyidx' value '0'
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: set interface 
ap_scan to 1
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: inactive - scanning
  Oct 16 02:49:11 boron NetworkManager[950]: warn Activation 
(wlan0/wireless): association took too long.
  Oct 16 02:49:11 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:49:11 boron NetworkManager[950]: 

[Desktop-packages] [Bug 875424] Re: unable to connect to encrypted access point with r8712 driver

2011-12-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/875424

Title:
  unable to connect to encrypted access point with r8712 driver

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Wifi was working without issue under Ubuntu 11.04. After upgrading to
  Ubuntu 11.10 Wifi will not connect if the access point has encryption
  enabled.

  r8712u module is being loaded for Wifi adapter.

  Output from lsusb:
  Bus 001 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191S WLAN 
Adapter

  Output from uname -a:
  Linux boron 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  Output from syslog during connection attempt:
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: starting - ready
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: ready - inactive
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) starting 
connection '42'
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation 
(wlan0/wireless): access point '42' has security, but secrets are required.
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:47:50 boron NetworkManager[950]:keyfile: updating 
/etc/NetworkManager/system-connections/42
  Oct 16 02:48:11 boron NetworkManager[950]: get_secret_flags: assertion 
`is_secret_prop (setting, secret_name, error)' failed
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: need-auth - prepare (reason 'none') [60 40 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation 
(wlan0/wireless): connection '42' has security, and secrets exist.  No new 
secrets needed.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'ssid' value 
'*'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'scan_ssid' 
value '1'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'key_mgmt' 
value 'NONE'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'wep_key0' 
value 'omitted'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 
'wep_tx_keyidx' value '0'
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: set interface 
ap_scan to 1
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: inactive - scanning
  Oct 16 02:49:11 boron NetworkManager[950]: warn Activation 
(wlan0/wireless): association took too long.
  Oct 16 02:49:11 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:49:11 boron NetworkManager[950]: warn Activation 
(wlan0/wireless): asking for new secrets
  Oct 16 02:49:11 boron NetworkManager[950]: warn Couldn't disconnect 
supplicant interface: This 

[Desktop-packages] [Bug 875424] Re: unable to connect to encrypted access point with r8712 driver

2011-12-29 Thread Zilvador
I have had the same problems ince the upgrade from Natty in October and
it is really becoming a pain.

My data from lsusb does not contain any information about WLAN, so I
cannot say if I use the same driver.

My WLAN card is :
- product: AR928X Wireless Network Adapter (PCI-Express) [168C:2A]
- vendor: Atheros Communications Inc. [168C]

I hope something will be done about it soon or at least a solution
strategy will be known. So far Wicd has helped me a few times, but other
updates since the upgrade seem to make it worse.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/875424

Title:
  unable to connect to encrypted access point with r8712 driver

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Wifi was working without issue under Ubuntu 11.04. After upgrading to
  Ubuntu 11.10 Wifi will not connect if the access point has encryption
  enabled.

  r8712u module is being loaded for Wifi adapter.

  Output from lsusb:
  Bus 001 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191S WLAN 
Adapter

  Output from uname -a:
  Linux boron 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  Output from syslog during connection attempt:
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: starting - ready
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: ready - inactive
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) starting 
connection '42'
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation 
(wlan0/wireless): access point '42' has security, but secrets are required.
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:47:50 boron NetworkManager[950]:keyfile: updating 
/etc/NetworkManager/system-connections/42
  Oct 16 02:48:11 boron NetworkManager[950]: get_secret_flags: assertion 
`is_secret_prop (setting, secret_name, error)' failed
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: need-auth - prepare (reason 'none') [60 40 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation 
(wlan0/wireless): connection '42' has security, and secrets exist.  No new 
secrets needed.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'ssid' value 
'*'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'scan_ssid' 
value '1'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'key_mgmt' 
value 'NONE'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'wep_key0' 
value 'omitted'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 
'wep_tx_keyidx' value '0'
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: set interface 
ap_scan to 1
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: inactive - scanning
  Oct 16 02:49:11 boron NetworkManager[950]: 

[Desktop-packages] [Bug 875424] Re: unable to connect to encrypted access point with r8712 driver

2011-10-20 Thread SJI
If I delete the network connection details from /etc/NetworkManager
/system-connections and then recreate the connection it will connect and
work fine. If the connection is lost or I reboot the connection fails
and I have to delete the connection and recreate it again.

Additionally, when the connection fails I am prompted to enter the WEP
key in a dialogue box. If I ignore the dialogue box another will
eventually appear, and another, and...  I gave up at 15 dialogue boxes.

** Package changed: ubuntu = network-manager (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/875424

Title:
  unable to connect to encrypted access point with r8712 driver

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Wifi was working without issue under Ubuntu 11.04. After upgrading to
  Ubuntu 11.10 Wifi will not connect if the access point has encryption
  enabled.

  r8712u module is being loaded for Wifi adapter.

  Output from lsusb:
  Bus 001 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191S WLAN 
Adapter

  Output from uname -a:
  Linux boron 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  Output from syslog during connection attempt:
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: starting - ready
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
  Oct 16 02:47:25 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: ready - inactive
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) starting 
connection '42'
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation 
(wlan0/wireless): access point '42' has security, but secrets are required.
  Oct 16 02:47:49 boron NetworkManager[950]: info (wlan0): device state 
change: config - need-auth (reason 'none') [50 60 0]
  Oct 16 02:47:49 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:47:50 boron NetworkManager[950]:keyfile: updating 
/etc/NetworkManager/system-connections/42
  Oct 16 02:48:11 boron NetworkManager[950]: get_secret_flags: assertion 
`is_secret_prop (setting, secret_name, error)' failed
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) started...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: need-auth - prepare (reason 'none') [60 40 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) scheduled...
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 1 
of 5 (Device Prepare) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) starting...
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): device state 
change: prepare - config (reason 'none') [40 50 0]
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation 
(wlan0/wireless): connection '42' has security, and secrets exist.  No new 
secrets needed.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'ssid' value 
'*'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'scan_ssid' 
value '1'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'key_mgmt' 
value 'NONE'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 'wep_key0' 
value 'omitted'
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: added 
'wep_tx_keyidx' value '0'
  Oct 16 02:48:11 boron NetworkManager[950]: info Activation (wlan0) Stage 2 
of 5 (Device Configure) complete.
  Oct 16 02:48:11 boron NetworkManager[950]: info Config: set interface 
ap_scan to 1
  Oct 16 02:48:11 boron NetworkManager[950]: info (wlan0): supplicant 
interface state: inactive - scanning
  Oct 16 02:49:11 boron NetworkManager[950]: warn