Actually, never mind the previous comment - it was obvious once I
thought about it the right way. The mounted event is SYNCHRONOUS:
anything that says 'start on mounted ...' will block mountall until it
comes back, and this is by design (see mounted(7)). Thus the effect of
alsa-restore's 'start on runlevel [2345] and (mounted MOUNTPOINT=/usr)
and (mounted MOUNTPOINT=/var)' is to deadlock mountall.
Furthermore, the current job specification means that 'alsactl restore'
will never be run unless /usr and /var are both separate mountpoints.
The right way to specify this is not '(mounted MOUNTPOINT=/usr) and
(mounted MOUNTPOINT=/var)', but simply 'filesystem'. I'll fix this
shortly.
** Package changed: mountall (Ubuntu) => alsa-utils (Ubuntu)
** Changed in: alsa-utils (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates from 2011-02-22
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
