*** This bug is a duplicate of bug 42860 ***
https://bugs.launchpad.net/bugs/42860
** Changed in: gnome-desktop
Status: New => Invalid
--
Unable to specify which wep key# to store key in
https://bugs.launchpad.net/bugs/49600
You received this bug notification because you are a member
*** This bug is a duplicate of bug 42860 ***
https://bugs.launchpad.net/bugs/42860
This bug is a duplicate of bug #42860. Also the upstream bug I reported
also happened to be a duplicate (visit
http://bugzilla.gnome.org/show_bug.cgi?id=382491 for more info).
** This bug has been marked a dupl
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Ubuntu Desktop Bugs
--
Unable to specify which wep key# to store key in
https://launchpad.net/bugs/49600
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
** Changed in: gnome-desktop (upstream)
Status: Unknown => Unconfirmed
--
Unable to specify which wep key# to store key in
https://launchpad.net/bugs/49600
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Reported to http://bugzilla.gnome.org/show_bug.cgi?id=382491 as request
for enhancement.
** Changed in: Ubuntu
Sourcepackagename: None => gnome-system-tools
Status: Unconfirmed => Confirmed
** Bug watch added: GNOME Bug Tracker #382491
http://bugzilla.gnome.org/show_bug.cgi?id=382491
*
This is really an issue with the upstream gnome-tools. network-admin
only allows for a a minimalistic set of wireless configuration (wep/not
wep and a single key). network-manager, at the very least, shoudl allow
for input of the "proper" key for use, but if multiple keys need to be
configured (and
