GNOME Bugzilla – Bug 603219
Logitech Quickcam IM webcam is not recognized
Last modified: 2010-04-14 16:21:41 UTC
ID 046d:08a0 Logitech, Inc. QuickCam IM is not recognized by Cheese, while it works on Skype 2.0.0.72 .
additional comments: my webcam is recognized by Ekiga also. When I launch gstreamer-properties, i get the following messages (but it does not block the application): gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' In the "Video" tab of gstreamer-properties, I tried all combinations of "Default Output" and "Default Input", no one gives the webcam output when I clcik on Test in the gstreamer-properties window. I tried also to start Cheese after all combinations of gstreamer-properties, each time closing gstreamer-properties then launching Cheese, then closing Cheese and launching gstreamer-properties again to choose another combination. Here are all possibilities I have in gstreamer-properties : Default ouput: Plugin: -Autodetect (was used by default) -X window system (without Xv) -X window system (X11/XShm/Xv) -> Device : Default /or ATI Radeon Overlay /or Radeon Textured Video - Personalized Default input: Plugin: -Input test - v4l - v4l2 -> By default (was used by default) /or USB camera (046d:08a0) - Personalized hope this helps... regards
What's the output of "lshal" on this machine with the webcam plugged in?
Also, do you know which driver are you using? This kind of issue usually arises when using unmaintained out of tree drivers (like gspcav1). A cheese -v output can be helpful too.
Created attachment 149001 [details] lshal (end of output only)
Created attachment 149002 [details] cheese -v output
@Bastien & Filippo: thank you for your answers. Here are the requested logs. The "lshal" log is trunkated. Please remember me the command to paste it directly into a text file. Concerning the driver, please tell me to know it ?
(In reply to comment #6) > @Bastien & Filippo: thank you for your answers. Here are the requested logs. > The "lshal" log is trunkated. Please remember me the command to paste it > directly into a text file. > Concerning the driver, please tell me to know it ? No need for a complete lshal, cheese -v is enough. The device is being detected correctly, it seems something else is failing. What exactly do you see when you launch cheese? the colored bars?
yes, i see the colored bars.
Could you please attach a log file created with this command? Just run it, let it finish and attach the "debug.log" file it creates. GST_DEBUG=*:3 gst-launch-0.10 -v v4l2src ! fakesink num-buffers=1 > debug.log 2>&1
i launched the command, plugged the webcam, then the waited 5 minutes , but the process in the terminal had not stopped: see first log (copy/paste from terminal). Then I disconnected the webcam: this stopped the process in the terminal: see 2nd log (copy/paste from terminal). Then I realized the copy/paste of your command did not take the end (2>&1). So i edited it inside the Text editor, and pasted the right command in the terminal (after pluggin in the webcam). After 5 minutes , I unplugged the webcam. a debug.log was created : 3rd atteched file.
Created attachment 149017 [details] GST_DEBUG wrong command (before disconnecting webcam)
Created attachment 149018 [details] GST_debug wrong command (deconnected webcam)
Created attachment 149019 [details] debug.log (right command)
Wow, that's kinda strange. v4l2src manages to open the device correctly and get caps but when it tries to grab frames fails "no such device" errors. I don't really have any clue, that's the first time I see an error like this. Does "gst-launch-0.10 v4l2src ! ffmpegcolorspace ! xvimagesink" work?
In which conditions should I use this command? (webcam connected? Cheese started? etc..) What result should I expect? I did it first without webcam (and without Cheese): yyy@yyy-laptop:~$ gst-launch-0.10 v4l2src ! ffmpegcolorspace ! xvimagesink Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device "/dev/video0". Additional debug info: v4l2_calls.c(482): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... Then I plugged the webcam, and tried the command again (still without Cheese): yyy@yyy-laptop:~$ gst-launch-0.10 v4l2src ! ffmpegcolorspace ! xvimagesink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock It blocked here. I started Cheese, saw the lines again, and then closed Cheese. I then unplugged the webcam. Here is what was displayed in the terminal after the "New clock: GstSystemClock" line: libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device libv4l2: error dequeuing buf: No such device ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed trying to get video frames from device "/dev/video0". Additional debug info: v4l2src_calls.c(189): gst_v4l2src_grab_frame (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed after 50 tries. device /dev/video0. system error: No such device Execution ended after 66874802768 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
Wait, I missed the part where you said you disconnected the webcam. Did you do it for debug.log too? Don't! So the no device errors were right, you disconnected the device while accessing it :) About the last command, just run it with the webcam connected (forget this disconnecting thing, it is not useful at all) and no cheese (only one program can access the webcam at the time). GST_DEBUG=*:3 gst-launch-0.10 -v v4l2src ! ffmpegcolorspace ! xvimagesink > debug.log 2>&1 Expected result: you see a window with the image from the webcam. If the test succeeds, close the video window and attach the debug.log created. If the test fails, you don't see any window with the webcam images, wait for a couple of seconds (like ten), hit ctrl+c to stop gst-launch, attach the debug.log created.
As i don't know if there is a space in the command between > and "debug.log", I tried it twice. Files attached.
Created attachment 149198 [details] debug with space.log
Created attachment 149199 [details] debug without space.log
Reopening as requested information has been provided.
Yann, did the last test succeed? did you see a window with images from the webcam? Anyway, could you please test cheese 2.29.5? We changed a lot of things in the way device detection works and there is a good chance that your bug isn't reproducible anymore.
I did not get any image during my last test. (I have the default version for Karmic : 2.28.1 ) How can I install the 2.29.5 ? (Just with the "git clone git://git.gnome.org/cheese " command ? isn't there any DEB package or PPA repository ? )
I tried the following and i need your help to install the 2.29.5 : ~/depot_cheese$ git init Initialized empty Git repository in /home/yyy/depot_cheese/.git/ ~/depot_cheese$ git clone git://git.gnome.org/cheese Initialized empty Git repository in /home/yyy/depot_cheese/cheese/.git/ remote: Counting objects: 9011, done. remote: Compressing objects: 100% (3770/3770), done. remote: Total 9011 (delta 6701), reused 6835 (delta 5192) Receiving objects: 100% (9011/9011), 14.51 MiB | 64 KiB/s, done. Resolving deltas: 100% (6701/6701), done. ~/depot_cheese$ cd cheese ~/depot_cheese/cheese$ ./configure bash: ./configure: no such file or folder in the INSTALL text file is written to enter ./configure but as you see it does not work. What should i do to install the 2.29.5 ?
Heya :-) You might either wait for your distribution to pick it up, download official tarballs from http://ftp.gnome.org/pub/GNOME/sources/cheese/2.29/cheese-2.29.5.tar.bz2 or use JHBuild.
> I did not get any image during my last test. (I have the default version for > Karmic : 2.28.1 ) Sorry for the delay, it really seems cheese has nothing to do with your issue. Who's failing is either gstreamer (unlikely), your driver or the device itself. From what I see in your logs, your device claims to support 100Hz frame rate. This is probably false and since gstreamer tries to use the best rate the device advertises, it fails to display anything. My suggestion is to test cheese from git in a bleeding edge distribution livecd. You could e.g. download latest ubuntu lucid alpha and run the following: sudo apt-get build-dep cheese git clone git://git.gnome.org/cheese cd cheese ./autogen.sh --prefix=/usr make sudo make install cheese
if it is a problem due to gstreamer, my driver or the device, i feel strange it works with Ekiga and Skype (skype_2.0.0.72-0medibuntu4_i386 ,not the last version), don't you think? i will try on Lucid live-cd.
(In reply to comment #26) > if it is a problem due to gstreamer, my driver or the device, i feel strange it The issue is still there if you access the webcam with gst-launch. This excludes cheese itself. Ekiga and skype both don't use gstreamer. It leaves two choices either gstreamer is doing something wrong or gstreamer does what it should and the driver doesn't behave correctly. As I said the high advertised framerate could be a clue, could you try the following pipeline and tell me if you see any image? (Karmic is ok for this no need to run the livecd) gst-launch-0.10 v4l2src ! video/x-raw-yuv, width=640, height=480, framerate=30/1 ! xvimagesink
I tried it: no image appeared, and i had the following log: $ gst-launch-0.10 v4l2src ! video/x-raw-yuv, width=640, height=480,framerate=30/1 ! xvimagesink (gst-launch-0.10:2333): GLib-WARNING **: g_set_prgname() called multiple times Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock
Hi. This time, I tried 3 things on Lucid beta2 live-cd: 1) normally installed Cheese via Software Center: black image (no colored bars like on Karmic) 2) tried "sudo apt-get build-dep cheese" : see error log attached 3) tried the "gst-launch-0.10 ..." command: see log attached
Created attachment 152659 [details] log gst-launch on lucid
Created attachment 152660 [details] log build-dep on lucid
Yann, I think your problem is an outdated package list. Please do a apt-get update before trying to install anything. TIA!
(In reply to comment #29) > Hi. This time, I tried 3 things on Lucid beta2 live-cd: > 1) normally installed Cheese via Software Center: black image (no colored bars > like on Karmic) We dropped colored bars, you should see a big red error symbol on black background or something like that depending on the gtk theme. A cheese log produced with "GST_DEBUG=*:3 cheese > cheese.log 2>&1" could be probably useful > 2) tried "sudo apt-get build-dep cheese" : see error log attached As Tobias said, apt-get update please > 3) tried the "gst-launch-0.10 ..." command: see log attached The "log" doesn't say anything, do you see a window with images coming from your webcam? don't you? please attach a proper log with the following command if you don't. GST_DEBUG=*:3 gst-launch-0.10 v4l2src ! video/x-raw-yuv, width=640, height=480, framerate=30/1 ! xvimagesink > debug.log 2>&1
Impossible to update on live-cd: "not enough memory" (870Mo RAM is not enough?). So I will have to try on virtual-box, but I fear some USB problems due to VB...
Hi, I'am back with you :) This time, I installed Lucid beta, and updated it. Default version of Cheese is 2.30.0 . But it also does not recognize my webcam : black image. In preferences it is written (in grey) : "USB camera (046d:08a0) (dev:video0)". in terminal: 1) According to Comment 25, I did: sudo apt-get build-dep cheese git clone git://git.gnome.org/cheese cd cheese but ./autogen.sh --prefix=/usr says "You need to install gnome-common from the GNOME CVS", and of course I don't know how to do it, please could you guide me a little for this? 2) I ran the command given in Comment 27, it did the same as in Karmic (Comment 28), so I tried to launch Cheese, and it crashed: see https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/551774 3) I ran the command given in Comment 33. Please see log attached. Hope this helps make Cheese better !
Created attachment 157504 [details] debug.log in Lucid beta 31March2010
(In reply to comment #35) > Hi, I'am back with you :) This time, I installed Lucid beta, and updated it. Hi, > Default version of Cheese is 2.30.0 . But it also does not recognize my webcam > : black image. In preferences it is written (in grey) : "USB camera (046d:08a0) > (dev:video0)". > > in terminal: > > 1) According to Comment 25, I did: > sudo apt-get build-dep cheese > git clone git://git.gnome.org/cheese > cd cheese > but ./autogen.sh --prefix=/usr says "You need to install gnome-common from the > GNOME CVS", and of course I don't know how to do it, please could you guide me > a little for this? No need to install from git, lucid has the very latest cheese release. Anyway, for future reference, you're missing gnome-common install it and run autogen.sh again. > 2) I ran the command given in Comment 27, it did the same as in Karmic (Comment > 28), so I tried to launch Cheese, and it crashed: see > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/551774 WTF? Launchpad says I'm not allowed to view that page. > 3) I ran the command given in Comment 33. Please see log attached. Didn't it crash? it was the same command as the previous but with debugging enabled. Anyway, please attach the log done with GST_DEBUG=*cheese*:5 cheese -v > cheese-debug.log 2>&1 too
ok, I managed to compile it, so I now have the 2.30.1 version. But still black image. Concerning the Launchpad bug report, it was marked as "private", I changed it to public. I did your command: log attached. (maybe you will see in the log, I tried to take a picture, it made 3 -2 -1 flash, but no picture was saved.) Regards
Created attachment 157511 [details] cheese-debug.log 31march2010
(In reply to comment #38) > ok, I managed to compile it, so I now have the 2.30.1 version. But still black > image. > Concerning the Launchpad bug report, it was marked as "private", I changed it > to public. Ok, now I can see it, thanks. It seems launchpad marks bug reports containing core dumps as private thinking they might expose sensitive informations. The stack trace seems to point to a gstreamer crash but it's missing too symbols and I don't know how to analyse the core dump. > I did your command: log attached. (maybe you will see in the log, I tried to > take a picture, it made 3 -2 -1 flash, but no picture was saved.) Ok, so my guess about the too high frame rate was wrong. We force 30 frames per second and still don't get any image. So, I really have no clue. The only thing I can say for sure is that it's not cheese related, as I said in the past, the fault is either in gstreamer, in libv4l or in the device itself.
Thank you for your efforts, I will continue here: https://bugs.launchpad.net/libv4l/+bug/551858
(In reply to comment #40) > Ok, so my guess about the too high frame rate was wrong. We force 30 frames per > second and still don't get any image. > So, I really have no clue. The only thing I can say for sure is that it's not > cheese related, as I said in the past, the fault is either in gstreamer, in > libv4l or in the device itself. Hi Hans, I'm CC-ing you since you might have better chance to know what's going wrong (a quick google search tells me it should be supported by spca and work out of the box). The reporter says the webcam doesn't work with cheese nor with gst-launch but does with ekiga and skype. The device is: 046d:08a0 Logitech, Inc. QuickCam IM Thanks!
Yann, I think this might be a driver issue. Could you try running cheese, then go to the preferences and change the resolution from 640x480 to 320x240. Then exit cheese and restart cheese, it should have remembered the 320x240 you choose. I would like to know if changing to 320x240 fixes things. Also can you please do: dmesg > log And then attach the file "log" here ? Thanks. Regards, Hans
Wow, thank you Hans ! when setting to 320x240 i can take pictures ! But... I can't take video :'( when i click the "Start recording" button, the window becomes black and Cheese freezes. Please find in attached file the dmesg > log.
Created attachment 157675 [details] dmesg log 1st paril 2010
(In reply to comment #44) > Wow, thank you Hans ! when setting to 320x240 i can take pictures ! > But... I can't take video :'( when i click the "Start recording" button, the > window becomes black and Cheese freezes. > To be clear, so you do see a moving picture when selecting 320x240 and you can take pictures, but things stop working when you press start record ? That would be a gstreamer or cheese issue most likely. > Please find in attached file the dmesg > log. Thanks, so your camera has a zc3xx bridge + pas202b sensor. I just plugged in a labtec camera with the same combo (I have too many webcams) and it works fine on my system including in 640x480, but recently some fixes were done to the driver for exact this combo (zc3xx + pas202b + 640x480). Perhaps you can try upgrading to the latest version of gspca: <install mercurial> hg clone http://linuxtv.org/hg/v4l-dvb/ cd v4l-dvb make menuconfig <unselect the old zc0301 driver> <exit> make sudo make install <reboot, yes really> And see if that helps ? Note this will replace the v4l / dvb subsystem of your kernel with the latest, but it won't touch the rest of your kernel.
>To be clear, so you do see a moving picture when selecting 320x240 and you can > take pictures, Exactly. > but things stop working when you press start record ? No, I mistook. Indeed when I press "Start recording", one image (from the webcam) appear (it is yellowish). Then that is when I press "Stop recording" that the window becomes black and Cheese freezes. I will try to upgrade gspca. But before this, I would like to point out the log I have when launching Cheese via the terminal (you can see Cheese created a blank video before crashing, and that I have a repeting libv4lconvert error), see below: $ cheese ** Message: Error: Stream contains no data. gsttypefindelement.c(939): gst_type_find_element_activate (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstTypeFindElement:typefind: Can't typefind empty stream totem-video-thumbnailer couldn't open file 'file:///home/yyy/Vid%C3%A9os/Webcam/2010-04-01-203710.ogv' Reason: Stream contains no data.. ** (cheese:10043): WARNING **: could not generate thumbnail for /home/yyy/Vidéos/Webcam/2010-04-01-203710.ogv (video/ogg) libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffd9 libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000fff6 libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff ... and so on
(In reply to comment #47) <snip> > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffd9 > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000fff6 > libv4lconvert: Error decompressing JPEG: unknown huffman code: 0000ffff > ... and so on Those messages are fixed in the latest gspca driver.
I tried to upgrade gspca as mentionned in Comment #46 (several errors occured during the compilation, see log), then reboot the pc. Cheese behaves the same as before, and I still have the libv4lconvert messages, so I wonder if I succeded or not to update the driver ?
Created attachment 157704 [details] log driver upgrade April 2
Up. I need help for the compilation, please see the log above.
Yann, I suggest you to just wait for the updated drivers to enter ubuntu repositories. If you still want to manually compile the drivers, look for the proper way to do it in your distribution, the error message is pretty clear, you need some missing package with kernel headers. Closing the bug as NOTGNOME as cheese is obviously not involved (if you have anything wrong with video recording please open another ticket). Feel free to use this bug even if it is closed to let us and Hans know if the new driver actually fixed your issues. Also, feel free to reopen it if anything new comes up that brings back cheese into the game.