Kino (0.9.2) Dapper backport defaults to use /dev/dv1394/0 but Ubuntu Dapper uses /dev/dv1394-0
Bug #67818 reported by
Duncan Lithgow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kino (Baltix) |
Invalid
|
Medium
|
Mantas Kriaučiūnas | ||
kino (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kino
This is a configuration and usability bug, not a functional bug.
Kino (0.9.2) Dapper backport defaults to use /dev/dv1394/0 should default to use /dev/dv1394-0 as there are no /dev/dv1394/0 in Ubuntu 6.06 (Dapper). If any was feeling really helpful they could submit a patch to kino which would search for the presence of /dev/dv1394/0 (/dev/dv1394-0).
Changed in kino: | |
status: | Unconfirmed → Rejected |
status: | Unconfirmed → Rejected |
description: | updated |
Changed in kino: | |
assignee: | nobody → mantas |
importance: | Undecided → Medium |
status: | Rejected → Confirmed |
Changed in kino (Baltix): | |
status: | Confirmed → Invalid |
To post a comment you must log in.
In dapper I used /dev/raw1394, but with the group set to 'video' in /etc/udev/ rules.d/ 40-40-permissio ns.rules . (I don't use firewire for anything else.)
After a dist-upgrade to edgy, kino's capture no longer worked. (Oddly, dvgrab did.) Changing the device used by kino (Edit -> Preferences -> IEE 1394) from /dev/raw1394 to /dev/dv1394/0 solved the problem. The camera controls work OK. I think it's the old video1394 interface that had problems with dv cameras, and the dv1394 interface was written to solve them, AIUI.