Issue 399939 in chromium: WebRTC hangout video input broken, gives a green screen

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 399939 by adys...@gmail.com: WebRTC hangout video input broken,
gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/36.0.1985.125 Safari/537.36

Steps to reproduce the problem:
As described here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/hangouts/E8mYgSxISu0/dSazvW9Ui9sJ

What is the expected behavior?

What went wrong?
Screenshot: https://mediacru.sh/Ue_d8nitxy6y

Attached is a dump from chrome://webrtc-internals.

Did this work before? N/A

Chrome version: 36.0.1985.125 Channel: stable
OS Version: Arch Linux
Flash Version: No flash

Attachments:
d09df289-5e39-4350-97bf-b637fd3b6e3d.gz 14.4 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #1 on issue 399939 by adys...@gmail.com: WebRTC hangout video input

broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Video output works fine, by the way; I can see other people's videos.

[chro...@googlecode.com]

Updates:
Labels: Cr-Blink-WebRTC

Comment #2 on issue 399939 by ashej...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #9 on issue 399939 by adys...@gmail.com: WebRTC hangout video input

broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Maybe this is the same as https://crbug.com/176825

[chro...@googlecode.com]

Comment #10 on issue 399939 by adys...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Funnily enough I don't get a green screen on
http://webdesign.maratz.com/lab/responsivetypography/.

[chro...@googlecode.com]

Updates:
Cc: brav...@chromium.org vikasm...@chromium.org

Comment #11 on issue 399939 by tnak...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #12 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Chrome on Linux only supports several video capture formats.
You can check it by installing v4l2-ctl and "v4l2-ctl --list-formats".
Also you can try some other webcams.

[chro...@googlecode.com]

Comment #14 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

These two formats should be both supported by chrome on Linux. It's
interesting that you don't have problem with the link in #10. How about
http://googlechrome.github.io/webrtc/samples/web/content/getusermedia/ then?

Do you have other webcam to verify with, i.e. C910, 9000?
And have you ever built webrtc on Linux?

[chro...@googlecode.com]

Comment #15 on issue 399939 by adys...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

That link also works fine.

I don't have another webcam available unfortunately. And I have not built
webrtc before, no.

[chro...@googlecode.com]

Comment #16 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Weird. How about other webrtc demos on
https://github.com/GoogleChrome/webrtc? Especially the peer-connection and
munge-sdp demo?

[chro...@googlecode.com]

Comment #17 on issue 399939 by adys...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

They all display camera input just fine.

[chro...@googlecode.com]

Comment #18 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

But you said you got green video with
https://apprtc.appspot.com/?debug=loopback . That doesn't make any sense.
Could you please try again?

