Bug 723072

Summary: Attempt to connect to wireless AP results in "Waiting for authorization" until timeout.
Product: [Fedora] Fedora Reporter: Anatoly Solomin <anatoly.solomin>
Component: kde-plasma-networkmanagementAssignee: Rex Dieter <rdieter>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: anatoly.solomin, kevin, ltinkl, rdieter, thibault.north
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-12 22:51:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anatoly Solomin 2011-07-18 22:55:27 UTC
Description of problem:
It is impossible to connect to a wireless AP

Version-Release number of selected component (if applicable):
0.9-0.53.20110616git.nm09
which came to me automatically from "updates", not from "updates testing"

How reproducible:
Always

Steps to Reproduce:
1.In the "Manage Connections" -> "Wireless" -> "Add, Edit and Remove network connections" Add a new connection to the desired AP, type in the proper password and check boxes "Connect automatically" and "System connection". Then Apply, OK.
2.Try to connect to this AP

  
Actual results:
At first it is "Configuring interface" and then - "Waiting for authorization" until time-out happens. But no appropriate pop-up window appears. And after that "Connection ... failed"

Expected results:
"Waiting for authorization" should result in appearing of a pop-up window that asks for the password (which is in fact already typed in, but with fat black dots) and after I confirm - connection establishes.

The result is "Expected" de-facto only, because I would expect that it would connect silently, since I defined it to connect automatically and permitted to use Wallet to retrieve the password when needed.

Additional info:
Even the above "Expected results" is not always the case, because very rarely the connection happens seamlessly, by itself... IMHO, this indicates that there might be several bugs around that problem.

I also confirm, that it was possible to type in a "hidden" network, but the "return" did not do anything... But I have not tested it with this particular version yet... because I had to un-hide my network...

On fedora 14, the 1:0.9-0.41.1.20110616git.fc14 works, not ideally, but works somehow, at least if I un-check "Enable networking" and then check it again, the connection succeeds. Although there is a lot of mess around this point anyway. The behaviour is unstable in sort-of random way. It would take a lot of testing and time to document all nuances.

Additionally, I observe that old MacBook Pro with Snow Leopard connects to this AP automatically ALWAYS, invariably. Same with Windows 7 (although I use it rarely). This means that the router is unlikely to be an issue.

True, the plasma does not crash any more, but the main problem (practically impossible to connect) persists, unfortunately.

Comment 1 Lukáš Tinkl 2012-06-12 15:05:46 UTC
Does this still happen with F17?

Comment 2 Anatoly Solomin 2012-06-12 17:04:13 UTC
I'll let you know in a  few days when I install F17.

In fact, in F16 I do not see that thing for quite some time. But, I must admit, I switched from an old Belkin ADSL modem to a more contemporary Cisco EPC2325 cable modem...

- Anatoly

Comment 3 Kevin Kofler 2012-06-12 22:51:25 UTC
If it's already fixed in F16, that's even better. :-)

Closing as no longer reproducible.