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

Issue 845536 link

Starred by 4 users

Issue metadata

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



Sign in to add a comment

Unable to use chrome os camera app on Scarlet- dru

Project Member Reported by mkarkada@chromium.org, May 22 2018

Issue description

Chrome OS Version: Chrome OS 10701.0.0, 68.0.3436.0 dev channel scarlet-dru
CCA version: 5.0.2

Steps To Reproduce:
(1) Open Chrome OS Camera app (CCA) from launcher 

Actual Result:
'Your camera is currently unavailable' error message is seen. Unable to use camera app.

Attached screenshot.
 
Screenshot 2018-05-22 at 10.20.15.png
108 KB View Download
Owner: mkarkada@chromium.org
Status: Assigned (was: Untriaged)
I guess this is not reproducible on earlier CrOS versions?
Could you provide the latest version that is working fine?
Owner: ----
Re #1, camera was working fine, latest on live version M68 (10682.0.0, 68.0.3431.0).
Owner: jcliang@chromium.org
This is probably a buffer allocation failure. I'm looking into it.
Project Member

Comment 6 by bugdroid1@chromium.org, May 29 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/12741be45ea7c93c6cdcdbb42232f0e04320ed07

commit 12741be45ea7c93c6cdcdbb42232f0e04320ed07
Author: Ricky Liang <jcliang@chromium.org>
Date: Tue May 29 03:21:43 2018

gpu: Allow gfx::BufferFormat::R_8 as force_native_gpu_read_write_formats

This is required on Chrome OS ARM platforms to allocate BLOB buffers for
camera HAL.

BUG= 845536 , 832772
TEST=Make sure camera works on Dru.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I656f7166663192c255989b68f985943eeb2d8b64
Reviewed-on: https://chromium-review.googlesource.com/1073186
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Ricky Liang <jcliang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562319}
[modify] https://crrev.com/12741be45ea7c93c6cdcdbb42232f0e04320ed07/gpu/ipc/host/gpu_memory_buffer_support.cc

Cc: bhthompson@chromium.org
Labels: Merge-Request-68
We need the CL in #6 to make CCA work on Dru on M-68.
Labels: -Merge-Request-68 Merge-Approved-68
Project Member

Comment 9 by bugdroid1@chromium.org, May 29 2018

Labels: -merge-approved-68 merge-merged-3440
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/84ce5a4696875b642b1ac88bb2be0c9ce0262010

commit 84ce5a4696875b642b1ac88bb2be0c9ce0262010
Author: Ricky Liang <jcliang@chromium.org>
Date: Tue May 29 17:50:16 2018

gpu: Allow gfx::BufferFormat::R_8 as force_native_gpu_read_write_formats

This is required on Chrome OS ARM platforms to allocate BLOB buffers for
camera HAL.

BUG= 845536 , 832772
TEST=Make sure camera works on Dru.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I656f7166663192c255989b68f985943eeb2d8b64
Reviewed-on: https://chromium-review.googlesource.com/1073186
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Ricky Liang <jcliang@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562319}(cherry picked from commit 12741be45ea7c93c6cdcdbb42232f0e04320ed07)
Reviewed-on: https://chromium-review.googlesource.com/1076847
Reviewed-by: Ricky Liang <jcliang@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#25}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/84ce5a4696875b642b1ac88bb2be0c9ce0262010/gpu/ipc/host/gpu_memory_buffer_support.cc

Status: Fixed (was: Assigned)
Cc: allendam@chromium.org
Status: Verified (was: Fixed)
Verified on M68 (10718.7.0, 68.0.3440.9).

Sign in to add a comment