GNOME Bugzilla – Bug 523435
Logitech Quickcam Messenger doesn't work
Last modified: 2008-08-07 12:26:31 UTC
I'm using Ubuntu 8.04 and I've compiled the qc-usb-messenger-1.7 driver for my Logitech Quickcam Messenger. I'm using Linux kernel 2.6.24 compiled by myself, not the Ubuntu one. The webcam works with gstreamer-properties (v4lsrc device="/dev/video"), camorama, ekiga and xawtv, but not with cheese (neither 2.21.5 nor 2.22). I'm not sure whether this is a Cheese bug. Any idea?
does it also work with gst-launch v4lsrc ! ffmpegcolorspace ! ximagesink could you paste the cheese -v output?
Yes, it works with gst-launch v4lsrc ! ffmpegcolorspace ! ximagesink . There is no output when I run cheese -v from a terminal.
could you try with cheese 2.22.1?
It doesn't work with 2.22.1 .
*** Bug 527111 has been marked as a duplicate of this bug. ***
I have the same problem with Jaime Frutos Morales. > There is no output when I run cheese -v from a terminal. Try "cheese --verbose" instead. I believe that even though I make all the required changes via gstreamer-properties to set my Logitech QuickCam Messenger as the default video input device, Cheese somehow bypasses that setting and uses another input (a PCI TV tuner card which I haven’t configured yet in my box). The reason I suspect this is that my webcam is at /dev/video1 and the "cheese --verbose" command gives: Detected webcam: AverTV Studio 303 (M126) . . . (Lots of numbers etc.) . . . device: /dev/vbi0 device: /dev/radio0 v4l2src name=video_source device=/dev/video0 ! video/x-raw-yuv,width=768,height=576,framerate=30/1 ! identity I’m using Ubuntu 8.04, with Cheese and everything else downloaded via the Synaptic Package Manager.
I have a Quickcam IM and I'm having the same kinds of issues listed here. When I run "cheese --verbose" I get this as the output: Detected webcam: Logitech QuickCam IM device: /dev/video0 video/x-raw-yuv 160 x 120 num_framerates 1 25/1 video/x-raw-yuv 320 x 240 num_framerates 1 25/1 video/x-raw-yuv 640 x 480 num_framerates 1 25/1 video/x-raw-yuv 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 640 x 480 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 640 x 480 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 640 x 480 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 v4lsrc name=video_source device=/dev/video0 ! video/x-raw-yuv,width=640,height=480,framerate=25/1 ! identity Cheese doesn't do anything after that. Trying to exit cheese locks up the program. I have to force quit the application. My webcam works just fine when testing it using gstreamer-properties and gst-launch v4lsrc ! ffmpegcolorspace ! ximagesink
I have the same problem with 2.22.1 except that the phenomenology is different. I'm on Ubuntu 8.04. The cam (Quickcam Messenger using the in-kernel driver) works in gstreamer-properties and gst-launch. Running cheese --verbose produces NO terminal output. Cheese does not appear to detect the cam at all.
I got same thing. In my case (Logitech Quickcam Express), hal does not advertise the device as "video4linux" so no device is found.
I have the same issue with my Logitech Quickcam Express using the 1.8 driver from <http://home.mag.cx/messenger/>. The camera works fine with `camorama` and `gst-launch v4lsrc ! ffmpegcolorspace`. I get no output from `cheese -v` or `cheese --verbose` and Cheese simply shows the test video.
If hal doesn't advertise the device as "video4linux" (as for the Logitech Quickcam Express) we won't find the device and cheese won't work. I think you should file a bug against hal for that
I just thought of a way to fix this. If we don't find any devices in HAL we might want to just try v4l2src and v4lsrc to see if we get an image. I'll look into a patch
*** This bug has been marked as a duplicate of 531835 ***