plasma widget networkmanager couldn't connect wpa

Bug #378145 reported by Ömer Fadıl USTA
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
knetworkmanager
Fix Released
Unknown
plasma-widget-network-manager (Ubuntu)
Triaged
Medium
Unassigned
Nominated for Karmic by Ömer Fadıl USTA

Bug Description

Binary package hint: plasma-widget-network-manager

The current version of plasma-widget-network-manager ( plasma-widget-network-manager_0.0+svn966653-0ubuntu1 ) has a wpa connection BUG.

Solution : Downgrading to plasma-widget-networkmanagement_0.1~svn951801-1

1- sudo apt-get remove plasma-widget-network*
2- download older version from :
http://ftp.us.debian.org/debian/pool/main/p/plasma-widget-networkmanagement/plasma-widget-networkmanagement_0.1~svn951801-1_i386.deb
3- install it :
sudo dpkg -i plasma-widget-networkmanagement_0.1~svn951801-1_i386.deb
4- reboot system
5- Thats all now your wpa connection starts to work

Revision history for this message
BluesKaj (blueskaj) wrote :

Yes , this insstall/ fix worked for my Belkin USB rt2870 driver (WPASPK), which wasn't working with svn966653-0ubuntu1.

Revision history for this message
Per Hermansson (hermansson-per) wrote :

Hi, would it be possible to test the new version again and attach your /var/log/daemon.log (only lines starting with Network Manager are interesting for me).
(Between those two revisions I've got some patches committed that was supposed to get WPA to work, so I would be happy to see why it now fails for you)

Revision history for this message
BluesKaj (blueskaj) wrote : Re: [Bug 378145] Re: plasma widget networkmanager couldn't connect wpa

Per Hermansson wrote:
> Hi, would it be possible to test the new version again and attach your /var/log/daemon.log (only lines starting with Network Manager are interesting for me).
> (Between those two revisions I've got some patches committed that was supposed to get WPA to work, so I would be happy to see why it now fails for you)
>
>
Hi Per,
 Yes certainly , here is the logfile you requested . I hope it helps
                 Good Luck,
                  BluesKaj

Revision history for this message
robin0800 (robin-linux-hotmail) wrote :

Its still not working here the error is in the plasma-widget-network-manager which I have not seen an update to.
 The error line from daemon log

Trying to associate with 00:17:3f:5c:b2:ff (SSID='belkin54g' freq=2412 MHz)
May 19 14:57:37 Robins-Laptop wpa_supplicant[3421]: Association request to the driver failed

Hope this helps

Revision history for this message
Per Hermansson (hermansson-per) wrote :

I've looked at the log but Network Manger doesn't seem to report any problems. Only the same line about "Association request to the driver failed" makes me think this is not related to plasma-widget-network-manager.
I've build the 0.0+svn966653-0ubuntu1 version from Karmic and it works without problems for me under Jaunty with WPA-PSK.

Are all of you testing this on Karmic or Jaunty?

Revision history for this message
robin0800 (robin-linux-hotmail) wrote :

For your information I'm on Karmic and I think the bug must be in The Plasma network widget As the solution in the second post says .......

"Solution : Downgrading to plasma-widget-networkmanagement_0.1~svn951801-1"

is what clears the bug.

Revision history for this message
BluesKaj (blueskaj) wrote :

Per Hermansson wrote:
> I've looked at the log but Network Manger doesn't seem to report any problems. Only the same line about "Association request to the driver failed" makes me think this is not related to plasma-widget-network-manager.
> I've build the 0.0+svn966653-0ubuntu1 version from Karmic and it works without problems for me under Jaunty with WPA-PSK.
>
> Are all of you testing this on Karmic or Jaunty?
>
>
Per,
Using Karmic here. Rolled back the plasma-widget-network-manager to the
svn951801-1 version, which worked perfectly after installing.

Revision history for this message
Per Hermansson (hermansson-per) wrote :

Great new (sort of). I've now installed Karmic and tested WPA-PSK and I'm now experiencing the same problem as you guys.

Since the same version works for me in Jaunty the problem most be in combination with a new version of some other component. My guess is either wpa_supplicant or KWallet manager (since it kept asking me for a correct wpa key) is to blame, but I'll investigate this further.

Revision history for this message
Ömer Fadıl USTA (omerusta) wrote :

@Per Hermasson:
Could you please try these steps ?
1- sudo apt-get remove plasma-widget-network*
2- download older version from :
http://ftp.us.debian.org/debian/pool/main/p/plasma-widget-networkmanagement/plasma-widget-networkmanagement_0.1~svn951801-1_i386.deb
3- install it :
sudo dpkg -i plasma-widget-networkmanagement_0.1~svn951801-1_i386.deb
4- reboot system
5- Thats all now your wpa connection starts to work
and write results to here

Revision history for this message
Per Hermansson (hermansson-per) wrote :

Yes, that version works (for the record I'm using an amd64 system). The next step would be to build and test different subversion revision to find where things start to break.

Revision history for this message
Ömer Fadıl USTA (omerusta) wrote :
Changed in plasma-widget-network-manager (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in knetworkmanager:
status: Unknown → New
Changed in knetworkmanager:
status: New → Confirmed
Changed in plasma-widget-network-manager (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

same problem with wep.

Changed in knetworkmanager:
status: Confirmed → Fix Released
Revision history for this message
Erasmosis (barukh) wrote :

I had the same problem. It has been reported elsewhere, https://bugs.launchpad.net/bugs/392593

I installed removed network manager and installed Wicd, and that seems to have worked for me.

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

Other bug subscribers

Bug attachments

Remote bug watches

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