Bug 682922 - KDE Network Manager does not connect to WLAN with hidden ESSID
Summary: KDE Network Manager does not connect to WLAN with hidden ESSID
Status: VERIFIED FIXED
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.4
: P5 - None : Major with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-28 00:23 UTC by Forgotten User 0EFFxZV8cC
Modified: 2012-11-15 23:21 UTC (History)
4 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User 0EFFxZV8cC 2011-03-28 00:23:54 UTC
This problem seems to affect OpenSuse 11.4 KDE and other Linux Distros based on KDE4. It seems that that bug was repeatedly reported to the KDE team more than a year ago. Nobody there seems to be capable or willing to fix it. Suggest OpenSuse offers a solution (i.e. alternate network manager) until KDE fixes this bug.
Comment 1 Bill Wayson 2011-04-01 15:28:03 UTC
This problem existed for me after installing openSUSE 11.3.  I assume it still exists in 11.4, but I upgraded.  A (not ideal) workaround is to temporarily expose your WLAN's ESSID, then set up the connection in Network Manager.  Once the setup is complete, you can hide the ESSID again.  The connection should continue to appear and work in NM -- it does for me.  By the way, this issue did not exist using Ubuntu 10.4 and Gnome via dual booting on the very same laptop.
Comment 2 Massimo Spiller 2011-07-08 07:28:45 UTC
...temporarily expose ... NOT in real world (where you use AP set up by other people)!

We need a fix or a new gui interface. Sad that all action is just wait for KDE ... (until when? 11.5?)
Comment 3 Till Dörges 2012-09-09 14:07:04 UTC
The problem still exists in 12.1.

Installed packages are the default ones from the distribution:

--- snip ---
$  rpm -qa | egrep 'kernel-d|NetworkM' | sort
NetworkManager-0.9.1.90-4.8.1.x86_64
NetworkManager-kde4-libs-0.9.1+0.9.0-1.6.1.x86_64
NetworkManager-kde4-libs-lang-0.9.1+0.9.0-1.6.1.noarch
NetworkManager-openvpn-0.9.0-2.1.2.x86_64
NetworkManager-openvpn-kde4-0.9.1+0.9.0-1.6.1.x86_64
NetworkManager-openvpn-lang-0.9.0-2.1.2.noarch
NetworkManager-pptp-0.9.0-3.1.2.x86_64
NetworkManager-pptp-kde4-0.9.1+0.9.0-1.6.1.x86_64
NetworkManager-pptp-lang-0.9.0-3.1.2.noarch
NetworkManager-vpnc-0.9.0-2.1.2.x86_64
NetworkManager-vpnc-kde4-0.9.1+0.9.0-1.6.1.x86_64
NetworkManager-vpnc-lang-0.9.0-2.1.2.noarch
kernel-default-devel-3.1.10-1.16.1.x86_64
kernel-desktop-3.1.10-1.16.1.x86_64
kernel-desktop-devel-3.1.10-1.16.1.x86_64
kernel-devel-3.1.10-1.16.1.noarch
--- snap ---

After having added/configured the connection through the nm-applet, no connection is actually made.

If I manually do

--- snip ---
iwlist wlan0 scan essid <HIDDENSSID>
--- snap ---

the connection does appear in the nm-applet and can be used.
Comment 4 Till Dörges 2012-09-09 14:09:35 UTC
This appears to be related to bug 541009 and to bug 689245.
Comment 5 Forgotten User DV81ZEWZkN 2012-11-15 23:21:12 UTC
Closing, 11.4 reached EOL, if you can reproduce with >= 12.1 open a new BR.