commit | 928c38fbcf5f80d872c05257c38955b67fd3d8ce | [log] [tgz] |
---|---|---|
author | Chih-Yang Hsia <paulhsia@chromium.org> | Thu May 07 18:21:44 2020 +0800 |
committer | Commit Bot <commit-bot@chromium.org> | Mon May 11 16:41:30 2020 +0000 |
tree | 18cc2b6700c8a642b78cd7c1e131e3b8b0ef4454 | |
parent | 61d9c12064b16aa9b3cdb45735d2bde1b087dfaa [diff] |
cros-pulse-config: Add cros-audio-config to Wants of pulseaudio Under several scenarios: - CrOS suspends for a while when using Crostini or - `vmc start termina`, `lxc stop penguin` and restart Crostini, pulseaudio will go into inactive state and it will be re-activated again by the next audio action. (e.g. Play audio from some apps). But cros-audio-config won't restart with a new pulseaudio start and this will cause no audio issue since pulseaudio will fallback to use module-null-sink. To resolve the issue, we add cros-audio-config to the Wants list of pulseaudio and test it with systemd commands: ``` systemctl --user stop pulseaudio systemctl --user start pulseaudio systemctl --user status cros-pulse-config ``` cros-pulse-config should be re-run and update to the latest timestamp. And we should see module-alsa-sink in ``` pactl list sinks short ``` Bump up version to 0.1.3. BUG=b:155857693 BUG=chromium:1068945 TEST=Build cros-pulse-config_0.1.3_all.deb pkg and install TEST=crostini.AudioPulseSanity.* Change-Id: I3aebcdfd69706471b6c4670554affe64f9df74b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2186706 Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Fergus Dall <sidereal@google.com> Tested-by: Tomasz Figa <tfiga@chromium.org> Commit-Queue: Chih-Yang Hsia <paulhsia@chromium.org> (cherry picked from commit 7c0aad60c7b0868d09d210a62054a3a57961efbb) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2193320 Tested-by: Chih-Yang Hsia <paulhsia@chromium.org> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.