RE: [GnomeMeeting-list] "Abnormal call termination"



On Wed, 2006-05-17 at 13:32 +0800, Stefan Brüns wrote:
>  
> > -----Original Message-----
> > From: gnomemeeting-list-bounces gnome org 
> > [mailto:gnomemeeting-list-bounces gnome org] On Behalf Of 
> > Damien Sandras
> > Sent: Wednesday, 17 May 2006 1:13 AM
> > To: GnomeMeeting mailing list
> > Subject: Re: [GnomeMeeting-list] "Abnormal call termination"
> > 
> > Le mardi 16 mai 2006 à 18:44 +0200, Josh Green a écrit :
> > > On Tue, 2006-05-16 at 15:19 +0200, Damien Sandras wrote:
> > > > 
> > > > The debug output you sent is not valid. It doesn't give 
> > any details. I
> > > > know it is a bug of Gentoo, but I do not know how it can be fixed.
> > > 
> > > Thanks for the reply.  It makes sense that there is 
> > something wrong with
> > > the debugging output, since it was rather sparse.
> > > 
> > > How is the debugging output normally enabled?  Is it controlled via
> > > a ./configure flag or some other method?  I tried enabling 
> > the Gentoo
> > > "debug" USE flag, but it still did not improve the debug output.  So
> > > however the debug output is enabled is not being done by the current
> > > Gentoo ebuild.  I would look into fixing this if I knew how 
> > to enable
> > > this option.  Perhaps its a flag given to one of Ekiga's 
> > dependencies?
> > 
> > It is enabled with standard build without specific flag.
> > So gentoo is doing something "non-standard", but I have no idea what.
> 
> It seems they use NOTRACE in opal , which effectively disables any
> debuggig/tracing code.
> 
> <rant>
> What do they thing this code is for? Yeah, gentoo is 1% smaller, 1% faster,
> and 100% unusable ...
> </rant>
> 
> Lurchi
> 

Thanks for the info.  I wouldn't be too hard on Gentoo though, its 100%
unusable for those who configure it wrong ;)  Its only a matter of
adding a USE flag for the Opal ebuild.  Which can be done like so (for
those interested):
echo "net-libs/opal debug" >>/etc/portage/package.use

Now that I got some useful debug output, I found a thread which sounds
like the exact same issue.  I am also getting a massive amount of
messages like:
"RTP	STUN could not create socket pair"

The thread for reference:
http://mail.gnome.org/archives/gnomemeeting-devel-list/2006-March/msg00004.html

So I think its a problem with the NAT router I'm using and the STUN
implementation.  I'll try setting a different RTP port range using
gconf, like one reply to that thread suggests.

For reference, the router is a D-Link DI-824VUP+ and I'm connecting to
it wirelessly with my laptop.

Thanks for all the replies.  Very helpful.
	Josh Green





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]