Bug 444733

I second this bug ... my goodness what happenend here?!?

I went from an albeit not perfect KNetworkManager at least a Network Manager that would let me connect to 1: my homenetwork with WPA/WPA2 and 2: my university network with WPA/WPA2 Enterprise with EAP-TTLS ... out of the box! I even assisted in several bug reports to get that working. Thanks again Helmut Schaa. :)

But what now?!?

1: As the Network Manager plasmoid starts up it shows all 20 wifi networks availalbe in the neighbourhood, filling a large portion of my screen for a few second before disappearing again - why I don't know, it went to fast to see anything anyways.

2: When you click the (much more ugly icon) I get an unmovable window (except by pressing ALT) that looks *ugly*, and which allows me to do ... nothing. Well except turn my wireless off. But:
- I can't connect to *any* wireless network, WPA, WEP or otherwise ... pressing on the 'Play' icon does ... nothing, it doesn't even ask me for credentials. 

3: Next thing I know, it crashes ... and the whole of plasma with it (wtf?!?) taking down the whole layout at well (the entire taskbar is turned around) and to top that it makes the Network Manager icon transparant (good luck finding it).

In short we went from a very usuable, very good workin KNetworkManager that allowed me to do my work. To ... something that turns your laptop in a very expensive paperweight.

My advice: make a good attempt to get rid of the aforementioned bugs but *also* make sure it's still possible to start KNetworkManager from the Live CD!!!

Interesting ... When you install KNetworkManager and start it up it crashes Plasma (again), kills the Network Manager applet but then the KNetworkManager works as it used to. When you then start the Network Manager widget then suddenly it seems to come to live and the buttons and controls work, it seems to be tapping into the (K)NetworkManager backbone, just provindg a different GUI.

Seems like someone forgot to pack the KNetworkManager with this beta 5 :)

Please try NetworkManager-kde4 package from http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_Factory/ - it may resolve some of your problems.

I resolve a few bugs, but too many remain. There are really too many bugs to list almost.

1: Still whenever you start the widget it will fill your screen with pop-up notifications: this, this, this, this, etc, etc. network is available. What information does this provide when you have 20+ networks in your neighborhood (not uncommon in cities).
2: When you click the widget's icon (which is at least visible now) you only get to see a few of the network available, more precisely only the networks I have ever been connected to and a profile exists in KNetworkManager. It doesn't show me 'fresh' network I might want to connect to.
3: It's not easy to add a new network, you have to click 'Manage...' and then 'Add' and then 'Scan' to see what Networks are available. Everything is then put int a tiny tiny 'graph' [1] where all the SSID's are shortend to 3-4 characters (good luck identifying the 4 networks that begin with 'Speedtouch'). Click the 'Details' tab doesn't help much either since the windows don't resive automatically. So the names are still 3-4 characters short. [2]
4: Constant pop-ups 'Network is available', 'Network is unavailable' are annoying. Also all notifications for me appear double so for each event I get two simultaneous events.
5: all my in KNEtworkconfigured profiles are not visiable in the 'Manage' window, even though I am connected to it.
6: in the pop up when you the 'Stop' buttons overlaps with the SSID text.

I'm sure there are many more but most of them are technical issues that should probably be reported seperatly, like the lack of WPA Enterprise, WPA2, AES/CCMP TKIP and all those things.

[1] http://img216.imageshack.us/my.php?image=sc0lb4.png
[2] http://img409.imageshack.us/my.php?image=sc1ya5.png

I also have a trouble with knetworkmanager : I cant create wired connection with static IP, clicking by button Add for add an IP just do nothing.

I like the more technical approach of this new networkmanager. However, the wireless "scan" window, although being a very promising element of it - is still badly arranged.

Beside this suggest to include the challen number AND the frequency for every access point.

