The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: console-tools (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: console-common (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: console-tools (Ubuntu Oneiric)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: console-common (Ubuntu Oneiric)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I had this issue with installing linux 12.04, kubuntu.
Sometimes it hanged and wanted to search network.
Sometimes it skipped the part.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
** Changed in: upstart
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
configuration message at
The problem also occurs for my with a freshly-installed Ubuntu Server
12.04 (64 bit). The problem seems to be the existence of sub-interfaces.
If there is eth0:1 (iface eth0:1 inet static) in
/etc/network/interfaces, an additional waiting time of ~2min is added to
the boot sequence. This is quite
/var/log/boot.log in the problem case.
** Attachment added: /var/log/boot.log
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/881079/+attachment/3278705/+files/bad-boot.log
** Also affects: upstart
Importance: Undecided
Status: New
--
You received this bug notification
With this configuration, the problem does not occur. However, of course,
the sub-interface is missing. This is not a useful solution, therefore.
** Attachment added: /etc/network/interfaces
https://bugs.launchpad.net/upstart/+bug/881079/+attachment/3278714/+files/good-interfaces
--
You
On Mon, Aug 27, 2012 at 08:53:11AM -, Thomas Dreibholz wrote:
The problem also occurs for my with a freshly-installed Ubuntu Server
12.04 (64 bit). The problem seems to be the existence of sub-interfaces.
If there is eth0:1 (iface eth0:1 inet static) in
/etc/network/interfaces, an
In regards to your last comment Steve resorting to having to use network
manager to resolve the problem is not a viable or root cause fix. The
other issue in using network manager is that it is not applicable when
vlans are being used.
Since upgrading from 11.04 to 11.10 and onwards I too have
On Sat, Jun 02, 2012 at 09:58:18AM -, Roberto Gordo Saez wrote:
Please note there is a problem with removable network devices (usually
usb). The file /etc/init/network-interface.conf causes network devices
to be brought up or down as a result of hardware being added or
removed, as its own
Please note there is a problem with removable network devices (usually
usb). The file /etc/init/network-interface.conf causes network devices
to be brought up or down as a result of hardware being added or
removed, as its own comment says, but they must be configured as auto
in
I have a similar bug. lubuntu 12.04. If I add in the config bridge br0
/etc/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 10.0.1.8
netmask 255.255.0.0
gateway
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
configuration message at startup, but all
Clint:
Done. I've opened a new bug report: Bug #950662
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
configuration message
I'm having this problem with a fresh (post-beta1) Precise install on an
EeePC 900. Commenting out lines in /etc/network/interfaces does nothing,
even if BOTH wlan0 and eth0 are able to connect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Excerpts from Jane Atkinson's message of Thu Mar 08 23:39:32 UTC 2012:
I'm having this problem with a fresh (post-beta1) Precise install on an
EeePC 900. Commenting out lines in /etc/network/interfaces does nothing,
even if BOTH wlan0 and eth0 are able to connect.
Hi Jane. It would be
I solved by deleting the configuration lines in /etc/network /interfaces
that are related to the wireless interface.
Because my interface starts after starting the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: upstart (Ubuntu Precise)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
** Changed in: upstart (Ubuntu Precise)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
Ming, please provide a comment if you intentionally meant to change the
bug's status back to confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60
I am still touched by the problem[1] after upgrading from oneiric to precise,
but I have
no any changes on /etc/udev.
Also the workaround in #56 does work for me.
[1], https://bugs.launchpad.net/bugs/835833
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello Clint, going to have to say user error on this one apologies for
the false alarm - someone had a line in a script that was changing stuff
in /etc/udev which bonked things. Did a fresh Precise reinstall from
the mini.iso and no issues, also a Lucid - Precise upgrade to confirm
and indeed...
Try this workaround:
sudo sed -i s|sleep|#sleep|g /etc/init/failsafe.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881079
Title:
FIXED: spurious Waiting up to 60 more seconds for network
I'm getting exactly these symptoms after a test upgrade from vanilla Lucid -
Precise.
Upon reboot, the iface is indeed reachable and I can ssh into it within about
10 seconds but
on the monitor it says Waiting up to 60 more seconds for network
configuration... error,
and hangs there for a
Hi Mark, this sounds like a new bug, not the one that caused the
original reporter problems. Indeed, you should not see any slow down as
soon as eth0 is up.
Can you post the output of
ls -l /etc/network/if-up.d
And
ls -l /run/network
Thanks!
--
You received this bug notification because you
You're wrong about bug #876829 - that bug is about alias that isn't up
but if you look into log you'll see it's not the case - all interfaces
are up! And I still get the messages despite of EVERY interface is up!
Bug isn't fixed in 1.3-0ubuntu11 yet!
--
You received this bug notification because
Or should I open a new bug with the same subject instead as you've marked this
one as fixed? Bug which affects me is exactly:
spurious Waiting up to 60 more seconds for network configuration message at
startup, but all network devices are up at that moment.
--
You received this bug
On Wed, Nov 09, 2011 at 03:12:41PM -, LStranger wrote:
You're wrong about bug #876829 - that bug is about alias that isn't up
but if you look into log you'll see it's not the case - all interfaces
are up! And I still get the messages despite of EVERY interface is up!
If something is
Ah, I see... that's strange enough as alias really is up (just as log
says, routing table says that also, and my host is available by alias IP
from local network) but ifconfig doesn't show it so probably that's the
case. Thank you for pointing on that.
--
You received this bug notification
On Sun, Nov 06, 2011 at 10:02:15PM -, LStranger wrote:
I've got the same bug. My upstart package is 1.3-0ubuntu11. The file
/etc/network/interfaces contains:
auto lo eth1 eth1:0
iface lo inet loopback
iface eth1 inet static
address 10.11.12.1
netmask 255.255.0.0
32 matches
Mail list logo
