On 04/07/13 12:15, mazzeppanell wrote:
Hi,
i found Ekiga a bit slow at startup. Since this could be a subjective tought, I started
the program in command line with "ekiga -d 3".
Here is an excerpt of what i got in the points with a noticeable time gap:
< ... >
2013/07/04 10:32:28.099 0:00.376 Ekiga Started
STUN detector
2013/07/04 10:32:28.211 0:00.487 StunDetector:0xadabeb40 OPAL STUN server
"stun.ekiga.net" replies Cone NAT, external IP <Public_IP>
2013/07/04 10:32:28.211 0:00.487 StunDetector:0xadabeb40 PTLib Thread ended:
name="StunDetector:0xadabeb40", real=0.111, kernel=0.000 (0%), user=0.000 (0%),
both=0.000 (0%)
2013/07/04 10:32:28.275 0:00.551 PV4L2Plugin
Detecting V4L2 devices
2013/07/04 10:32:28.275 0:00.551 PV4L2Plugin
detected device metadata at /sys/class/video4linux/
< 10 seconds "inactivity/elaboration" as you can see >
2013/07/04 10:32:38.089 0:10.366 Housekeeper:0xadf0cb40 Ekiga Stopped
STUN detector
< 15 seconds "inactivity/elaboration" as you can see >
2013/07/04 10:32:53.370 0:25.647 PV4L2Plugin
Detecting V4L2 devices
2013/07/04 10:32:53.370 0:25.647 PV4L2Plugin
detected device metadata at /sys/class/video4linux/
2013/07/04 10:32:53.445 0:25.722 PV4L2Plugin
Detecting V4L2 devices
2013/07/04 10:32:53.446 0:25.722 PV4L2Plugin
detected device metadata at /sys/class/video4linux/
2013/07/04 10:32:53.460 0:25.737 PV4L2Plugin
Detecting V4L2 devices
2013/07/04 10:32:53.460 0:25.737 PV4L2Plugin
detected device metadata at /sys/class/video4linux/
2013/07/04 10:32:53.595 0:25.872 Ekiga version
4.0.1
< application GUI spawns about at this point >
< ... >
Try using ekiga -d 8 and see if some intermediate lines are written
during inactivity.
About 25 seconds to show the main window. I don't know if this is a normal
behaviour and there are legitimate elaborations going on,
that's why i classified the report as minor bug.
This is not normal. It does not appear here. This sometimes appear
when there are some issues with the DNS and the STUN result, but as
written below the STUN is not the case. I suppose you have restarted
ekiga after disabling network detection, right?
P.S. I tried a quick installation on two virtual machines (an ubuntu one and a
windows one, both with nat networking) and it seems not to stuck.
Because of the slowdown near STUN operations and video device detection, i tried
unchecking "Enable network detection" in Ekiga settings,
but this changed nothing; also could be relevant that there is no webcam
detected in virtual machines, so maybe it skips some operations.
Another idea is to look with wireshark at second 10 and 25 what packets
you receive. If it is DNS response, then it would confirm my hypothesis
about DNS exchange taking so long. Alternatively, you can try another
DNS server (in /etc/resolv.conf), e.g. someone wrote on our mailing list:
"I had a similar problem with dns servers where the isp provider didn't
have a good dns server and I had many delays on the connections.
I use the dns from opendns.com and I have no problem anymore..."
--
Eugen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
