| Summary: | Webcam Device List Not Accessable | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | BugStalker <spam> |
| Component: | Audio/Video Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | fschaefer.oss, lamarque |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Creative PC-CAM 880 hal configuration
30-syntek_174f_6a51.fdi |
||
|
Description
BugStalker
2008-07-24 02:37:00 UTC
Created attachment 32326 [details]
Creative PC-CAM 880 hal configuration
Hi, I had this same problem with my Creative PC-CAM 880. There is a missing configuration in hal to make it regonize the webcam. Kopete asks solid for available webcams and solid asks the same question to hal, so if hal does not recognize the webcam it will no be available to Kopete. In my case I created the file /etc/hal/fdi/information/30-creative.fdi and restarted hal and Kopete recognized the webcam. The 30-creative.fdi is attached, you must run lshal and find your webcam there and change the info.udi in 30-creative.fdi to match your webcam's.
That .fdi should belongs to the hal-info package. The problem is the video4linux.device key, which is dynamic and will be different from /dev/video0 if there is more than one video device. I think someone will have to create a udev rule to add and remove those .fdi files dynamically. Created attachment 33837 [details]
30-syntek_174f_6a51.fdi
this is for my camera from ASUS S96S 174f:6a51
Kopete uses Solid to detect available video devices. Letting users add device files manually would be a dirty hack which would causes more new problems than it solves (e.g. device removal). If the mentioned device(s) are still not shown (selectable using the popup menu in the video settings dialog) in recent versions of Kopete, please create a bug report for product Solid. Actually it is not a hack, that is the way hald works. That is the only way to add hardware information not provided by the hardware itself to hald and consequently to solid and then to Kopete. The package hal-info I mentioned contains .fdi files to several hardware. Even gphoto used to have its own .fdi file (/usr/share/hal/fdi/information/20thirdparty/10-camera-libgphoto2.fdi) to add info about all cameras it supports. Since hald has been deprecated for years I think no new .fdi file has been added to hal-info, so this problem. In KDE SC 4.6 we have a new udev backend that should provide that information, hopefully we will not need hald and those .fdi files anymore. I have not tested the Solid's udev backend yet, so I cannot say if it really solves this problem. Sure essentially this is a hald/udev problem, not KDE's. Nevertheless the information in this bug entry is usefull for other users understand what is happening. (In reply to comment #5) > Actually it is not a hack, that is the way hald works. That is the only way to > add hardware information not provided by the hardware itself to hald and > consequently to solid and then to Kopete. If applications try to work around bugs in upstream libraries instead of fixing them there, I would call that dirty hacks. Especially when the workarounds introduce new problems... > The package hal-info I mentioned > contains .fdi files to several hardware. Even gphoto used to have its own .fdi > file (/usr/share/hal/fdi/information/20thirdparty/10-camera-libgphoto2.fdi) to > add info about all cameras it supports. Since hald has been deprecated for > years I think no new .fdi file has been added to hal-info, so this problem. Did you try to submit a patch ? HAL is still maintained ! > In KDE SC 4.6 we have a new udev backend that should provide that information, > hopefully we will not need hald and those .fdi files anymore. Hopefully. > Sure essentially this is a hald/udev problem, not KDE's. Nevertheless the > information in this bug entry is usefull for other users understand what is > happening. Definitely, thanks. |