Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
plasma-widget-network-manager (Ubuntu) |
Invalid
|
Undecided
|
Jonathan Riddell | ||
Jaunty |
Won't Fix
|
High
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Jonathan Riddell | ||
plasma-widget-networkmanagement (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
High
|
Unassigned | ||
wireless-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am using 64-bit Kubuntu Jaunty on my Gateway M-7315u laptop. My laptop does not require closed source drivers to function, and has functioned with every previous Kubuntu release I've tried. I am using the default Network Manager plasmoid that is added to the plasma panel.
My wireless network is not hidden. It's set up as WEP with a shared key. When I enter the information, the connection fails every time.
On another partition, I have Windows Vista set up which is able to connect to the wireless router every time with the same settings.
I have also tried disabling the mac address filtering of my router, but that doesn't fix anything. The mac address of my laptop is added to the allowed list on my router.
summary: |
- Kubuntu Jaunty: Cannot Connect To Wireless Network + Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key |
Changed in wireless-tools (Ubuntu Karmic): | |
status: | New → Invalid |
Changed in plasma-widget-network-manager (Ubuntu Karmic): | |
assignee: | nobody → Jonathan Riddell (jr) |
Changed in wireless-tools (Ubuntu Jaunty): | |
status: | New → Invalid |
description: | updated |
Changed in plasma-widget-networkmanagement (Ubuntu): | |
assignee: | nobody → abdus salaam anthony (middleground4) |
assignee: | abdus salaam anthony (middleground4) → nobody |
With all updates, this is still a problem.