switching from runlevel 5 to runlevel 1 locks up system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: plymouth
(the system was freshly installed as 10.4-beta1 and upgraded today)
steps to reproduce:
- boot the system normally
- either: log in graphically and open a console window
- or: switch to vt1 and log into the console
- issue the command: telinit 1
Processes will be stopped and so on, but the procedure ends in a state where
- the ubuntu splash screen is shown
- no reaction to pressing ctrl-alt-f1
- system has to be restarted with ctrl-alt-del
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 19:54:56 2010
DefaultPlymouth: /lib/plymouth/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Gigabyte Technology Co., Ltd. EP35-DS3
ProcCmdLine: root=/dev/sda2 ro quiet splash
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: EP35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: EP35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
tags: | added: runlevel1 |
Yes, I can confirm this looking at the upstart jobs.
plymouth starts on runlevel [016], and calls plymouth show-splash.
plymouth-stop.conf is responsible for stopping plymouth again, but the start condition "stopped rc RUNLEVEL=[2345]" doesn't match.
I think runlevel 1 just needs to be added to the plymouth-stop.conf start condition.