Wifi usb Key DWL-G122 not working

Is this symptom still reproducible in 8.10 or 9.04?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

I have a similar symptom in karmic (9.10) 32 and 64 bit system using a DWL-G122 Rev. B1.
When I try to connect to the access point the protocol negotiation seems to work but I can't get an IP address. If I configure the stick manually I can't ping anywhere, not even to the AP. The USB-Adapter worked in Ubuntu 9.04 and 8.10 without any problems.
lsusb reads:
xxx@dimension-e521:~$ lsusb
Bus 002 Device 004: ID 0d8c:0006 C-Media Electronics, Inc. Storm HP-USB500 5.1 Headset
Bus 002 Device 003: ID 03f0:0517 Hewlett-Packard LaserJet 1000
Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 046d:c51a Logitech, Inc. MX Revolution/G7 Cordless Mouse
Bus 001 Device 008: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. B1 [ralink]
Bus 001 Device 003: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 002: ID 0644:0200 TEAC Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

syslog shows:
Nov 9 20:19:16 dimension-e521 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 9 20:19:16 dimension-e521 NetworkManager: <info> Config: set interface ap_scan to 1
Nov 9 20:19:16 dimension-e521 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Nov 9 20:19:16 dimension-e521 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: CTRL-EVENT-SCAN-RESULTS
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: WPS-AP-AVAILABLE
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: Trying to associate with 00:24:fe:05:45:41 (SSID='FRITZ!Box Fon WLAN 7270' freq=2457 MHz)
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: Association request to the driver failed
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: Association request to the driver failed
Nov 9 20:19:18 dimension-e521 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Nov 9 20:19:18 dimension-e521 kernel: [ 3331.669709] wlan0: authenticate with AP 00:24:fe:05:45:41
Nov 9 20:19:18 dimension-e521 kernel: [ 3331.672468] wlan0: authenticated
Nov 9 20:19:18 dimension-e521 kernel: [ 3331.672473] wlan0: associate with AP 00:24:fe:05:45:41
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: Associated with 00:24:fe:05:45:41
Nov 9 20:19:18 dimension-e521 NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Nov 9 20:19:18 dimension-e521 kernel: [ 3331.688507] wlan0: RX AssocResp from 00:24:fe:05:45:41 (capab=0x431 status=0 aid=1)
Nov 9 20:19:18 dimension-e521 kernel: [ 3331.688514] wlan0: associated
Nov 9 20:19:18 dimension-e521 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: WPA: Key negotiation completed with 00:24:fe:05:45:41 [PTK=CCMP GTK=TKIP]
Nov 9 20:19:18 dimension-e521 wpa_supplicant[1362]: CTRL-EVENT-CONNECTED - Connection to 00:24:fe:05:45:41 completed (reauth) [id=0 id_str=]
Nov 9 20:19:18 dimension-e521 NetworkManager: <info> (wlan0): supplicant conn...

Hi Luftikus,

I'd encourage you to open a new bug.

You have all information needed in https://help.ubuntu.com/community/ReportingBugs

Thanks

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]