GNOME Bugzilla – Bug 783302
v4l2src: My webcam ceased to work
Last modified: 2017-06-05 15:47:38 UTC
Cheese 3.22.1 "There was an error playing video from the webcam" $ cheese (cheese:3361): Gtk-WARNING **: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version libv4l2: error turning on stream: Input/output error libv4l2: error turning on stream: Input/output error (cheese:3361): cheese-WARNING **: Failed to allocate required memory.: gstv4l2src.c(531): gst_v4l2src_decide_allocation (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin28/GstV4l2Src:v4l2src1: Buffer pool activation failed A fragment from usb-devices output: T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=17a1 ProdID=0128 Rev=01.00 S: Manufacturer=TASCORP S: Product=USB2.0 JPEG WebCam C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=224mA I: If#= 0 Alt= 0 #EPs= 1 Cls=00(>ifc ) Sub=00 Prot=00 Driver=t613 Particularly the above proves that the USB cable is connected. Reboot does not help. Note that in the not so long past Cheese worked without any problems. I use Debian "testing" rolling release.
$ uname -a Linux victor.local 4.9.0-3-686-pae #1 SMP Debian 4.9.25-1 (2017-05-02) i686 GNU/Linux
What is the output / result of the following command?: gst-launch v4l2src ! xvimagesink ("gst-launch" might have other names depending on your distribution, e.g. on Fedora 25 it is called "gst-launch-1.0".)
$ gst-launch-1.0 v4l2src \! xvimagesink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock libv4l2: error turning on stream: Input/output error ERROR: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: Output window was closed Additional debug info: xvimagesink.c(555): gst_xv_image_sink_handle_xevents (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0 Execution ended after 0:00:28.004134396 Setting pipeline to PAUSED ... Setting pipeline to READY ... libv4l2: error turning on stream: Input/output error Setting pipeline to NULL ... Freeing pipeline ... After "libv4l2: error turning on stream: Input/output error" there was created a window. The rest output appeared after I closed the window.
As it also happens on the command line, this is not a problem in Cheese. Which feedback have you received in a forum of your distribution about this problem?
Which gstreamer / gstreamer1 version is this about? Which graphics driver is used?
$ gst-launch-1.0 --version gst-launch-1.0 version 1.10.4 GStreamer 1.10.4 http://packages.qa.debian.org/gstreamer1.0 The following graphics driver software is used: $ dpkg -p xserver-xorg-video-nouveau Package: xserver-xorg-video-nouveau Priority: optional Section: x11 Installed-Size: 454 Maintainer: Debian X Strike Force <debian-x@lists.debian.org> Architecture: i386 Source: xserver-xorg-video-nouveau (1:1.0.11-1) Version: 1:1.0.11-1+b1 Provides: xorg-driver-video Depends: libc6 (>= 2.15), libdrm-nouveau2 (>= 2.4.38), libdrm2 (>= 2.4.25), libudev1 (>= 183), xorg-video-abi-19, xserver-xorg-core (>= 2:1.16.99.901) Recommends: libgl1-mesa-dri (>= 9.0) Filename: pool/main/x/xserver-xorg-video-nouveau/xserver-xorg-video-nouveau_1.0.11-1+b1_i386.deb Size: 316156 MD5sum: 1504ec915b5e52c21b874c8ebf51472d Description: X.Org X server -- Nouveau display driver Homepage: http://nouveau.freedesktop.org/wiki/ Description-md5: b084a16945b86c1eda89ad33dbb4530d Tag: admin::hardware, hardware::video, role::plugin, use::driver, x11::xserver SHA1: a2e7c911c5118b70735f2d1d9bcc063c39697c2a SHA256: 9be560f56deca572418d2489de7a64c583ff331f90de81aa2121f0a9337caffa $ dpkg -p libdrm-nouveau2 Package: libdrm-nouveau2 Priority: optional Section: libs Installed-Size: 51 Maintainer: Debian X Strike Force <debian-x@lists.debian.org> Architecture: i386 Multi-Arch: same Source: libdrm Version: 2.4.60-3 Depends: libc6 (>= 2.4), libdrm2 (>= 2.4.38) Pre-Depends: multiarch-support Filename: pool/main/libd/libdrm/libdrm-nouveau2_2.4.60-3_i386.deb Size: 23448 MD5sum: 1d2217c3572d520698c7e1323250f406 Description: Userspace interface to nouveau-specific kernel DRM services -- runtime Description-md5: a8a5d523c49607cd4a96eb6032dcb202 Tag: role::shared-lib SHA1: 22deb2ea2f6e54be97354221e2f26fcab56b25ed SHA256: af14cf04a3ccae0f575ee8f1916a7b2f9935fe536b33dd52ab6d6f13883f9c3c $ dpkg -p libdrm2 Package: libdrm2 Priority: optional Section: libs Installed-Size: 86 Maintainer: Debian X Strike Force <debian-x@lists.debian.org> Architecture: i386 Multi-Arch: same Source: libdrm Version: 2.4.60-3 Depends: libc6 (>= 2.17) Pre-Depends: multiarch-support Filename: pool/main/libd/libdrm/libdrm2_2.4.60-3_i386.deb Size: 33354 MD5sum: 0e2af132d7aa71375932fd42d278dd17 Description: Userspace interface to kernel DRM services -- runtime Description-md5: aefc4200d84a6f2aee6f342bdd88dc24 Tag: implemented-in::c, role::shared-lib SHA1: 232348a0398346d85cd121711d6eebef6a6cce34 SHA256: bda0f2fb4a8e8d957d0f2d25e29395eefa8cd2d33b0035440032b653da54a879
I've reported to Debian bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863957
Please provide what the debian dev is requesting, I would have asked the same. >are there any errors in the Kernel >message buffer visible? Please type >dmesg and look for errors. >Could you please try qv4l2 and check if >it displays proper video?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!