I deny that it works for me. I am using ipw3945 to connect to an AP
WITHOUT any WEP or WPA, so maybe it's a different bug. But the point is,
nm-applet can not join networks UNLESS I RUN IT AS ROOT. Then it can
attach as it is supposed to. Otherwise, I have to sudo dhclient eth1 (my
ipw3945 lives there.) I just updated today. I see this bug is still
open. Maybe my problem is different, but my description is identical...

eth1      IEEE 802.11g  ESSID:"Wireless"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:0F:CC:29:A6:78   
          Bit Rate:54 Mb/s   Tx-Power:15 dBm   
          Retry limit:15   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=81/100  Signal level=-57 dBm  Noise level=-57 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:157   Missed beacon:0

It's in a hotel, this is not my imaginative ESSID. Doesn't work at home
associating to my 802.11b Linksys either (WAP11 or something like that,
I forget, I'm not there right now.)

Attached is a daemon.log from the last time I tried it and failed a
bunch of times. Right now I have it running as root (and working
correctly.)

** Attachment added: "daemon.log.bz2"
   http://launchpadlibrarian.net/12117865/daemon.log.bz2

-- 
[ipw3945] nm-applet doesn't work unless I start dhclient manually
https://bugs.launchpad.net/bugs/127649
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to