Ubuntu
sysvinit package

reboot hangs at Plymouth logo after upgrading base-files and initscripts

Asked by dj_palindrome

Please excuse me if I am reporting against the wrong package, or even if this report is invalid altogether, but I was told in no uncertain terms that "today's" update of initramfs-tools resolved this issue. It does not. I survived the botched, uncoordinated migration to /run, and tried to avoid upgrading all packages at once. I had the current versions of udev and initramfs under my belt before attempting the following:

initscripts: 2.88dsf-13.10ubuntu4
base-files: 6.4ubuntu2

A warm reboot of the (virtual) machine seems OK, but a cold restart hangs at the Plymouth logo. Eventually, Plymouth stops spinning and the login screen never appears. Recovery mode of the same kernel version (3.0.0-5-virtual) still works.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: base-files 6.4ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-5.6-virtual 3.0.0-rc7
Uname: Linux 3.0.0-5-virtual x86_64
Architecture: amd64
Date: Fri Jul 15 20:57:58 2011
Dependencies:

InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: base-files
UpgradeStatus: Upgraded to oneiric on 2011-04-30 (76 days ago)

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu sysvinit Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #811385.

Revision history for this message
dj_palindrome (dj.palindrome) said : 		#1

My report appears to be invalid. My Plymouth hadn't been updated to take the /run transition into account, even if initramfs had been. At least that's the conclusion I draw. After reverting to a stable baseline, updating Plymouth, then updating base-files and initscripts, everything worked, even after a cold boot.

My apologies. Even if the updates really did make their appearance at the same time, it became increasingly difficult to keep track of which package triggered any given consequence.

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.