Excerpts from ilf's message of Sun Oct 23 13:05:31 UTC 2011:
> The workaround only fixes the waiting time.
> It disables auto-up of the interface, which I want, if it us plugged in. This
> is a regression and still a major annoyance for me.
> Closing this bug report is not right, this isn't the fa
The workaround only fixes the waiting time.
It disables auto-up of the interface, which I want, if it us plugged in. This
is a regression and still a major annoyance for me.
Closing this bug report is not right, this isn't the fault of ifupdown, but
upstart.
--
You received this bug notificatio
Excerpts from ilf's message of Fri Oct 14 21:50:25 UTC 2011:
> Thanks for your workaround, using that now.
>
> I still think it's wrong to assume that one of these three has to exist on a
> system:
> - auto eth0 and eth0 always plugged in
> - network-manager installed
> - boot time delayed by two
Thanks for your workaround, using that now.
I still think it's wrong to assume that one of these three has to exist on a
system:
- auto eth0 and eth0 always plugged in
- network-manager installed
- boot time delayed by two minutes.
And no, I won't install network-manager even if it doesn't depen
Excerpts from ilf's message of Fri Oct 14 18:11:56 UTC 2011:
> I don't like this behavior.
>
Hi ilf, sorry that you're experiencing problems with this change.
This behavior is meant to provide a balance between mobile systems and
servers/dedicated workstations.
The former needs flexible network
I don't like this behavior.
I have eth0 auto in /etc/network/interfaces, so that it gets auto-enabled when
plugged in.
This being a laptop it gets moved around and doesn't always have an ethernet
connection plugged in.
No I'm supposed to wait two minutes on every boot OR not have the interface
** Changed in: ubuntu-release-notes
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/839595
Title:
failsafe.conf's 30 second time out is too low
To manage notifications a
Manual symlink of /var/run->/run and /var/lock-/run/lock fixed my
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 second time out is too low
To manage notific
Sorry for the typo in my last statement, the new bug report is bug
#847782
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
Jeremy: "Could either a new bug for this issue be opened or [...]"
Done!
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
f
Could either a new bug for this issue be opened or this bug's status be
changed away from "Fix Released"? All but 3 of the comments have been
posted after this was "fixed".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I've a fresh Oneiric Beta 1 installation and because of this sleep
command I thought either my Ubuntu or laptop itself is broken. See my
report bug #845914. I installed Ubuntu from the alternate CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can confirm I had 'auto eth0' in /etc/network/interfaces on my
notebook, and I don't think I've put them there myself.
Furthermore, I just installed 11.04 in a VM, and /etc/network/interfaces
has a "auto eth0" line.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
ubiquity has source specifically for managing /etc/networking/interface
(d-i/source/netcfg/write_interface.c) so it seems whatever I am doing
during the install is the wrong way to do it. Sorry for the red herring
in network-manager, it was just a likely guess since that was the only
thing I touche
Three is a crowd! I have 4 machines running kubuntu. Two started out
with regular CD/USB live image installed to disk. The other two were
installed from the netinstall mini-iso, connected to ethernet. These two
are the only ones where I see an auto ethN.
I also played in one of my machines extensi
Just as a side note on how I installed this machine initially ... to get
partition alignment setup properly (using ssd here), I pre-partitioned
the disk, then used the natty-alternate install with the onboard
ethernet connected ... Perhaps that is how I've ended up with eth0 in
/etc/networking/inte
I still haven't figured out what's creating it, but even a new machine
installed from beta 1 with an ethernet cable plugged in, pulling the
ethernet cable and and dist-upgraded over wifi the next boot is hitting
the problem because auto eth0 is in there. Ubiquity when you check
update/install third
Excerpts from Leo Milano's message of Fri Sep 09 20:22:53 UTC 2011:
> Clint. The biggest issues it that we are not sure, but it is plausible
> that a large proportion of the existing systems will suffer a 2 minute
> delay after the upgrade. How about we test this:
>
> * remove the offending ethN l
Clint. The biggest issues it that we are not sure, but it is plausible
that a large proportion of the existing systems will suffer a 2 minute
delay after the upgrade. How about we test this:
* remove the offending ethN line from /etc/networking/interfaces
* reboot
* connect the laptop/desktop to
Excerpts from Leo Milano's message of Fri Sep 09 18:55:11 UTC 2011:
> Robert, Chris, I think you are both hitting also the other problem I
> encountered, namely the fact that X is not starting until failsafe is up
> (even though theoretically this should not be the case).
>
> Could you please look
Robert, Chris, I think you are both hitting also the other problem I
encountered, namely the fact that X is not starting until failsafe is up
(even though theoretically this should not be the case).
Could you please look at comment #21 by Clint and post the info he is
asking for as well? I will, l
I can confirm Robert's workaround in Comment #22 does fix-up this delay
when booting. I /just/ upgraded from natty to Oneiric today and
instantly ran into this issue on a Lenovo x220, which has in the past
(not often) made use of the onboard ethernet.
--chris
--
You received this bug notificati
So this seems to be hitting every one of my machines after the last
round of updates, and removing eth0 from /etc/networking/interfaces does
indeed fix the 2 minute pause before the desktop comes up. That entry
exists for every machine that's had a network cable plugged in in the
past (with availab
Excerpts from Leo Milano's message of Fri Sep 09 16:16:57 UTC 2011:
> Will do. I assume you mean to run a grep on syslog right after I login
> (or pls let me know otherwise).
>
Right, to clarify
at grub scren, edit cmdline and remove 'quiet', add '--verbose'
After booting up, attach two things
Will do. I assume you mean to run a grep on syslog right after I login
(or pls let me know otherwise).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 second time out
Excerpts from Leo Milano's message of Fri Sep 09 12:41:00 UTC 2011:
> Clint, I'll give it a swirl. Where exactly do you add --verbose? Do you
> mean to remove the "quiet" linux boot parameter? Or add splash=verbose
> ?
In grub, yes remove 'quiet' and replace it with '--verbose'
It may also be i
Clint, I'll give it a swirl. Where exactly do you add --verbose? Do you
mean to remove the "quiet" linux boot parameter? Or add splash=verbose
?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Excerpts from Leo Milano's message of Fri Sep 09 04:22:22 UTC 2011:
> Hi,
>
> Just an update: Lightdm also gets penalized and waits the sleep time
> declared in failsafe.conf before loading
>
Very interesting. I'd be curious to see your /var/log/boot.log with
--verbose added to the boot commandl
Hi,
Just an update: Lightdm also gets penalized and waits the sleep time
declared in failsafe.conf before loading
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 seco
I will try to dig in a bit. My X clearly doesn't start until the penalty
120 secs expire, so I'd like to understand why, since for what you are
saying this shouldn't be the case (and there is, indeed, a kdm.conf in
/etc/init).
In the meantime: I use KDE, with KDM set to autologin to a user account
Excerpts from Leo Milano's message of Thu Sep 08 19:17:14 UTC 2011:
> @ Scott: thanks for the detailed response. It all makes sense now. I am
> guessing perhaps wicd wrote that entry in my interfaces file. I haven't
> edited this file by hand.
>
> @ Clint: yes, I think it makes sense to add this
@ Scott: thanks for the detailed response. It all makes sense now. I am
guessing perhaps wicd wrote that entry in my interfaces file. I haven't
edited this file by hand.
@ Clint: yes, I think it makes sense to add this to the release notes.
Thanks for updating the description. It seems like this
I think this change may deserve a release note for 11.10, so that people
who have kept an interface in /etc/network/interfaces for some reason
aren't surprised by the long boot.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Description changed:
+ RELEA
On Thu, 8 Sep 2011, Leo Milano wrote:
> Scott, is this how things are intended to work? My current understanding
> is:
>
>
> * "pre-start exec sleep N" means "wait up to N seconds for the
> preconditions to be satisfied". In this case, these are a network up and
> a fs up. I thought it meant "Wait
Scott, is this how things are intended to work? My current understanding
is:
* "pre-start exec sleep N" means "wait up to N seconds for the preconditions to
be satisfied". In this case, these are a network up and a fs up. I thought it
meant "Wait at least N seconds", but I guess I was wrong.
*
Yes, that's correct. Is that something that should not be there? Thanks!
santisofi@minime:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto
On Thu, 8 Sep 2011, Leo Milano wrote:
> I am not an expert, so sorry if this silly, but isn't upstart all about
> dependency based start up? It seems as if using sleep statements defeats
> the whole purpose of the system?
Could you please post your /etc/network/interfaces file ?
I suspect that y
One more thought, just by looking at the script and the behaviour on my
system. The bug description states "as far as I can understand, the 30
second sleep in failsafe.conf means that /etc/init/rc-sysinit.conf will
start within AT MOST 30 seconds of 'filesystem' and 'ifup lo' having
occurred."
It
** Attachment added: "dmesg for a boot with sleep = 1"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+attachment/2370271/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Oh yes, changing that value in failsafe.conf brings back the old boot times:
tried setting to 12 and then 1, and it definitely fixed things: ( I added the
//comments )
Wed Sep 7 17:13:34 PDT 2011. Boot Time [s]: 156 // Sleep 120
Wed Sep 7 18:59:59 PDT 2011. Boot Time [s]: 51 // Sleep 12
We
Hi
After installing this version of upstart is making, my netbook takes
extra 100 seconds to boot. CTRL-ALT-F1 shows me that that the network
security us being brought up. Any thoughts? Could this be a coincidence?
Boot time (as measured with a script) has regressed incredibly over the
last few da
This bug was fixed in the package upstart - 1.3-0ubuntu7
---
upstart (1.3-0ubuntu7) oneiric; urgency=low
* debian/conf/failsafe.conf: raise timeout to 120 seconds to
allow for very slow DHCP interfaces to come up on servers.
(LP: #839595)
-- Clint ByrumSun, 04 Sep 2011
Agreed Scott, I think we should wait a little longer. 2 minutes seems a
reasonable amount of time, especially given that this should never
affect the average laptop/desktop machine.
** Changed in: upstart (Ubuntu)
Status: New => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undeci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 second time out is too low
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upst
44 matches
Mail list logo
