ekiga not "normal" in Juanty and Debian Testing

[H.S.]

Hello,

I have Ekiga in Debian Testing as well as on Jaunty machines. Debian got
the new version only a few months ago. I have noticed two main things:
1. During a call, Ekiga appears to hog the CPU (40%~70%). I already
reported this here some weeks ago (so let's just keep this in that
thread only and focus on the following point here).
2. After ending a call and trying more calls is problematic. Or perhaps
it is the length of time that Ekiga has been running. But after some
time, the remote user is usually reported to be not available and I
cannot make further calls.

Anyone else having these problems?
I have, on Debian: Ekiga 3.2.1~git20090515.9d0263-1
and on Juanty: Ekiga 3.2.0-0ubuntu2

Thanks and regards,
->HS
--

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.

_______________________________________________
ekiga-list mailing list
ekiga-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Eugen Dedu]

H.S. wrote:
> Hello,
>
> I have Ekiga in Debian Testing as well as on Jaunty machines. Debian got
> the new version only a few months ago. I have noticed two main things:
> 1. During a call, Ekiga appears to hog the CPU (40%~70%). I already
> reported this here some weeks ago (so let's just keep this in that
> thread only and focus on the following point here).

I 2 days the 3.2.5 ekiga should be available in unstable.  Please test
with this one and tell if the CPU is high.  If yes, we will fix it for
3.2.6.

> 2. After ending a call and trying more calls is problematic. Or perhaps
> it is the length of time that Ekiga has been running. But after some
> time, the remote user is usually reported to be not available and I
> cannot make further calls.

This also is interesting.  The -d 4 output is precious, please give it
to us.

> Anyone else having these problems?
> I have, on Debian: Ekiga 3.2.1~git20090515.9d0263-1
> and on Juanty: Ekiga 3.2.0-0ubuntu2

--
Eugen
_______________________________________________
ekiga-list mailing list
ekiga-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-list

[H.S.]

Eugen Dedu wrote:

> H.S. wrote:
>> Hello,
>>
>> I have Ekiga in Debian Testing as well as on Jaunty machines. Debian got
>> the new version only a few months ago. I have noticed two main things:
>> 1. During a call, Ekiga appears to hog the CPU (40%~70%). I already
>> reported this here some weeks ago (so let's just keep this in that
>> thread only and focus on the following point here).
>
> I 2 days the 3.2.5 ekiga should be available in unstable.  Please test
> with this one and tell if the CPU is high.  If yes, we will fix it for
> 3.2.6.

Wonderful!


>
>> 2. After ending a call and trying more calls is problematic. Or perhaps
>> it is the length of time that Ekiga has been running. But after some
>> time, the remote user is usually reported to be not available and I
>> cannot make further calls.
>
> This also is interesting.  The -d 4 output is precious, please give it
> to us.

Okay. I will start ekiga with -d 4 now and will report when my remote
user is available and we try to talk.

Thanks,
regards.





--

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.

_______________________________________________
ekiga-list mailing list
ekiga-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-list

[H.S.]

Eugen Dedu wrote:

> H.S. wrote:
>> Hello,
>>
>> I have Ekiga in Debian Testing as well as on Jaunty machines. Debian got
>> the new version only a few months ago. I have noticed two main things:
>> 1. During a call, Ekiga appears to hog the CPU (40%~70%). I already
>> reported this here some weeks ago (so let's just keep this in that
>> thread only and focus on the following point here).
>
> I 2 days the 3.2.5 ekiga should be available in unstable.  Please test
> with this one and tell if the CPU is high.  If yes, we will fix it for
> 3.2.6.
>
>> 2. After ending a call and trying more calls is problematic. Or perhaps
>> it is the length of time that Ekiga has been running. But after some
>> time, the remote user is usually reported to be not available and I
>> cannot make further calls.
>
> This also is interesting.  The -d 4 output is precious, please give it
> to us.

Unfortunately, the remote user was not at the computer for this
experiment. However, when I tried to call him anyway, I got a message in
-d 4 output that the remote user was temporarily unavailable.

I will try this again tomorrow when I get a chance (and I will save the
-d 4 output to a file, which I forgot to do this time).

regards.




--

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.

_______________________________________________
ekiga-list mailing list
ekiga-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Detlef Lechner-2]

On Thu, 2009-07-09 at 12:08 -0400, H.S. wrote:


> 1. During a call, Ekiga appears to hog the CPU (40%~70%).

I noticed the same phenomenon.
 See
https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/395594/?loggingout=1


Regards,

Detlef Lechner

_______________________________________________
ekiga-list mailing list
ekiga-list@...
http://mail.gnome.org/mailman/listinfo/ekiga-list