** Summary changed:

- mountall hangs when fsck is run
+ mountall needs to flush plymouth message queue before emitting upstart events

** Description changed:

  Binary package hint: mountall
  
  On boots when fsck runs, mountall appears to hang.  The mountall process 
consumes 100% CPU time, and the following error message loops on the console:
  "mountall: Plymouth command failed"
  
  Although this error message continues to loop on the main console, login
  is still possible on other consoles, or through kdm.
+ 
+ mountall needs to flush the plymouth message queue before each upstart
+ event that it emits; otherwise, plymouth may be killed in response to
+ one of these upstart events (in practice: filesystem -> gdm or rc-
+ sysinit -> plymouth-stop), leaving as the last message on the splash
+ screen whatever mountall managed to get out before plymouthd exited.
+ This is particularly disconcerting when gdm or kdm stops plymouth with
+ --retain-splash.
  
  To reproduce:
  1) Force a filesystem check:
  # touch /forcefsck
  
  2) Reboot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mountall 2.11
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  Architecture: i386
  Date: Sat Apr 10 14:15:12 2010
  EcryptfsInUse: Yes
  ExecutablePath: /sbin/mountall
  ProcEnviron: PATH=(custom, no user)
  SourcePackage: mountall

** Changed in: mountall (Ubuntu)
       Status: New => Triaged

** Changed in: mountall (Ubuntu)
   Importance: Undecided => High

** Changed in: mountall (Ubuntu)
     Assignee: (unassigned) => Scott James Remnant (scott)

** Changed in: mountall (Ubuntu)
    Milestone: None => ubuntu-10.04

** Also affects: mountall (Ubuntu Lucid)
   Importance: High
     Assignee: Scott James Remnant (scott)
       Status: Triaged

-- 
mountall needs to flush plymouth message queue before emitting upstart events
https://bugs.launchpad.net/bugs/559761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to