init: ureadahead-other main process terminated with status 4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ureadahead |
New
|
Undecided
|
Unassigned | ||
ureadahead (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
For information on ureadahead and its exit status of 4: http://
--- original report ---
Binary package hint: ureadahead
During boot, I first see the white splash image. After that, I see a blinking cursor in the upper right corner, and the following messages appear:
fsck from util-linux-ng 2.16
* moblock is not running
/dev/sda1: clean, 379409/3842048 files, 2300412/15360140 blocks
fsck from utul-linux-ng 2.16
init: ureadahead-other main process (1542) terminated with status 4
/dev/sda5: clean, 75046/10911744 files, 11084035/43626507 blocks
init: ureadahead-other main process (1552) terminated with status 4
init: ureadahead-other main process (1557) terminated with status 4
* Setting preliminary keymap...
* Preparing restricted drivers...
* Starting AppArmor profiles
I guess this is not the way it should be: I expect no console output, and ureadahead should not output an error message. After this, my computer boots normally into Ubuntu.
ProblemType: Bug
Architecture: i386
Date: Wed Nov 18 10:49:27 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: ureadahead 0.90.3-2
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ureadahead
Uname: Linux 2.6.31-15-generic i686
tags: | added: amd64 boot |
Changed in ureadahead (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in ureadahead (Ubuntu): | |
status: | Invalid → Confirmed |
tags: | added: iso-testing |
Changed in ureadahead (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in ureadahead (Ubuntu): | |
status: | Invalid → Confirmed |
description: | updated |
Also same here.