alsaconf cannot be the culprit, because it does not do anything on
system shutdown. It is a utility to probe free resources in an effort
to load the appropriate ALSA driver. Furthermore, alsaconf has not been
shipped in Ubuntu's alsa-utils package since dapper (6.06).
NOTE: THE SUGGESTION BELOW IS ONLY FOR TESTING PURPOSES!!
Guys/gals, please try commenting out lines 50-52 of /etc/init.d/alsa-
utils:
while [ ! -d /usr/bin -o ! -d /var/lib/alsa ]; do
sleep 0.2
done
NOTE: THE SUGGESTION ABOVE IS ONLY FOR TESTING PURPOSES!!
The potential regression with the above three lines commented out is
that ALSA mixer state is not stored or restored correctly. (On the
other hand, PulseAudio, on desktop systems, restores volumes for sinks
and sources upon GNOME session login, so the effect is mitigated.)
However, the shutdown sequence should no longer hang IF AND ONLY IF
alsa-utils's test condition is faulty (which is what we're attempting to
isolate).
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Daniel T Chen (crimsun)
Status: Confirmed => Incomplete
--
shutdown freeze on alsa shutdown
https://bugs.launchpad.net/bugs/274995
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
