> I have fixed some of your problem already in CVS - at least for Qt2.3.2
>
> Ok, I might have to install and use an even older Qt to be on the safe side.
>
> Kabi: how low should I go?
I've been keep 2.0 compatibility.
This version comes with Debian Potato - but of course in this version
the GUI locked much uglier compared with the current Keramic style :)
>
> > The segfault appeared when I was exiting the avicap program, so this seems
> > to be some kind of synchronization problem.
>
> Any other ideas what might have caused the segfault, did you anything
> different from what you done usually?
Hmm I think I've also caused the segfault by quiting avicap without
stopping recorfing first - it will be some mess in destructors.
It'll have to be checked.
> I should have disabled that before the release, my fault.
>
No need - as long as it's clearly new feature which doesn't
influence anything else it might stay there - this is not pay-supported
support - so not everything must be perfect right after the first commit :)
> Cause, if you are an avicap/avirec user, I'd like you to help us with
> developing, downloading the newest CVS and see if it still compiles and runs
> etc
If someone wants to help with bug fixing and is skilled enough -
he may try to get a ssh account on SF
--
.''`.
: :' : Zdenek Kabelac [EMAIL PROTECTED], users.sf.net, fi.muni.cz}
`. `' Debian GNU/Linux maintainer - www.debian.{org,cz}
`-
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
