Re: Kino Crashes Opening Files

dhk <[email protected]>
Newsgroups gmane.comp.video.kino.devel
Message-ID <[email protected]>
Stefan Richter wrote:
>> On Wed, May 13, 2009 at 4:54 AM, dhk <[email protected]> wrote:
>>> I think the problem is in the environment or setup somewhere.  I 
>>> don't have
>>> the answer, but I think I'm getting closer.  So please bear with me as I
>>> explain.
>>>
>>> First)  This is kino version 1.3.1 I'm working with.  There isn't any
>>> libavcodec package in the portage tree as far as I've seen, but there 
>>> is a
>>> libavc1394 version 0.5.3. The highest version of lbdv is 1.0.0-r2.
> 
> $ equery b libavcodec
> [ Searching for file(s) libavcodec in *... ]
> media-video/ffmpeg-0.4.9_p20090201 (/usr/include/libavcodec)
> 
> equery is provided by the gentoolkit package.
> 
> Opening files works for me here on an amd64 Gentoo box.
> 
> [But capturing doesn't work for me; Gentoo's kino-1.3.1 and -1.3.3 as 
> well as dvgrab-3.4 stop early after one frame or a few frames; 
> dvgrab-3.1 works though.  I still need to check what's going on --- this 
> is a newly set-up amd64 box replacing a dead i586 one.  I now noticed 
> that my older secondary Gentoo amd64 box misbehaves the same; apparently 
> I never tried capturing in Kino on that PC and only rarely with dvgrab. 
> Eventually I'll reinstall the secondary PC as an i586 system for test 
> purposes...]

With some help from the Gentoo group, I found the problem.  Version 
1.3.3 was masked.  I had to add media-video/kino ~amd64 to the 
package.keywords file.  Now the problem is gone.  Thanks all.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.