| 2011-09-09 18:54:23 |
Timo Jyrinki |
bug |
|
|
added bug |
| 2011-09-09 18:55:14 |
Timo Jyrinki |
description |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe. |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then (after noticing that actually the boot happens if I just wait long enough) started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe. |
|
| 2011-09-09 18:58:08 |
Timo Jyrinki |
description |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then (after noticing that actually the boot happens if I just wait long enough) started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe. |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then (after noticing that actually the boot happens if I just wait long enough) started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe.
Filing upstart bug mostly because for whatever real need the failsafe boot delay is there (I read a few mailing messages), this shouldn't be a possible behavior. Of course, the real root reason might be somewhere else that causes this to happen. |
|
| 2011-09-09 19:00:16 |
Timo Jyrinki |
description |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then (after noticing that actually the boot happens if I just wait long enough) started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe.
Filing upstart bug mostly because for whatever real need the failsafe boot delay is there (I read a few mailing messages), this shouldn't be a possible behavior. Of course, the real root reason might be somewhere else that causes this to happen. |
Starting today, on each boot there is a non-interruptible long delay, apparently 2 minutes exactly. This started after shutting down computer normally, after having updated oneiric to the latest packages after yesterday.
I do not have a clue what's causing the actual problem, but changing the sleep 120 in /etc/init/failsafe.conf to sleep 1 makes everything work again without problems, and returning it to 120 brings the delay back to the boot.
From user point of view the problem is very worrying and confusing, since a) it happens also in the safe mode and b) it gives impression that either the computer or Ubuntu is simply broken, since also I didn't first wait for two full minutes of nothingness, especially since the problem also occurred in safe mode. I then (after noticing that actually the boot happens if I just wait long enough) started making a note about boot messages, and noted that the delay was slightly before AppArmor profiles loading and finally guessed to change the sleep value in /etc/init/failsafe.
Filing upstart bug mostly because for whatever real need the failsafe boot delay is there (I read a few mailing messages), this shouldn't be a possible behavior. Of course, the real root reason might be somewhere else that causes this to happen. I think I might have been noticed "doing nothing" already before the current value of 120 seconds that was changed a few days ago in upstart, but I'm not sure. This is a new laptop I just got and installed a fresh 64-bit beta 1 Oneiric. |
|
| 2011-09-10 09:26:35 |
Launchpad Janitor |
upstart (Ubuntu): status |
New |
Confirmed |
|
| 2011-09-12 01:42:34 |
choel |
bug |
|
|
added subscriber choel |
| 2011-09-12 12:13:26 |
glepore70 |
bug |
|
|
added subscriber glepore70 |
| 2011-09-13 23:15:44 |
Clint Byrum |
marked as duplicate |
|
847782 |
|
| 2011-10-14 17:50:30 |
ilf |
bug |
|
|
added subscriber ilf |
| 2012-01-02 02:28:09 |
David Ziegler |
bug |
|
|
added subscriber David Ziegler |