In addition to these "minor" bugs, it still doesn not suport WPA-enterprise, and in spite of the fact that it promises to support unencrypted WLANS, it does not connect to them. (May it be related to https://bugzilla.novell.com/show_bug.cgi?id=444740 ?)

Moreover, it shows every (even WPA-enterprise type) network with an open lock, which may make users to think, those are open networks. BTW, it's all the same when WLAN connection is totally impossible with any versions of KDE.

And please, do not forget that https://bugzilla.novell.com/show_bug.cgi?id=444364 still applies to Beta-5!

Trying to connect to my wireless access point simply 
is without any action (as reported above).

Furthermore I would like to mention that configuring
knetworkmanager for my access point saves my
WEP ascii key in hexadecimal format. 

It does this as well configuring knetworkmanager in KDE3.

1. White big and very ugly icon.
2. Few wireless networks in main panel.
3. Sometimes (like wired connection) button is on the text.
4. More complicated addind new connection:
a) I can't resize elements in detail or map
b) why in main position is BSID, MAC elements. That's could it be in advanced panel
c) to much clicking Icon->Manage->Wireless->Add->Scan->Detail (becasuse this map is the worst idea what I can image)
5. The most important bug I can't connect with any connection point.

My opinion about that is, why did you add this in Beta5 (exactly RC1 with official roadmap). It's no Alfa version.

the priority is not for reporters

... and we're back to kde3 applet

When the kde4 networkmanager applet is installed, notifications can be disabled from system settings > notifications. Seems like every single notification is turned on by default. It would make more sense to turn them all off by default and let the user configure which events they want to be notified of. 

The kde4 applet has a ton of potential, but right now, it crashes every 2 minutes and lacks the ability to connect to wireless networks. Manually connecting to a wired network is a crap shoot - the play button works only when it wants to. I doubt all the major problems can be fixed by the GM release, but more power to the guys working on it.

FYI- I reported the alerts scrolling up the middle of the screen issue in Bug 447122. I was told it's fixed in KDE 4.2 and haven't heard back about a workaround. Frankly, I think this is a big enough issue that a backport of the fix, or some sort of work around should be possible. The way it functions now is completely unusable.

FYI- one workaround to at least stop the sometimes constant "found wireless
network" and "lost wireless network" messages scrolling up the middle of the screen (actually a KNotify4 bug) is to go into Configure Desktop >
General > Notifications, change the Event source to Network Management Events,
then uncheck the "show a message in a popup".

Have added bug #458933 and bug #458937 to this pile ...

Sorry; ignore me, those are about the KDE3 version...

@William Stephenson: when you can release a usable version?

at the moment I can't set up a manual IP. The button "add ip address" doesn't work.
btw.. why starts the dialog with enter a MAC-address to overwrite??

it doesnt remember ip-address setting: i choose manual, but it stays at dhcp

Regarding this bug and Bug #449850, if I understand the situation correctly, there was a major change in the code for "11.1 Final" and all the comments before Comment #17 in this report are outdated, and the whole of Bug #449850 is outdated.  Comment #17 on Dec. 28, 2008 should be regarding "11.1 Final" and should be current.  But there has been no follow-up for Comment #17.

I have bugs and issues to report regarding "11.1 Final" but I think I would rather start a new Report to avoid confusion.  I think these two old reports should be closed.  If Comment #17 is regarding "11.1 Final", then I think that Nick could open a new bug report too.

Is this acceptable to everyone?

fine with me. i only hope networkmanager-kde4 will be polished in time for opensuse 11.2

I have closed Bug #449850 and am closing this bug as well, as per our discussion, and no responses after #19.

Nick, I just received a bunch of bug fixes today, and one of them seems to have had some small effect on the operation of the Network Manager.  If you have not tried it lately, you might want to make sure you are fully updated, and give it a try before following up on this issue.

I will be opening a new Report, but I am not sure what is going to happen to it.  It is going to be a bit vague at first.  The core issue is that what I am finding is that I can use WiFi on the "root" account, but not in a "non-root" account.  We will see where it goes from there.

Again, I am closing this one as "Invalid" since I do not know what will happen with the code that was used early in the Betas and RCs, nor whether the current code will be used in the future.  We only know that the previous problems were related to the earlier code.

I have opened the new report as Bug #474965.  If you are having the same problem, you can check it out.