New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 607740 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

No audio (volume button non functional) on TOT

Project Member Reported by rookrishna@chromium.org, Apr 28 2016

Issue description

ChromeOS 52.0.2719.0/8253.0.0 samus

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)  AU to build  52.0.2719.0/8253.0.0 samus

(2) Play any audio
(3) 

Expected Result: Audio 

Actual Result: No audio. Volume slider unmovable

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always on TOT

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.


 
Summary: No audio (volume button non functional) on TOT (was: No audio (volume button non functional) on Samus TOT)
Reproduced on Peppy TOT build

Comment 2 by dgreid@chromium.org, Apr 29 2016

Owner: dgreid@chromium.org
Status: Started (was: Untriaged)
build system breakage, fix posted. https://chromium-review.googlesource.com/#/c/341263/1
Cc: kavvaru@chromium.org durga.behera@chromium.org songsuk@chromium.org pucchakayala@chromium.org ajha@chromium.org
 Issue 607812  has been merged into this issue.
Issue 607979 has been merged into this issue.
Cc: rohi...@chromium.org avkodipelli@chromium.org hsiangc@chromium.org

Comment 6 by willg...@gmail.com, Apr 30 2016

Will this fix the broken mic in this build as well or should I open a separate issue?

Comment 7 by dgreid@chromium.org, Apr 30 2016

same issue, if the CQ would give a clean run it will land soon.
Project Member

Comment 8 by bugdroid1@chromium.org, Apr 30 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/adhd/+/24dfdc806405b7c588ed77783b03612dde0f1fe6

commit 24dfdc806405b7c588ed77783b03612dde0f1fe6
Author: Dylan Reid <dgreid@chromium.org>
Date: Fri Apr 29 01:10:44 2016

CRAS: Set default for CRAS_CONFIG_FILE_DIR to /var/run/cras

The change:
8d225aa - CRAS: Make socket directory configurable.
Set the default using the $localstatedir variable, however that is set
to /usr/local/var in Chrome OS builds, which was a change from /var that
left apps unable to find the server socket.

BUG= 607740 
TEST=play audio on Samus

Change-Id: I441c0073f7a92ae999ca33d07d44ad2d4e3787b8
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/341263
Reviewed-by: Ben Zhang <benzh@google.com>

[modify] https://crrev.com/24dfdc806405b7c588ed77783b03612dde0f1fe6/cras/configure.ac

Status: Fixed (was: Started)
finally got through the CQ!
Cc: dgreid@chromium.org
 Issue 608240  has been merged into this issue.
Status: Verified (was: Fixed)
Verified on ChromeOS 8270.0.0, 52.0.2721.0

Sign in to add a comment