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
8
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).

Revision history for this message
Richard Lamont (richard-lamont) wrote :

In dapper I used /dev/raw1394, but with the group set to 'video' in /etc/udev/rules.d/40-40-permissions.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.

Revision history for this message
Dan Dennedy (dan-dennedy) wrote :

Kino's 0.9.0 source release already defaults to /dev/dv1394/0 for some time. See line 188 on this page:

http://kino.cvs.sourceforge.net/kino/kino/src/preferences.cc?revision=1.53&view=markup&pathrev=V_0_9_0

Are you certain you are not seeing your saved preference (~/.kinorc)? If not, then is Debian or Ubuntu appying a patch to mistakenly change the default?

Please do not bother to submit a patch to Kino for anything related to dv1394 because I will not accept it. dv1394 support will soon be removed. dv1394 was written to overcome problems with video1394, but it has been superceded by newer interfaces in raw1394.

"In Ubuntu for many reason, not least security, raw1394 cannot be accessed for normal users...." Yes, security is a problem, and it is being addressed--some draft patches already submitted and discussed pending finalization. However, security is the *only* reason--NOT "for many reason."

Revision history for this message
Richard Lamont (richard-lamont) wrote :

Yes, I think I was seeing the ~/.kinorc preferences. These would have survived a simple dist-upgrade. I've now built a new machine (yesterday) and kino defaults to /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
Przemek K. (azrael)
Changed in kino (Baltix):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.