Public bug reported:
If I select the wrong access point (e.g. my home config at work),
gethostbyname will fail.
This means gksudo will fail, so I can't run network-admin to fix it, nor
can I run sudo in a console -
[EMAIL PROTECTED]:~$ sudo killall dhclient3
sudo: unable to lookup myhost via gethostbyname()
I have to have a real root account now, which is a security hole, or
basically reboot the machine to have it recover since I can't run sudo
nor anything like network-admin which requires it.
Normally it will write an entry adding "myhost" to 127.0.0.1 in
/etc/hosts, but only if it hasn't been configured yet - or maybe only
after several minutes of dhcp failing (there is no connection - 0%
signal, etc, but it still runs dhclient3).
network-manager which is supposed to manage roaming doesn't seem to work
at all (may be my wireless card), nor does there seem to be a way to
specify "any" for the access point.
The network manager will also tend to want to select whatever the bottom
entry on the list is when it pops up - I trigger this about one out of
every five times (might be my touchpad). It really needs to confirm
changing the configuration. Also bad is you must select (and have it
spend several minutes failing) to select an old configuration to delete
it - you cannot delete an unselected configuration as far as I can tell,
and many simply won't work (e.g. I change the essid).
** Affects: Ubuntu
Importance: Untriaged
Status: Unconfirmed
--
wireless oops (too easy to do) requires reboot to recover
https://launchpad.net/bugs/59594
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
