17 Jan 2008 19:54
Re: kino 1.2.0 seg fault
Jim Nanney <jnanney <at> gmail.com>
2008-01-17 18:54:11 GMT
2008-01-17 18:54:11 GMT
Jarod Wilson wrote: |> [root <at> rama ~] |> $ dvgrab -d 10 |> Found AV/C device with GUID 0x08004601036b44b9 |> Capture Started |> "dvgrab-005.avi": 16.93 MB 119 frames timecode 00:03:45.22 date |> 2007.12.16 13:13:41 |> Capture Stopped |> |> and after removing ~/.kinorc and ~./kino-history (because it still |> crashed ...) now capture works fine in kino. |> Very good . next step , I'll have to burn that capture to a DVD .... |> thanks for your help all . | | Huh, interesting. So it would seem perhaps the dvgrab 2.1 segfault was indeed | leaving things a bit of a mess, which then caused problems for kino (which Dan | suggested was a possibility, iirc). Glad to hear you've got it working | smoothly now! | Just tried it with mine, still segfaults even when removing .kinorc dvgrab 3.0 still captures fine though.
.
|> Very good . next step , I'll have to burn that capture to a DVD ....
|> thanks for your help all .
|
| Huh, interesting. So it would seem perhaps the dvgrab 2.1 segfault was
indeed
| leaving things a bit of a mess, which then caused problems for kino
(which Dan
| suggested was a possibility, iirc). Glad to hear you've got it working
| smoothly now!
|
Just tried it with mine, still segfaults even when removing .kinorc
dvgrab 3.0 still captures fine though.
RSS Feed