I have a USB webcam, USB ID 19ff:0103 (it's branded 'Rocketfish'). Cheese used to work fine with this, I think at least up to Fedora 26, but I've just tried using it with current Fedora 27 - with cheese-3.26.0-1.fc27.x86_64 - and it runs, but doesn't read anything from the webcam (it just shows 'There was an error playing video from the webcam'). The console shows this: libv4l2: error set_fmt gave us a different result then try_fmt! libv4l2: error set_fmt gave us a different result then try_fmt! (cheese:23681): cheese-WARNING **: Device '/dev/video0' cannot capture in the specified format: gstv4l2object.c(3640): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin35/GstV4l2Src:v4l2src1: Tried to capture in BGR3, but device returned format YUYV Proposing as a Final blocker per criterion "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test" - a webcam app that can't read anything from the webcam clearly doesn't have working 'basic functionality'. Of course, whether this is accepted as a blocker will depend on whether this problem would affect all or many webcams, or if there's something weird about mine. It'd be good to have reports from other testers.
My Creative Technology USB powered web cam doesnt work as well.
I can confirm it works fine on the integrated camera in my Lenovo P50: *-usb:1 description: Video product: Integrated Camera vendor: SunplusIT Inc physical id: 8 bus info: usb@1:8 version: 0.12 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s
Discussed during blocker review [1]: RejectedBlocker AcceptedFreezeException (Final) - this seems to be hardware dependent, so far about 20% of tested cameras were affected. We think this is a low enough failure rate to not consider this a release-blocking issue, but important enough to be worth an FE if the release slips. [1] https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-11-02/
I'm unable to reproduce this (despite having tested 10+ different webcams), I've a feeling this is a kernel bug somehow, but it could also be a libv4l2 bug. Can someone who is seeing this do: LIBV4L2_LOG_FILENAME=/tmp/log cheese And then attach /tmp/log here afterwards ?
Created attachment 1347102 [details] V4L2 log requested by hans Here you go, Hans. This is with kernel 4.13.9-300.fc27.x86_64 and the same webcam listed in the initial report.
Ok, looks like a your webcam is triggering a somewhat old, but so far unnoticed bug in libv4lconvert. I've started a scratch-build of v4l-utils with a fix here: https://koji.fedoraproject.org/koji/taskinfo?taskID=22870480 Please give it a go when it is finished and let me know if it fixes things.
And the x86_64 build is done already :)
Yeah, works now. Seems very sluggish (low frame rate), but works.
Hi, (In reply to Adam Williamson from comment #8) > Yeah, works now. Good, I will go and create official updated v4l-utils packages for this then. > Seems very sluggish (low frame rate), but works. Yes I noticed that too with a few cams, where as other cams work fine, not sure what is going on here but this seems to be a separate bug. Can you try: dnf install camorama camorama -M -d /dev/video0 (/dev/video0 assuming you don't have a tvcard are some such) camorama is a quite old simple camera app, if that works the sluggishness problem is likely somewhere in gstreamer or cheese. Another interesting test-app (created and used by v4l developers) is qv4l2. Anyways it is probably a good idea to file a new bug (against cheese for now) for the sluggishness. Regards, Hans
v4l-utils-1.12.5-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8477dfde52
v4l-utils-1.12.5-5.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2c58475975
Is there anything I need to do to make use of the FreezeException (assuming there will be a time-window to do so) ?
v4l-utils-1.12.5-5.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8477dfde52
Hans: nothing you need to do, no. There may or may not be a time window, we are making the second go/no-go call this morning. There's some thorny issues to talk over.
BTW, seems it's just the camera that's slow, behaves the same with camorama. It's better at low resolutions.
v4l-utils-1.12.5-5.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2c58475975
v4l-utils-1.12.5-5.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
v4l-utils-1.12.5-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.