After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 563807 - my webcam is recognized by gstreamer, camorama, ekiga, etc., but not by cheese
my webcam is recognized by gstreamer, camorama, ekiga, etc., but not by cheese
Status: RESOLVED NOTGNOME
Product: cheese
Classification: Applications
Component: general
2.24.x
Other All
: Normal normal
: 2.24
Assigned To: Cheese Maintainer(s)
Cheese Maintainer(s)
: 568234 598112 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-09 04:57 UTC by jaywalkie
Modified: 2009-10-24 07:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description jaywalkie 2008-12-09 04:57:17 UTC 
Please describe the problem:
Cheese cannot use my webcam (syntek USB video camera, on Asus F3Sv laptop). gstreamer-properties command finds the Default Input and its picture quality is actually quite good, when I click on Test button. However, the Default output doesn't seem to work no matter what i do, and cheese output looks like exactly that: the test of default output, not the test of default input...

Steps to reproduce:
1. Open Cheese
2. It displays an error message: "No camera found!"
3. that's about it...


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Let me know if you need further information. Just email me at jaywalkie@yahoo.com
Comment 1 Filippo Argiolas 2008-12-09 07:54:57 UTC 
Hi, thanks for taking time to report this bug.
It seems that your driver, which I guess is stk11xx, doesn't correctly set the parent field of the videodev structure. This causes HAL to not be able to detect your device as a video4linux one and since we use HAL for device probing we don't get any device.
You should report the issue to your driver maintainers, if my guess is correct they have a project page at http://sourceforge.net/projects/syntekdriver/
It should be a pretty easy fix, something like
-	dev->vdev->dev = &dev->interface->dev;
+	dev->vdev->parent = &dev->interface->dev;

Feel free to point them to this bug report and let us know if they manage to fix it.
Comment 2 jaywalkie 2008-12-09 11:57:49 UTC 
Your guess about the driver being (stk11xx) is correct. I'll let them know about your suggestion.
Thank you.
Comment 3 jaywalkie 2008-12-09 12:14:00 UTC 
By the way, I did those changes myself, and it worked :) Thank you very much! I hope the developer of the driver will pay attention.
Thanks again!
Comment 4 Filippo Argiolas 2008-12-10 14:36:26 UTC 
(In reply to comment #3)
> By the way, I did those changes myself, and it worked :) Thank you very much! I
> hope the developer of the driver will pay attention.
> Thanks again!
> 

Great, you're welcome! I'm glad to hear it, so my guess was correct, now let's wait the developer to acknowledge it and fix it :)
Comment 5 Filippo Argiolas 2009-01-19 08:02:28 UTC 
*** Bug 568234 has been marked as a duplicate of this bug. ***
Comment 6 Filippo Argiolas 2009-10-24 07:08:19 UTC 
*** Bug 598112 has been marked as a duplicate of this bug. ***