No, it is not an kernel issue. I installed the same kernel as on the machine where it works, still the same problem. On these two machines, I am now using the same: kernel (2.6.23.1-42.fc8, incl. -devel,-headers) webcam (Labtec Webcam Pro, physically the same) webcam driver (gspca-20071224) ekiga (3.0.1 from source with the same configuration) x264,ffmpeg (ffmpeg-0.4.9-0.42.20071121.lvn8, x264-0-0.10.20070819.lvn8, incl. -devel) Yet I still H264 works on one computer and does not on the other one.
What else could be the trigger??? Palo ----- Originálna Správa ----- Od: Palo S. Komu: Poslaná: 27.10.2008 21:47 Predmet: Re: [Ekiga-list] [Fwd: AW: [Fwd: h264 bug]] > > Hi Matthias, > > thanks for the message! It can easily be a kernel > issue since the computer on which it works is > running a different kernel from the other two: > it works under 2.6.23.1-42.fc8.i686 and does not > work under 2.6.25.6-55.fc9.i686 (I don\\\'t have > access to the second computer that suffered by > the problem at the moment but it runs F9 with > either 2.6.25 or 2.6.24). > > However it does not seem that AppArmor patches > could be on blame since both suffering machines > are stock Fedora kernels and I doubt that these > come with any AppArmor patches. SELinux is > disabled on all these machines. > > I\\\'ll try to confirm whether it is a kernel issue > and if so to narrow it down, I will post my > findings here soon! > > Palo > > > > ----- Originálna Správa ----- > Od: Damien Sandras > Komu: \\\"Palo S.\\\" > Poslaná: 27.10.2008 09:26 > Predmet: [Fwd: AW: [Fwd: [Ekiga-list] h264 bug]] > > > > > -- > > _ Damien Sandras > > (o- > > //\\\\ Ekiga Softphone : http://www.ekiga.org/ > > v_/_ Be IP : http://www.beip.be/ > > FOSDEM : http://www.fosdem.org/ > > SIP Phone : sip:[EMAIL PROTECTED] > > > > > > > > > > > > --- Begin of attached message --- > > > > From: Matthias Schneider > > To: Damien Sandras > > Date: 2008-10-27 08:36:12 > > > > If you can forward to Palo S. (I just subscribed to user ML) > > > > Hi Palo, > > > > this issue has been reported by another person as well, > > and it seems to be an issue of some kernel modifications. > > It is suspected (although not yet proben) that AppArmor > > patches to the kernel are responsible for this behaviour > > (I suspect a bug there). > > So it would be interesting to know what kind of kernel you > > are using on the setups that do produce the error and on the > > system where it works. > > > > Matthias > > > > > > > > > > --- End of attached message --- > > > > > > > __________ > http://cestovanie.sme.sk/ - Celý svet na vašom monitore > > > _______________________________________________ > ekiga-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/ekiga-list > __________ Najpopulárnejší blog na Slovensku - http://blog.sme.sk/ _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