If possible you could help to get the chrome log by "--enable-logging --v=3
--vmodule=*libjingle/*=3,*=0".
(http://www.chromium.org/for-testers/enable-logging)

[chro...@googlecode.com]

Comment #19 on issue 399939 by adys...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Yup, definitely green screen on that last one.

I'll get you some logs in a minute.

[chro...@googlecode.com]

Comment #20 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Emmm, how about https://apprtc.appspot.com/?debug=loopback&hd=false ?

[chro...@googlecode.com]

Comment #21 on issue 399939 by adys...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

That one works fine.

Only logging output I get with % chromium --enable-logging --v=3
--vmodule='*libjingle/*=3,*=0'

[12281:12306:0806/050201:ERROR:raw_channel_posix.cc(139)] recvmsg:
Förbindelse borttagen av partnern
[12281:12306:0806/050201:ERROR:channel.cc(297)] RawChannel fatal error
(type 1)
[12281:12306:0806/050206:ERROR:raw_channel_posix.cc(139)] recvmsg:
Förbindelse borttagen av partnern
[12281:12306:0806/050206:ERROR:channel.cc(297)] RawChannel fatal error
(type 1)
[12281:12306:0806/050217:ERROR:raw_channel_posix.cc(139)] recvmsg:
Förbindelse borttagen av partnern
[12281:12306:0806/050217:ERROR:channel.cc(297)] RawChannel fatal error
(type 1)
[12281:12306:0806/050224:ERROR:raw_channel_posix.cc(139)] recvmsg:
Förbindelse borttagen av partnern
[12281:12306:0806/050224:ERROR:channel.cc(297)] RawChannel fatal error
(type 1)

WARNING: no real random source present!
[12281:12306:0806/050244:ERROR:raw_channel_posix.cc(139)] recvmsg:
Förbindelse borttagen av partnern
[12281:12306:0806/050244:ERROR:channel.cc(297)] RawChannel fatal error
(type 1)

[chro...@googlecode.com]

Comment #22 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

OK. Then I should know the problem now.
Now the default WebRTC is 720HD. But the C270 should only support 720 with
MJPG. Unfortunately, what chrome supports is MJPEG. So we could enumerate
that device with HD support, but get an unsupported capture format. Then
you would see green video.

The code is here: http://goo.gl/s7lnxR

This has been discussed before. But we won't add more supported format
unless it's widely used. I'm afraid MJPG is this case. You can try other
webcam, i.e. C910/9000.

Does anyone know if Hangout could force VGA or other size?

[chro...@googlecode.com]

Comment #28 on issue 399939 by kiwi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Same issue here with the Logitech C525 freshly brought for use with
Hangouts..

ID 046d:0826 Logitech, Inc.
$ sudo v4l2-ctl --list-formats
ioctl: VIDIOC_ENUM_FMT
Index : 0
Type : Video Capture
Pixel Format: 'YUYV'
Name : YUV 4:2:2 (YUYV)

Index : 1
Type : Video Capture
Pixel Format: 'MJPG' (compressed)
Name : MJPEG

Chromium Version 36.0.1985.143 (287914)

Archlinux on amd64.

I tested the various links provided here and have the same results as the
issue creator.


The logitech C270, C310 and C525 are flagship products for Logitech
webcams. Supporting them would be really useful. C910 is the other most
sell Logitech webcam but it's not the same price range (70$ vs 25-35$).

[chro...@googlecode.com]

Comment #29 on issue 399939 by kiwi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

brav...@chromium.org: I tried to rebuild chromium with the patch you
suggest, but "V4L2_PIX_FMT_MJPG" is not defined in #include
<linux/videodev2.h>

Isn't MJPEG and MJPG the same thing? "V4L2_PIX_FMT_MJPEG" is already there
and seems to be the default choice when HD is detected.

What is the next step?

I will try to gdb into
https://code.google.com/p/webrtc/source/browse/trunk/webrtc/modules/video_capture/linux/video_capture_linux.cc#158.

[chro...@googlecode.com]

Comment #30 on issue 399939 by kiwi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Additional information: it does work using today raw build from
https://download-chromium.appspot.com/ Version 39.0.2130.0 custom (290921)
(64-bit).

[chro...@googlecode.com]

Updates:
Owner: brav...@chromium.org

Comment #32 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
http://code.google.com/p/chromium/issues/detail?id=399939

Oops, it's my bad. Yes MJPEG is the MJPG in the vol2-ctl result, which is
actually same as my result with C910 on my Linux box. I'm not sure how I
made such a mistake. Thanks kiwiii@ for pointing it out!
And it's strange that it works with 39.0.2130, since I didn't see any work
done on the video_capture_linux.cc in chromium recently.

@kiwiii, I think it's easier to debug into webrtc than chromium, if webrtc
standalone could reproduce the same problem with HD size.
By building webrtc standalone, you can run vie_auto_test and debug with
a "simple loopback call". Also there would be a ViELoopbackCall_trace.txt
in the out/ folder. I could help on checking that log file too. Let's see
where it fails first.

[chro...@googlecode.com]

Comment #35 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen

https://code.google.com/p/chromium/issues/detail?id=399939

@kroylar, you can just build all by "ninja -C out/Debug"
(https://sites.google.com/site/webrtc/reference/getting-started) and run
vie_auto_test by "./out/Debug/vie_auto_test" and do a "simple loopback
test" by option '7'. Then following the on-screen instructions(enter for
default) until you see the video in the two windows if there is any.
Remember to choose WHD(1280x72) for the video size.
If it doesn't work, please help to collect the trace file. You can add more
debug info in the capture source codes.

@mark, yes you can debug with chromium. But it's more easy with webrtc. And
I have no idea about why chrome works, but chromium doesn't. Could you also
please help to figure it out? Thanks!

[chro...@googlecode.com]

Comment #36 on issue 399939 by sebastia...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I have the same issue with a Logitech C910 on Chromium 37.0.2062.94 on Arch
Linux x86_64.

When I install the latest version (Chromium 39), everything works fine.

[chro...@googlecode.com]

Comment #39 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen

https://code.google.com/p/chromium/issues/detail?id=399939

I just tried to compile chromium-dev (Arch x86_64), my C310 still won't
work with Hangouts.

https://apprtc.appspot.com/?debug=loopback doesn't work either.
https://apprtc.appspot.com/?debug=loopback&hd=false works fine.

[chro...@googlecode.com]

Comment #40 on issue 399939 by sebastia...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Still the same issue with a Logitech C910 on Chromium 38.0.2125.101 on Arch
Linux x86_64.

Lust like the person above me,
https://apprtc.appspot.com/?debug=loopback&hd=false works fine,
https://apprtc.appspot.com/?debug=loopback&hd=true doesn't.

[chro...@googlecode.com]

Comment #41 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Logitech C270, Chromium Version 38.0.2125.101 (290379) (64-bit), Arch Linux
x86_64 still same issue. HD is green, no HD works OK.

[chro...@googlecode.com]

Comment #42 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re comment #39, 40 and 41: Could you try using guvcview and select 1280x720
in the video tab (guvcview /dev/video0)? Does it work or is it green?

https://www.archlinux.org/packages/community/i686/guvcview/

[chro...@googlecode.com]

Comment #43 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re #42: Nothing happens, see attached file for output.
As a regular user I get the attached output + Segmentation fault, as root
only the attached output.

Attachments:
guvc_out.txt 13.6 KB

[chro...@googlecode.com]

Comment #44 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Exact same thing as #42 happens to me.

[chro...@googlecode.com]

Comment #45 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Exact same thing as #43 happens to me.

[chro...@googlecode.com]

Updates:
Cc: mca...@chromium.org

Comment #46 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #47 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

guvcview fails enumeration mjpeg formats but should still work with yuyv
which enumerates fine.

Could you also attach the output of: v4l2-ctl --device 0 --list-formats-ext

Thanks for your help!

[chro...@googlecode.com]

Comment #48 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Tried "guvcview -f yuyv". Still getting the seg fault.
Got your output.

Attachments:
v4l2-ctl-output 9.2 KB

[chro...@googlecode.com]

Comment #49 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Thanks!
So the issue here seems to be that it cannot enumerate MJPEG falling back
to YUYV. YUYV consumes more bandwidth than MJPEG, could it be that your
camera is not getting the USB bandwidth it needs to 1280x720?

Has something changed on the OS side resulting in that MJPEG no longer
works hence falling back to more USB bandwidth consuming YUYV resulting
1280x720 no longer works? Whats strange however it seems some of you get it
working with Chromium 39. Is that the case for you too b.karnek?

[chro...@googlecode.com]

Comment #50 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Not sure about the USB bandwidth issue, I just tried on different USB2/USB3
ports, doesn't seem to change anything.
I don't think something's wrong with MJPEG on the OS level (all of the
above links work w/ firefox).
I tried both versions of chromium (stable and dev, so yeah, I'm using 39
now), and both behave like I said in #39.

[chro...@googlecode.com]

Comment #51 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Firefox does not support HD (1280x720) with WebRTC so you are not testing
the same thing.

Do you have any other app that could open the camera in 1280x720, if so
which format does it use?

[chro...@googlecode.com]

Comment #52 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

FYI I'm running Ubuntu trusty without any issues with either Logitech C910
or MS HD 3000 in 1280x720 using Chromium or Chrome.

[chro...@googlecode.com]

Comment #53 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

@jansson
My v4l2-ctl output is attached as a diff from what is shown in comment #48
(mostly the same)

As for "guvcview -f yuyv", as the comment #48

Tried different USB ports (USB2, USB3) - same green screen.

Attachments:
v4l2ctl-device0 657 bytes

[chro...@googlecode.com]

Comment #54 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re #53:

YUYV
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/10, 1/5,

MJPEG
{ discrete: width = 1280, height = 720 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,

So it seems MJPEG fails as it should be chosen before YUYV due to higher
FPS (30vs 10).

Does any other app work with your camera in 720p?

[chro...@googlecode.com]

Comment #55 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re #54:
Skype looks like it works ok (dont know what resolution), Cheese works at
1280x960 (which is the maximum). I'm not sure where else I can check.

[chro...@googlecode.com]

Comment #56 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Browse to
http://googlechrome.github.io/webrtc/samples/web/content/manual-test/constraints/

Then enter 1280x960 in the minWidth and minWidth in the mandatory section
then request getUserMedia.

Do you get a proper video stream?

[chro...@googlecode.com]

Comment #57 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I tried with wxcam :
- yuyv @720p
- mpeg @720p

They both work fine, but error messages keep showing up in my terminal when
using mpeg

Attachments:
wxcam_yuyv_720p 347 bytes
wxcam_mpeg_720p 1.9 KB

[chro...@googlecode.com]

Comment #58 on issue 399939 by jan...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

You could also try 1280x720 in the min section and 10 FPS in the max
section to see if it works.

[chro...@googlecode.com]

Comment #59 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re #56, #58

Requesting getUserMedia with constraints: {
"audio": true,
"video": {
"mandatory": {
"minWidth": "1280",
"minHeight": "960"
},
"optional": []
}
}
Green Video like in hangouts


Requesting getUserMedia with constraints: {
"audio": true,
"video": {
"mandatory": {
"minWidth": "1280",
"minHeight": "720",
"maxFrameRate": "10"
},
"optional": []
}
}
Same green video


Tried wxcam like #57
YUVU, Auto Driver - the FPS below 10, but there is a video
MPEG, Auto Driver - the FPS is on average 30, there is a video, but same
errors in the console like #57 except I also have this line
"VIDIOCGCAP: Inappropriate ioctl for device"

[chro...@googlecode.com]

Comment #60 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Requesting getUserMedia with constraints: {
"audio": true,
"video": {
"mandatory": {
"minWidth": "1280",
"minHeight": "960"
},
"optional": []
}
}

Green screen same as #59

Requesting getUserMedia with constraints: {
"audio": true,
"video": {
"mandatory": {
"minWidth": "1280",
"minHeight": "720",
"maxFrameRate": "10"
},
"optional": []
}
}

Black screen, webcam light goes off after one second, looks like the cam
turns off

[chro...@googlecode.com]

Comment #61 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

It's hard to tell anything without debugging with Arch Linux as it should
be an OS specific issue. I could find some time to install a Arch Linux VM.
Wondering how popular Arch Linux is?

[chro...@googlecode.com]

Comment #62 on issue 399939 by Ko.Dmi...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Re #61
First of all thanks for the efforts! Good (I guess) to know this is an OS
specific issue, Ill try to search answers in arch linux community.

About popular, arch linux (according to distrowatch) is on the 7th place,
right after mint, ubuntu, debian, mageia, fedora and opensuse
(http://distrowatch.com/). So yea, it is pretty popular! :)

[chro...@googlecode.com]

Comment #67 on issue 399939 by tim.r...@googlemail.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I have the same issues on Gentoo, so I doubt that this is an Archlinux
specific issue, as some suggested above.

Also on Gentoo installing Chromium means, building it from sources, so I
also doubt, that the problem is in the distro specific packaging process.

Tried the lini in #56 and having the same green screen as in hangouts. The
light on my webcam (Logitech HD C270) stays on all the time until I close
the webpage.

The camera itself works fine (when opening in VLC) and hangout with this
camera on the same computer also works fine, when using firefox (which I
assume is still using the old plugin?!)

Is there any additional information I can provide helping solving this
issue?

If it would help you, trying something on my computer, we could also find a
date for Teamviewing/VLC'ing. You can find my contact information on
https://www.timroes.de/about-me

I am glad to help fixing this, since it's pretty annoying to switch always
to firefox jsut to use hangouts :-)

[chro...@googlecode.com]

Comment #68 on issue 399939 by mca...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

tim.roes88, if you don't mind terribly and are able to build Chromium,
perhaps you could try and modify the value of the constants used in line
[1], namely |kMjpegWidth| and |kMjpegHeight|, to be above 1280 and 720,
respectively, then try again #56. It might be that the JPEG format used by
these cameras has some quirk that confuses libyuv, which is what we use to
decode this format [2].


[1]
https://code.google.com/p/chromium/codesearch#chromium/src/media/video/capture/linux/video_capture_device_linux.cc&sq=package:chromium&type=cs&l=234&rcl=1412920526
[2]
https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/renderer_host/media/video_capture_controller.cc&sq=package:chromium&type=cs&q=videocapturecontroller%20mjpeg&l=453

[chro...@googlecode.com]

Comment #69 on issue 399939 by b.ka...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Might as well pull the git repo and compile from there. I'd rather do that
than alter packages that are supposed to be handled by Portage (or any
package manager).
I'll try that tomorrow.

[chro...@googlecode.com]

Comment #70 on issue 399939 by sebastia...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

#68, that did it!
I compiled Chromium 38.0.2125.101 with both kMjpegWidth and kMpjegHeight
set to 2000, and now:

- https://apprtc.appspot.com/?debug=loopback&hd=true WORKS
-
http://googlechrome.github.io/webrtc/samples/web/content/manual-test/constraints/
with 1280x960 minWidth x minWidth WORKS
- Hangouts WORKS!

The strange thing is that all of this also works with the pre-compiled
Google Chrome 38.

[chro...@googlecode.com]

Comment #71 on issue 399939 by tim.r...@googlemail.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I can also confirm, that increasing the two constants to 2000 solves the
problem on Gentoo.

[chro...@googlecode.com]

Comment #72 on issue 399939 by tim.r...@googlemail.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I can also confirm, that increasing the constants to 2000 solves the
problem (on the test page and in hangouts) on Gentoo. Also I experience the
same as #70, meaning Google Chrome 38 worked already, while Chromium 38
didn't.

[chro...@googlecode.com]

Comment #73 on issue 399939 by brav...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Installing an Arch Linux is too troublesome. No time for it.

Could anyone here help to check if there is any difference of the captured
buffer between ArchLinux and Ubuntu? And how libyuv failed to decode it on
Arch Linux?
BTW: It would be much easier to debug with WebRTC standalone. By
launching './out/Debug/vie_auto_test' could start a simple loopback test.

[chro...@googlecode.com]

Comment #75 on issue 399939 by daniel.c...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Experiencing the same green-screen issues with hangout and
using https://apprtc.appspot.com/?debug=loopback&hd=true

https://apprtc.appspot.com/?r=45283765&debug=loopback&hd=false (works fine)

extra/chromium 38.0.2125.111-1
3.17.2-1-ARCHx 86_64 GNU/Linux

dmesg:
[ 157.299394] Linux video capture interface: v2.00
[ 157.366951] uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0361)
[ 157.400896] usbcore: registered new interface driver uvcvideo

possibly related:
Skype and VLC can capture video fine, though cheese segfaults after
capturing a single frame.

SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffba7fc700 (LWP 3082)]
0x00007fffd795cc62 in ?? () from /usr/lib/libjpeg.so.8
(gdb) where
#0 0x00007fffd795cc62 in ?? () from /usr/lib/libjpeg.so.8

(no debug symbols, unfortunately)

[chro...@googlecode.com]

Comment #76 on issue 399939 by daniel.c...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

...and it works in google-chrome-stable from aur.archlinux.org ver:
38.0.2125.111-2

[chro...@googlecode.com]

Comment #77 on issue 399939 by sebastia...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I opened a bug[1] about this in the Arch Linux bug tracker, and the
packager found the issue! The problem seems to be that the Arch package was
built with the system libjpeg-turbo instead of the bundled libjpeg.

To all Arch users, could you please test the package mentioned in the 1st
comment of the bug report?

[1]https://bugs.archlinux.org/task/42747

[chro...@googlecode.com]

Comment #78 on issue 399939 by evange...@foutrelis.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Ideally I would want to continue building Chromium against the system
libjpeg.

@Chromium devs: Is this incompatibility between libyuv abd libjpeg-turbo
something you could possibly look into? (I'm guessing it could also be a
bug in libjpeg-turbo itself.)

[chro...@googlecode.com]

Comment #79 on issue 399939 by daniel.c...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

#77, The bundled libjpg version of chromium works for me too.
#78, The cheese crash mentioned earlier (#75) seems to be related to libjpg
as well so I'd say your guess is plausible.

[chro...@googlecode.com]

Comment #80 on issue 399939 by evange...@foutrelis.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

@Daniel: How about Chromium with system libjpeg, but with libjpeg-turbo
from svn trunk:

http://pkgbuild.com/~foutrelis/test-builds/libjpeg-turbo-svn-r1412/

Make sure to reinstall Chromium from the Arch repos before testing.

(I want to see if the issue still exists with latest libjpeg-turbo from svn
trunk.)

[chro...@googlecode.com]

Comment #81 on issue 399939 by daniel.c...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

@evan

Using Chromium 38.0.2125.111 from the arch repositories and
libjpeg-turbo-svn-r1412
no longer produces green-screen errors on the HD test or in hangouts.

...

cheese still segfaults though, if you're curious (VLC video capture still
works):

SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffba7fc700 (LWP 3082)]
0x00007fffd795cc62 in ?? () from /usr/lib/libjpeg.so.8

$ pkgfile /usr/lib/libjpeg.so.8
extra/libjpeg-turbo

[chro...@googlecode.com]

Comment #82 on issue 399939 by evange...@foutrelis.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

@Daniel: Thanks for the feedback; I need you to test one more libjpeg-turbo
package (with Chromium from the Arch repos):

http://pkgbuild.com/~foutrelis/test-builds/libjpeg-turbo-patched-r1104/

If that works as well, it means that the fix is in the following
libjpeg-turbo commit:

http://sourceforge.net/p/libjpeg-turbo/code/1104/

As far as I can see, Chromium's bundled libjpeg-turbo has a similar patch
(and that would explain why that's working as well):

https://codereview.chromium.org/7014037

[chro...@googlecode.com]

Comment #83 on issue 399939 by daniel.c...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

@evan, the last jpeg-turbo package also works.

[chro...@googlecode.com]

Comment #84 on issue 399939 by evange...@foutrelis.com: WebRTC hangout

video input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Thanks again for testing. Let's continue tracking this bug downstream in
Arch.

This issue can probably be closed, though I guess Chromium should drop its
local modifications from CR#7014037 [1] when the bundled libjpeg-turbo is
updated to 1.4.

[1] https://codereview.chromium.org/7014037

[chro...@googlecode.com]

Comment #85 on issue 399939 by sebastia...@gmail.com: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

I too can confirm that everything works now in Arch with the libjpeg patch
(which is now applied to the official Arch package). Thanks everyone!

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #88 on issue 399939 by tnak...@chromium.org: WebRTC hangout video

input broken, gives a green screen
https://code.google.com/p/chromium/issues/detail?id=399939

Closing per comments #84-87.

For the suggestions in comments #78 and #84 (and possibly the documentation
recommendation in #87), would you mind filing a new bug? Thanks!