| 2006-03-29 05:46:52 |
Andrew Jorgensen |
bug |
|
|
added bug |
| 2006-03-29 07:45:59 |
Reinhard Tartler |
wpasupplicant: status |
Unconfirmed |
Needs Info |
|
| 2006-03-29 07:45:59 |
Reinhard Tartler |
wpasupplicant: statusexplanation |
|
|
|
| 2006-04-01 12:55:53 |
sam tygier |
wpasupplicant: status |
Needs Info |
Confirmed |
|
| 2006-04-01 12:55:53 |
sam tygier |
wpasupplicant: statusexplanation |
|
after Andrew Jorgensen it seems that info is not needed. |
|
| 2006-04-01 13:10:46 |
Reinhard Tartler |
wpasupplicant: statusexplanation |
after Andrew Jorgensen it seems that info is not needed. |
reassigning to the correct package. If the driver doesn't support WPA properly, there is nothing that we can do about that in wpasupplicant |
|
| 2006-04-10 21:34:49 |
Ben Collins |
linux-source-2.6.15: statusexplanation |
reassigning to the correct package. If the driver doesn't support WPA properly, there is nothing that we can do about that in wpasupplicant |
The issue to me seems to be that wpasupplicant left rt2500 behind. If it worked in breezy, then it should continue to work in dapper. Considering that the regression occured because of wpasupplicant upgrade losing support for rt2500, then I think the blame lies there. |
|
| 2006-04-10 22:02:09 |
Ben Collins |
wpasupplicant: statusexplanation |
The issue to me seems to be that wpasupplicant left rt2500 behind. If it worked in breezy, then it should continue to work in dapper. Considering that the regression occured because of wpasupplicant upgrade losing support for rt2500, then I think the blame lies there. |
Sorry about that. |
|
| 2006-04-28 12:36:35 |
Scott James Remnant (Canonical) |
network-manager: statusexplanation |
Sorry about that. |
Sounds like a clear wpasupplicant problem! |
|
| 2006-04-28 13:13:34 |
Reinhard Tartler |
wpasupplicant: statusexplanation |
Sounds like a clear wpasupplicant problem! |
Reassigning back to linux-source-2.6.15. In order for rt2500 to work with wpasupplicant, it needs to implement WE19. Currently, it seems to implement its own supplicant in kernel space: see https://wiki.ubuntu.com/Rt2500WirelessCardsHowTo/ |
|
| 2006-05-10 20:23:58 |
Scott James Remnant (Canonical) |
network-manager: status |
Unconfirmed |
Rejected |
|
| 2006-05-10 20:23:58 |
Scott James Remnant (Canonical) |
network-manager: statusexplanation |
|
|
|
| 2006-05-10 20:24:14 |
Scott James Remnant (Canonical) |
title |
wpasupplicant doesn't work properly with rt2500 driver |
rt2500 driver does not implement wireless extensions correctly |
|
| 2007-04-14 14:09:28 |
sam tygier |
bug |
|
|
assigned to linux-source-2.6.20 (Ubuntu) |
| 2007-04-15 19:16:07 |
Cyclops |
linux-source-2.6.20: status |
Unconfirmed |
Confirmed |
|
| 2007-04-15 19:16:07 |
Cyclops |
linux-source-2.6.20: statusexplanation |
|
fortunately network-manager can be removed, but it's sad to do so. After removing NM, though, I'm suffering from this other annoying bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/78037 |
|
| 2007-12-17 21:40:13 |
Brian Murray |
linux-source-2.6.15: assignee |
|
ubuntu-kernel-team |
|
| 2007-12-17 21:40:25 |
Brian Murray |
linux-source-2.6.20: assignee |
|
ubuntu-kernel-team |
|
| 2008-01-24 20:14:46 |
oponek |
marked as duplicate |
|
134660 |
|
| 2012-05-29 14:41:04 |
Curtis Hovey |
removed subscriber Registry Administrators |
|
|
|
