*** This bug is a duplicate of bug 185854 ***
https://bugs.launchpad.net/bugs/185854
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported so it is
being marked as a duplicate. Please look at the other bug report to
This bug seems to have stopped happening for me in the last week or two;
(perhaps related to the update in bug #185854) ?
Is this true for everyone else?
Dave
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug
Probably related to bug #185854
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can't stand how such a big bug is marked as low.
For most people ubuntu, in the current status, won't have such a basic thing
like the static ip address functionallity.
Simple things like this will make a lot of people think that ubuntu
sucks.
--
network interface doesnt come up on boot when
Might be related to bug #178775 ...
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Adding 'auto eth0' to /etc/network/interfaces works for me too. Thanks
to Scott for this fix!
It's worth noting that even when making a change from static - DHCP
with network-admin, the 'auto eth0' line is removed.
I've added gnome-system-tools to the bug as I believe it's actually
network-admin
Looks like I changed to gnome-system-tools rather than adding it. My
apologies if this is a bad thing to do. I'm not quite experienced with
launchpad yet, so if things need changing then please do.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Confirmed
--
network interface
Adding auto works at boot but it isn't re-enabled after suspend/resume
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm I'm also seeing this on Hardy (beta as of March 29th when I
upgraded from Gutsy).
The ether worked fine after the first reboot after upgrade - but on a resume
from hibernate my static IP'd eth0 didn't come back;
and ifconfig showed the interface and I think showed it was UP - but
I can confirm that I am showing the same symptoms as Dave Gilbert
(above) -- the static ip had the exact same problem for me (and I also
worked around this by flipping to dchp and back).
But I have just now found what I believe to be the problem:
'auto eth0' needs to be added to
EDIT: The gui network-admin application is what I actually mean. The
NetworkManager applet is doing its job just fine by ignoring eth0 since
I am 'manually' (gui-ally) configuring it.
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You
I can confirm that the bug still exists. I've two AMD64 Hardy machines and both
of them are connected using the static ip via wireless.
One of the two is working perfectly with Gutsy, installed in another partition.
When booting, the wifi interfaces aren't ifupped and I have to do it manually.
More, I'd suggest to rise the low importance to medium or high
because it's quite a big problem for newbies and don't think that final
Hardy should get out with that.
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug
I found this in daemon.log with System Log Viewer.
...
NetworkManager: info /etc/network/interface changed: rebuilding the device
list.
NetworkManager: info Recreating the device list.
NetworkManager: WARN ifparser_init(): Error: Can't parse inet line 'inet'
NetworkManager: WARN
seems to be fixed after latest update.
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm still experiencing this issue with the same symptoms described
above. Anything you might have done that has fixed it for you, Artur? I
just did a fresh restart of my up to date system, and it's apparent the
network was down again (Pidgin complains on startup).
I also thought it might be worth
Unfortunately, I'm not able to identify any particular changes.
I'm using static ip conf on my laptop at work - and I just had two weeks off;
it was broken before and today
everything seems to just work.
--
network interface doesnt come up on boot when static ip set
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've been having the same problem for a while now; it still exists on a
fresh install of Hardy Beta.
It worked just fine on installation when it was set to roaming mode,
however I require a static IP on my private network. Once changing to
the correct static IP settings via the Network Settings
Hi there
do you still experience this issue with the current version of the
application?, could you please try to reproduce this using the live
environment of the Desktop CD of the development release - Hardy Heron.
Thanks in advance
** Changed in: network-manager (Ubuntu)
Importance:
confirmed - i'm having the same problem with static IP configuration.
--
network interface doesnt come up on boot when static ip set
https://bugs.launchpad.net/bugs/187274
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
21 matches
Mail list logo
