[karmic] networkmanagement plasma doesn't connect to wireless networks

Bug #416041 reported by nowardev
58
This bug affects 7 people
Affects Status Importance Assigned to Milestone
plasma-widget-networkmanagement (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On jaunty with kde 4.3 i can use wifi network without problems. with wpa-psk

on live cd with kde 4.3 it doesn't want connect. Clicking the wireless connection listed and/or entering the password for a connection doesn't cause an attempt to connect to the wireless network.

Revision history for this message
Joe Mulloy (jdmulloy) wrote :

Same problem for me with Kubuntu Karmic Alpha 4.

KDE version of NM finds the wifi and prompts for the passphrase but never actually connects.

I've been using WICD, but when I wiped my laptop and installed Karmic I decided to give NM another chance.

Now I've ripped out NetworkManager which is pure garbage and install WICD, and it works flawlessly, like it always has.

Network Manager is overly complex for what it does and very buggy. WICD follows the unix philosophy of keeping things simple and doing one thing and doing it well.

Network Manager SUCKS!!!!!!!!!!!!!!

Revision history for this message
Stéphane (racoonator) wrote :

I've the same problem with Kubuntu Karmic Alpha 4 installed on my Asus A3N.

I don't test Wicd, just try to connect with Network manager after a fresh install. I see the network all around me, select mine, type passphrase, select wpa-psk and... nothing, no connection.

The wifi card is an Intel 2200 if my memory is good (I don't have the computer with me to verify now).

I'm Ok to send all the informations needed to help to resolve this problem.

Stéphane

Revision history for this message
nowardev (nowardev) wrote :

Joe...*network manager sucks...

well on jaunty works fine (dhcp..)

is on karmic that doesn't work and this freaking thing is very very very very very bad for a linux distribution

network is very important for the use of linux but is very important to fix problems .... that one could have with his hardware...

i am a kubuntu user since 2006-2007 and kde stuff has always problems with networking much more than ubuntu and not because of kde ...

as i said on jaunty NM +kde 4.3 works fine.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Hopefully I've got the right package for this.
Looks to me like an issue specific to the plasma widget, and not to network-manager or the applet, as removing the widget and starting nm-applet, the connections are usable and will connect successfully.
Marking the bug as confirmed since I can reproduce it, and use the workaround above to bypass this limitation.

affects: network-manager (Ubuntu) → plasma-widget-networkmanagement (Ubuntu)
Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
description: updated
summary: - Regression network-manager doesn't work on karmic koala and kde 4
+ [karmic] networkmanagement plasma doesn't connect to wireless networks
Revision history for this message
nowardev (nowardev) wrote :

you have to give me an explanation why on jaunty works and on karmic not...

kde is the same but the results are different .

what a shame stuff for canonical always always always this freaking problem on networking... i can understand why every time there are these issues.

Revision history for this message
poet_imp (paul-lemmons) wrote :

I started experiencing this at plasma-widget-networkmanagement 0.1~svn1002781-0ubuntu2~jaunty1~ppa1

When that update was applied I could then see wireless networks but I could not connect to any of them. When I hovered over the icon the pop-up said "Unavailable" as opposed to "Not Connected".

Wired connection was successful.

Is thing nm-applet has me working again, however, I do look forward to this getting resolved.

Revision history for this message
shiftless (shiftless) wrote :

This doesnt work for me on 4.2 OR 4.3. No wireless networks are found. Wicd works flawlessly. Please fix network manager, its GARBAGE.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I believe that a lot of these issues were caused by updates that caused network configurations from older versions to not work. Unfortunately, since the symptom is quite broad "NetworkManager won't connect is is teh suxX0rs" it attracted comments from many people who could have been seeing different symptoms, and as a result this bug is now an unsortable mass of such comments.

If, after deleting old connections and creating new ones the connections still refuse to connect in Kubuntu 9.10 (with the latest updates applied of course), we would like for you to file separate reports here at Launchpad using the following page as a guide for providing detailed information. http://userbase.kde.org/NetworkManagement We would like this to be as separate reports so that peoples' reports don't become tangled up and when one person's stuff is fixed, whereafter people start complaining that their problem isn't fixed since it was an entirely different issue in the first place.

Thank you for your understanding, and have a nice day.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
nowardev (nowardev) wrote :

mmm
what kind of thinking have you done?

the problem IS ON LIVE CD !!

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Abdelatif Adel (abitaf) wrote :

I did a fresh install not an update of karmic alpha5 and still have the same problem !

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Without info, we cannot do anything. Please re-read my comment and provide the requested information, preferrably in one separate bug report per person.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Katsudon (katsudon) wrote :

I can confirm that removing all connections and then adding them back solved the problem in my case.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.