Hi,
will it ever work? We have 2009 now and I can’t use networkmanager-kde with WPA2 Enterprise. I can see the network, I can try to connect… and that’s all.
I’ve tried Gnome LiveCD and everything worked just fine. Where is the problem then?
HW: ThinkPad R61 with Intel 4965, EEE 1000h with some realtek, EEE 1005HA… anything i could find here.
Networkmanager is throwing me the window with network settings (like password, username, certificate etc.) after each attempt to connect (all data are correct). Nothing more.
Until someone provides you with a better answer, I wonder if the Gnome front-end (NetworkManager-gnome) might make the difference? You will need to install gnome-keyring package as well. (Your software manager will take care of any dependent packages).
Same kind of problem discussed in this Ubuntu thread.
Yes, the problem is only in KDE frontend to network-manager. I could use the gnome one, but i would like to have a consistent desktop (i just don’t like Gnome :)).
At the moment I am using Gnome frontend and everything works well. But this problem is known since the first version of KDE (or KDE frontend to network manager) was released
It makes me sad because it looks like developers are too busy making new shiny graphic efects and they don’t have time for fixing annoying bugs (i know - they are just people, but…).
I would even pay for fixing this bug (I think I’m not the only one with this idea). As a student I can’t afford much, but there is more people willing to pay for this.
I hear you. I feel the same way… and given that they are both developed in an open source environment, one would wonder why they can’t bug fix (by looking at each others functionality and code for example).
On 11/13/2009 02:56 AM, stenliq wrote:
>
> Thank you for your reply.
>
> Yes, the problem is only in KDE frontend to network-manager. I could
> use the gnome one, but i would like to have a consistent desktop (i just
> don’t like Gnome :)).
>
> At the moment I am using Gnome frontend and everything works well. But
> this problem is known since the first version of KDE (or KDE frontend to
> network manager) was released
>
> It makes me sad because it looks like developers are too busy making
> new shiny graphic efects and they don’t have time for fixing annoying
> bugs (i know - they are just people, but…).
>
> I would even pay for fixing this bug (I think I’m not the only one with
> this idea). As a student I can’t afford much, but there is more people
> willing to pay for this.
Are you using “Connect to Other Networks” to try to connect, or are you using
“Manage Connections”? The latter will work and the former will not. This
situation is a problem with NM, not with openSUSE and has nothing to do with
shiny graphics, or any other conspiracy theory.
1.) I click on it, select “Create network connection…”.
2.) Then I select wireless network I’d like to connect to (the one named “SH” in my case).
3.) I’m asked for username, password, certificate, etc.
After clicking OK, tray icon says “Activating” and after a while (sometimes quite long) the window from step 3 shows again…
On 11/13/2009 08:46 AM, stenliq wrote:
>
> Does anyone have account on bugs.kde.org and is willing to report bug? I
> suppose there is no point in reporting on SUSE bugzilla…?
Report it on the NetworkManager bug list. They are responsible for the kNM
applet, not KDE.
According to our wiki (Wifi - wiki.siliconhill.cz - CZ only ) I have to set AES cypher if I want to connect. It’s the only thing I can’t see (and set) in the kde-networkmanager. Is there any way to do it?
