Bug 225115 - If wireless network is gone, Knetworkmanager should not ask for password
Summary: If wireless network is gone, Knetworkmanager should not ask for password
Status: RESOLVED FIXED
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
: 243715 263567 268990 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-01 11:03 UTC by m.wege
Modified: 2011-08-25 20:04 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: nm09 branch


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2010-02-01 11:03:59 UTC
Version:           Unbekannt (using 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-18-generic

If I disable my wireless network in the router, because it is not needed and then my laptop looses the connection. Knetworkmanager pops up with a password-request for that network, as if the network was still existant. I do not know what is the reason for the behaviour. If Knetworkmanager still believes the network exists or if this just a kind of standard reaction to a network that disappears and it can not reconnect. But it would be really good, if this could be just changed into a notification "Wireless network connection lost, can not reconnect".
Comment 1 Berend Dekens 2010-04-03 13:33:12 UTC
I would also like this fixed but for another reason: my IWL 4965 wifi card sometimes overheats or crashes or it crashes the router or...

The result is the inability to connect to a network which has nothing to do with authentication (I am not sure if the network is truly 'gone' or that it appears non-responsive). The result is a authentication popup which I just confirm and then it logs on fine.

The easiest 'fix' would probably be a couple of silent failures before the authentication popup shows.
Comment 2 p92 2010-06-03 01:22:56 UTC
can solve  :
#232531 There is no easy way to enable disabled networking
#235477 knetworkmanager does not have an option to enable/disable networking
#226615 network manager disabled button
Comment 3 p92 2010-06-03 02:13:57 UTC
oops sorry wrong bug - ignore comment #2
Comment 4 Lamarque V. Souza 2011-03-17 05:41:44 UTC
*** Bug 263567 has been marked as a duplicate of this bug. ***
Comment 5 Lamarque V. Souza 2011-03-21 06:24:28 UTC
*** Bug 268990 has been marked as a duplicate of this bug. ***
Comment 6 Lamarque V. Souza 2011-05-09 06:59:12 UTC
*** Bug 243715 has been marked as a duplicate of this bug. ***
Comment 7 manik chand patnaik 2011-05-09 17:12:38 UTC
This bug is recently verified on
knetworkmanager --version
Qt: 4.7.1
KDE Development Platform: 4.6.00 (4.6.0) "release 6"
KNetworkManager: v0.9
OS: Linux

This is a poorly defined bug with a long history and so I have written down the problem in detail with possible approach to triage the bug. Unfortunately this still shows UNCONFIRMED status.

When I am in an area where the wireless is not stable, Once the wireless
network becomes unavailable, an authorization dialog for WAP or other password
pops up with the stored password. User can click on a box to see the existing
password there and can modify it. This is an insecure practice.
If the wireless becomes available, the password dialog does not go as it is a
dialog and waiting for response. So when my wireless network is not good, There
is no hope of reconnect.
In other words, Knetworkmanager always needs to be attended to. I cannot give a
download and leave the system on its own if the wireless is not stable.

In short the password prompt is the problem, it should not show at all. After
strength comes back, knetworkmanager should try to reconnect.

Reproducible: Always

Steps to Reproduce:
1 connect to wireless network
2 go a bit far where the signal is low, disconnection will occur
3 password prompt will be shown by knetworkmanager
4 come back to high strengh area


Actual Results:  
result: the password prompt remains, does not reconnect.

Expected Results:  
not show password prompt because it is rare that the password changes often.
networkmanager should reconnect once wireless strength returns.

Where is the problem and how to triage the bug:
When signal strength falls, the network disconnects. The program assumes that authentication has failed and opens the password dialog. The programmer should try to fix the behaviour by monitoring the signal level. If the signal level is below a threshold, the password dialog should not show and the disconnection message should show (currently both shows). When signal returns, the program should try to automatically connect with the saved password. (Currently the program monitors the signal level and tries to connect when the signal comes but this action is hindered by the already open password dialog). An authentication failure only should prompt the password dialog to be shown. 

PLEASE : 
Vote for the bug and escalate it.
If you can hack try to patch it and post the patch.
Will is too busy with Kopete, Kontact, Groupwise etc. Wake him up!
Pay someone who can patch it!
Please DO SOMETHING!
Comment 8 arne anka 2011-05-09 20:25:02 UTC
not sure, if my report #268990 really is a duplicate:
what i am talking about is that even after manually disabling the wifi-adapter (fn+key) the dialog pops up, fully ignoring the fact that _no_ wifi adapter is available anymore!

from the description above it seems that this is a completely unrelated misbehaviour!
Comment 9 Daniel Mader 2011-05-09 20:50:04 UTC
(In reply to comment #8)
> from the description above it seems that this is a completely unrelated
> misbehaviour!

Actually, this is not unrelated at all. In both cases, the wifi connection breaks. Either because the signal is to weak or because the adapter has vanished completely.

Now, the problem is that knetworkmanager is so dumb that it can't handle that gracefully but seems to think that credentials are necessary.
Comment 10 Lamarque V. Souza 2011-08-25 20:04:54 UTC
I think this is problem on how NM-0.8 works, it is the daemon that asks for the password.

Anyway, NM-0.9 asks for connection's secrets (password and encryption keys) only once per KDE session (at most), so upgrade to NM-0.9 and problem solved. Plasma NM for NM-0.8 is going to be deprecated since NM-0.9 final has been released this week.