Created attachment 875194 [details] lsusb -v output for my webcam Description of problem: Changing the photo resolution in cheese's preferences makes the screen go blank with "there was an error playing video from the webcam" Running it in the terminal, it prints this error message when that happens: (cheese:21750): cheese-WARNING **: Internal data flow error.: gstbasesrc.c(2865): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin34/GstV4l2Src:video_source: streaming task paused, reason not-negotiated (-4) Version-Release number of selected component (if applicable): cheese-3.10.2-1.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Run cheese 2. Go to Cheese -> Preferences 3. Select a different photo resolution Actual results: Cheese goes blank with just "there was an error playing video from the webcam" printed and the above error message in the terminal. Expected results: Cheese switches the camera resolution without error and keeps displaying the webcam image. Additional info: Only restarting cheese brings the webcam display back.
I also have caught similar one today. 1. Started zbarcam in xterm. 2. Quit zbarcam by Ctrl+C 3. Tried to start zbarcam in the same terminal window 2nd time, it failed with the following message libv4l2: error turning on stream: Invalid argument ERROR: zbar processor in v4l2_start(): system error: starting video stream (VIDIOC_STREAMON): Invalid argument (22) 4. Tried to start cheese in the same terminal to see if it produces camera feed. The cheese camera window is blank and says "There was and error playing video from the webcam". The message in terminal says: (cheese:5350): GLib-GObject-WARNING **: value "5.000000" of type 'gdouble' is invalid or out of range for property 'delaytime' of type 'gdouble' libv4l2: error turning on stream: Invalid argument (cheese:5350): cheese-WARNING **: Internal data flow error.: gstbasesrc.c(2865): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin34/GstV4l2Src:video_source: streaming task paused, reason not-negotiated (-4) 5. Attempted to reloadthe webcam with sudo rmmod uvcvideo sudo modprobe uvcvideo did not help. System: $ uname -r 3.13.8-200.fc20.x86_64 libv4l-1.0.0-1.fc20.x86_64 Lenovo Thinkpad x240s
Created attachment 885837 [details] $ lsusb -vs 02:04 >> webcam.info
just tested some more, this info could be helpful: putting laptop to sleep and waking up resets the webcam, I can get an output with cheese and zbar. However, after I quit zbar the camera locks like described above, and no application can access it any longer.
Hi Andrew and Aten, Andrew, I can reproduce your bug I'll try to look into it one of these days (no promises exactly when I'll have time for this though). Aten, your issue seems to be a different issue, since for Andrew (and me) just quiting cheese and restarting it resolves the issue. Where as for you the actual camera seems to be unhappy. Can you please file a new bug, against the kernel, and attach the output of lsusb -v there ? Thanks, Hans
(In reply to Hans de Goede from comment #4) > Hi Andrew and Aten, > > Andrew, I can reproduce your bug I'll try to look into it one of these days > (no promises exactly when I'll have time for this though). > > Aten, your issue seems to be a different issue, since for Andrew (and me) > just quiting cheese and restarting it resolves the issue. Where as for you > the actual camera seems to be unhappy. Can you please file a new bug, > against the kernel, and attach the output of lsusb -v there ? Could you please also attach the kernel log (dmesg) ?
The same here. Resolution change isn't possible without a restart of cheese. The camera I used is: Logitech HD Pro Webcam C920 (046d:082d), Fedora 20, Cheese 3.10.2, 64 Bit System. With guvcview 1.7.3 it is a live resolution change possible. dmesg output: 437.249211] usb 1-1.4.3: new high-speed USB device number 7 using ehci-pci [ 438.438853] usb 1-1.4.3: New USB device found, idVendor=046d, idProduct=082d [ 438.438858] usb 1-1.4.3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 438.438861] usb 1-1.4.3: Product: HD Pro Webcam C920 [ 438.438863] usb 1-1.4.3: SerialNumber: A4E212DF [ 438.475453] media: Linux media interface: v0.10 [ 438.482697] Linux video capture interface: v2.00 [ 438.663312] usbcore: registered new interface driver snd-usb-audio [ 438.663337] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 438.664285] input: HD Pro Webcam C920 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/input/input16 [ 438.664409] usbcore: registered new interface driver uvcvideo [ 438.664411] USB Video Class driver (1.1.1)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.