[Expired for gnome-system-tools (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Thanks for the report Paul Smith , It has been a long time without any
comment or a duplicate in this bug report and It is possible that the
bug has been fixed. May you please try to reproduce it with the latest
Stable Release of Ubuntu the Natty Narwhal and add the respective
comments to the repor
> My /etc/hosts file did not have an entry for my hostname "myhost";
there was ONLY an entry for "myhost.mydomain.com".
If gnome-system-tools does this then it has a bug. (I don't dare install or
run the
GNOME network configurator on my machine. In the past it would utterly botch
Debian/Ubuntu
Paul Smith wrote:
> and edit my /etc/hosts file to add "myhost" to the 127.0.0.1 IP address
Actually you should edit /etc/hosts to add "myhost" to the line 127.0.1.1,
yielding:
127.0.0.1 localhost
127.0.1.1 myhost
--
[Hardy] network-admin settings to DHCP do not work
https://bugs.laun
Hi same problem on hardy 8.04.1 , dhcp not work with network-admin !
I have this in interfaces file after manual configuration with network-
admin
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-psk
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid
But with same c
On Wed, Aug 20, 2008 at 12:32 PM, Mackenzie Morgan <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 12:11 PM, patriciaosullivan
> <[EMAIL PROTECTED]> wrote:
>> Trying to configure a WPA network key results in a corrupted key being
>> stored, which prevents access to any network. This is persis
On Wed, Aug 20, 2008 at 12:11 PM, patriciaosullivan
<[EMAIL PROTECTED]> wrote:
> Trying to configure a WPA network key results in a corrupted key being
> stored, which prevents access to any network. This is persistant and
> replicable on ANY machine I've tried with ANY wireless chipset.
I haven'
This is a serious problem, and may prevent lots of users trying to
persist with Ubuntu. Network Manager is seriously faulty:
Trying to configure a WPA network key results in a corrupted key being
stored, which prevents access to any network. This is persistant and
replicable on ANY machine I've
I can confirm that Network Admin + DHCP = fail on Hardy. Since WEP
doesn't work with Network Manager, I've attempted to use Network Admin
when connecting to WEP-encrypted networks, since it'll at least take the
WEP key. Unfortunately, no DHCP stuff happens with Network Admin set to
DHCP. It's no
I'll need to find a way to do a fresh install to test this. Maybe a
vmware image. Let me see what I can do.
--
[Hardy] network-admin settings to DHCP do not work
https://bugs.launchpad.net/bugs/214360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: ubuntu
Status: New => Incomplete
--
[Hardy] network-admin settings to DHCP do not work
https://bugs.launchpad.net/bugs/214360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
thanks for reporting, is this reproducible with non-beta releases?
--
[Hardy] network-admin settings to DHCP do not work
https://bugs.launchpad.net/bugs/214360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
12 matches
Mail list logo
