Google Git
Sign in
chromium / chromium / src / 7f0bc4b11547e958f6cd1b793ec2566d7c2f6918
commit7f0bc4b11547e958f6cd1b793ec2566d7c2f6918[log] [tgz]
authorLambros Lambrou <lambroslambrou@chromium.org>Thu Dec 12 19:35:33 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Dec 12 19:35:33 2024
tree4eba512fcab613df0ee16ee911e0c235c4f903c2
parent3bd9accf466b1eddbb5a533f4eff04d928c58cbf [diff]
[remoting] Support WirePlumber >= 0.5

The config template used by the Linux remoting host does not work with
newer versions of WirePlumber. Instead, this CL causes the host to run
WirePlumber with the default system config, but with a customized
profile.

The Debian package installs a new WirePlumber config "fragment" which
adds a custom "chrome-remote-desktop" profile. This will only be loaded
by newer WirePlumber versions which support config fragments.

Also, the environment variable $PIPEWIRE_REMOTE is added to the
session-manager child process, so that the virtual Audio/Sink device
is used by the session-manager and audio clients.

(cherry picked from commit 7b20861a958937757b4d2a2965b9806e2987780e)

Bug: 372866283
Change-Id: I7e001bb5bee5f10265daa68caaf9e6bfeb639e57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6076056
Reviewed-by: Erik Jensen <rkjnsn@chromium.org>
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1393978}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092196
Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#2055}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
4 files changed
tree: 4eba512fcab613df0ee16ee911e0c235c4f903c2
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.