Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off

2008-12-03 Thread Michael Ashley
Hi Matthias,

Thank you for investigating this issue further.

Yes, I could compile ekiga from sources. I did this earlier with
3.0.1. It took me a while to track down all the needed libraries, but
I eventually made a working version.

Regards, Michael

On Wed, Dec 03, 2008 at 07:27:29AM +, Matthias Schneider wrote:
> Hi Michael, 
> 
> I have been trying to reproduce your issue but still no "luck". I enabled my 
> camera,
> closed the call panel, left ekiga, unplugged the cam and restarted ekiga - 
> still no 100% CPU.
> Probably it seems this issue only appears with certain display drivers and/or 
> camera drivers? 
> Maybe we will have to run an instrumented version on your PC. Do you think 
> you could compile
> ekiga from the sources?
> 
> Matthias
> 
> 
> 
> - Ursprüngliche Mail 
> > Von: Michael Ashley <[EMAIL PROTECTED]>
> > An: Ekiga mailing list 
> > Gesendet: Mittwoch, den 26. November 2008, 22:28:44 Uhr
> > Betreff: Re: [Ekiga-list] ekiga pegs the CPU if started with the camera 
> > device turned off
> > 
> > Damien,
> > 
> > > If there is no debug output, do you also reach 50% CPU in the same
> > > situation ?
> > 
> > Yes. The CPU usage isn't just due to the last number of debug
> > messages.
> > 
> > In fact, I see ekiga and Xorg together using up about 100% of the
> > CPU. The proportion used by each varies a little bit depending on
> > whether the debug output is on.
> > 
> > Regards, Michael
> > ___
> > ekiga-list mailing list
> > ekiga-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/ekiga-list
> 
> 
> 
>   
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off

2008-11-26 Thread Michael Ashley
Damien,

> If there is no debug output, do you also reach 50% CPU in the same
> situation ?

Yes. The CPU usage isn't just due to the last number of debug
messages.

In fact, I see ekiga and Xorg together using up about 100% of the
CPU. The proportion used by each varies a little bit depending on
whether the debug output is on.

Regards, Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off

2008-11-26 Thread Michael Ashley
Hi Mathias,

> Hmm, you turn off the camera? 

Yes.

> Does this mean that the opening of the
> camera will fail ( do you get a window?)

Yes, it fails.  I get a popup that says "Error while accessing video
device GNF7129".

> and the moving logo will be
> displayed? What do you see when you open the call widget?

I get the moving logo, and the CPU goes down to less than a few
percent (and stays that way even if I now close the call widget).

Regards, Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off

2008-11-25 Thread Michael Ashley
Hi Matthias,

> the debug output is perfectly normal behaviour.  It is displayed on 
> each frame that cannot be displayed  because there is no widget to 
> show.

I don't know the details of the code, but one wonders whether it is 
necessary to poll 30 times a second.

> However 50% CPU is not. Actually I cannot reproduce this,
> when I have the widget unrealized and am getting this trace output, 
> all I get is CPU load of 1-2%... 
> Is there anything special you do? Just preview and deactivated call view?

The eee PC 901 has an inbuilt camera that can be deactivated to save 
power. If I turn off the camera, and then start ekiga, the CPU load 
stays at 50% until the call view panel is displayed.

Actually I just did some more tests and it isn't quite that simple! I 
only get the CPU problem if, in a previous invocation of ekiga I was 
displaying images from the camera. If I then deactivate the call 
view frame, exit ekiga, turn off the camera, and restart ekiga, _then_ 
I see the 30 errors/second and 50% CPU.

Regards, Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] ekiga pegs the CPU if started with the camera device turned off

2008-11-24 Thread Michael Ashley
A bug report:

With ekiga 3.0.0 SNV on Ubuntu 8.04 on an eee PC 901 I find that ekiga
uses about 50% of the CPU continuously if started with the camera
turned off. It repeats the following message every 30 milliseconds or
so:

2008/11/25 09:01:37.588   0:15.953  GMVideoOut...0xb5319b90 
GMVideoOutputManager_X  Widget not yet realized or gconf info not yet set, not 
opening display

The CPU usage returns to normal if one selects View->Show Call Panel.

Regards, Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga: could not set TOS field in IP header

2008-11-24 Thread Michael Ashley
Damien,

Thank you for your rapid reply.

> The fact that you can (or can not) set the TOS field should have no
> influence on the result of the echo test. It is certainly not mandatory
> to have the TOS field set to be able to make a call.

You are right (of course). Further investigation at debug level 4
showed that the real problem was a "488 Not acceptable here" reply to
a "100 Giving a try" request. 

I fixed this by enabling all the audio codecs (for some reason I had a
different set of codecs enabled when I tried ekiga as root).

Regards,
Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] ekiga: could not set TOS field in IP header

2008-11-23 Thread Michael Ashley
Hi folks,

With ekiga-snapshot (ekiga 3.0.0 SVN) on Ubuntu 8.04 I find that ekiga
can register OK, but when I try the echo test I receive the following
message (at debug level 1):

dialer:0xb523db90 RTP_UDP Session 1, could not set TOS field in IP
header: Operation not permitted.

My understanding is that I need the CAP_NET_ADMIN capability to set
TOS, but beats me how to obtain that capability, or why no one else on
the planet seems to have come across this problem.

This issue is possibly related to my earlier attempt to compile and run
ekiga 3.0.1 from sources.

If I run ekiga as root, the echo test succeeds.

Regards,
Michael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list