Ubuntu
knetworkmanager package

KNetworkManager connect button disabled w/stored key

Bug #158433 reported by Barrakketh on 2007-10-29

Affects		Status	Importance	Assigned to	Milestone
	knetworkmanager (Ubuntu)	Fix Released	Undecided	Luka Renko

Bug Description

Binary package hint: knetworkmanager

Note: The application knetworkmanager is being reported by dpkg as provided by the package network-manager-kde. The version is 1:0.2ubuntu1-0ubuntu5.

I have a WPA key stored in a KDE wallet, and after inputting my password I'm presented with the "Connect to Wireless Network" dialog. The connect button is disabled (greyed out) until I alter the password field. Either deleting the last character and typing it again or simply entering a space and deleting it will enable the button. Once this is done I can connect as normal.

The above always happens after a reboot.

Revision history for this message

Barrakketh (barrakketh) wrote on 2007-10-29:

Screenshot of the disabled button. Edit (37.0 KiB, image/png)

Revision history for this message

Luka Renko (lure) wrote on 2008-04-08:

knetworkmanager 0.2.2 is now available in Hardy and have some fixes for handling KWallet passwords that can help with your problem.
Can you check if you can reproduce this with up-to-date Hardy?

Changed in knetworkmanager:
assignee:	nobody → lure
status:	New → Incomplete

Revision history for this message

Bryan Donlan (bdonlan) wrote on 2008-05-03:

Seems to be fixed in 0.2.2

Changed in knetworkmanager:
status:	Incomplete → Fix Released

Revision history for this message

asdf (asdf2468-deactivatedaccount) wrote on 2008-10-28:

Dear Kubuntu people,

I have tried out Kubuntu 8.4 because I like KDE 3.5 very much, it is very stable. I tried to connect to my wireless network, but I had a problem. After searching on Google I ended up on this page, so I hope my additions will be valuable.

I right-clicked the KNetworkManager icon to connect to my Wireless network. I selected my network and it prompted for my key (I think WEP or WPA or so), however the 'Connect' button stayed disabled. I went to another computer and visited the configuration page of my router where my key is displayed. It turned out I had my key all wrong.

I was trying to type in a password (stupidly enough, my router password), but whilst typing the button remained disabled. However after a certain amount of characters, the button became enabled. I then occurred to me that probably there is a minimum length of the key, which was not met by the shorter password I tried to enter.

It would be far more clear if either of the following happened:
- Connect button is enabled, I try to click it and a message appears saying that it is wrong (it knows so by seeing it's not long enough), or
- When the key is not long enough it should display a message or something similar indicating that.

In either case I would have known that the key I was trying to enter was in fact invalid, because it simply was too short, instead of me getting frustrated and wondering why the button was disabled (I honestly thought there was a defect with the program).

I hope this information helps you make a better product in the future (not that I'm implying it's not good now, because it sure is for the most part).

Kind regards,
Paul