plymouthd alive when umountroot runs (prevents clean unmount)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
kde-workspace (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
On my system,
* /etc/X11/
* gdm is also installed
* the default runlevel is 2
* I boot in text mode (and optionally run startx later); i.e. no display manager is started from /etc/rc*.d
Since fsck runs on every reboot, I spawned a shell from /etc/init.
/sbin/plymouthd --mode=boot --attach-to-session --pid-file=
I guess this is what happens:
* /etc/init/gdm,conf starts and triggers /etc/init/
* plymouth-stop starts (and remains started), but seeing that gdm is running, it does nothing
* gdm exits when it discovers that I use a different default manager
* I log in from the text console
* "status plymouth-stop" reports this pseudo-service is running; the plymouthd daemon is also alive
* when I shut down, nothing stops plymouthd
* /etc/init.
Since the event dependencies between plymouth, gdm, kdb, rc*.d are so complex, I don't know what to suggest.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-25-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Oct 22 19:18:59 2010
DefaultPlymouth: /lib/plymouth/
MachineType: Dell Inc. Inspiron 1520
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
dmi.bios.date: 02/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0UW306
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.
Changed in plymouth (Ubuntu): | |
status: | Invalid → Incomplete |
affects: | kdebase-workspace (Ubuntu) → kde-workspace (Ubuntu) |
Sorry, but I think you've misunderstood the purpose of /etc/init. d/umountroot. This script is not supposed to *unmount* the root filesystem, it's supposed to remount it read-only. A plymouthd process running does not prevent this - and plymouthd is supposed to stay running up until the very end. Have you checked in your modified umountroot script what processes are holding the root filesystem open for *write* at this point? Those will be the processes preventing / from being remounted ro.