Bug#612594: [Pkg-sysvinit-devel] Bug#612594: Bug#612594: On boot thw wait have no job to wait for, and fail into reboot.
On Wed, 09 Feb 2011, Henrique de Moraes Holschuh wrote: > Erez, could we impose on you to remove the usplash package (not purge, just > remove) and check if the problem disappears (please revert your workaround > first)? Erez replied over private email that yes, just removing usplash is enough to avoid the problem. So, I'd say we should conflict with usplash and upload something to squeeze-proposed-updates. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#612594: [Pkg-sysvinit-devel] Bug#612594: On boot thw wait have no job to wait for, and fail into reboot.
On Wed, 09 Feb 2011, Erez Geva wrote: > Do not have any output since it occurs during boot proccess. > The /lib/init/usplash-fsck-functions.sh rechechs line 169: > However the wait have no job to wait for though fail into fake maintainance > login. > When finnish the maintainance, and exit a reboot is preformed. > But after rebood I get the same fake maintainance login. "fake"? > The follow patch is bypass to the problem. The correct fix is to purge usplash and all other such broken hacks from hell from the system. I don't know what to do about this bug, I have this hunch we need to add something to the initscripts or sysv-rc package in the next stable release to make sure usplash is _gone_, but since you actually have to purge usplash to make sure it can do no damage (so as to get rid of the conffiles), it might not be enough. This might require testing. Erez, could we impose on you to remove the usplash package (not purge, just remove) and check if the problem disappears (please revert your workaround first)? It is also probably a good idea for you to use aptitude to locate all "local packages", i.e. those which are not in the Squeeze package lists, and try to get rid of any cruft there that is not of vital importance to you. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#612594: On boot thw wait have no job to wait for, and fail into reboot.
Package: initscripts Version: 2.88dsf-13.1 Severity: critical -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii coreutils 8.5-1GNU core utilities ii debianutils 3.4 Miscellaneous utilities specific t ii file-rc 0.8.12 Alternative boot mechanism using a ii libc6 2.7-18lenny7 GNU C Library: Shared libraries ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii mount 2.17.2-9 Tools for mounting and manipulatin ii sysvinit-utils 2.88dsf-13.1 System-V-like utilities Versions of packages initscripts recommends: ii e2fsprogs 1.41.3-1 ext2/ext3/ext4 file system utiliti ii psmisc22.11-1utilities that use the proc file s initscripts suggests no packages. -- bug description Do not have any output since it occurs during boot proccess. The /lib/init/usplash-fsck-functions.sh rechechs line 169: However the wait have no job to wait for though fail into fake maintainance login. When finnish the maintainance, and exit a reboot is preformed. But after rebood I get the same fake maintainance login. The follow patch is bypass to the problem. It allow to run system normally. However it does not fix the problem. Why is the fsck does not run, and why is the wait does not have job 1 (%1). And why is there no check for the job being running before trying to wait for it! --- usplash-fsck-functions.sh 2011-02-09 13:21:25.0 +0200 +++ usplash-fsck-functions.sh 2011-02-09 13:21:25.0 +0200 @@ -166,7 +166,7 @@ usplash_write "VERBOSE default" usplash_write "TEXT Drive checks finished." usplash_write "TIMEOUT 15" - wait %1 # to collect fsck's exit code + wait # %1 # to collect fsck's exit code EXITCODE=$? [ -n "$CANCEL" ] && FSCKCODE=0 || FSCKCODE=$EXITCODE if [ "$FSCKCODE" -gt 1 ]; then ** IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies thereof. *** eSafe scanned this email for viruses, vandals, and malicious content. *** ** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
