Re: [Linphone-users] (alsa-related) crashes on linux

[Alastair Johnson]

My guess is AppArmor is blocking access to the port. I don't know how clear 
ubuntu makes access control violations, but if it's like fedora's early use of 
SElinux it may be far from obvious.

On Friday 01 April 2011, Dragos D wrote:
> Hi Simon,
> 
> I did not experience this, but apparently the port binding happens
> when no other program is using port 5060. One user said that
> netstat -ltupn | grep 5060
> did not report any other program using the port. I don't have an
> explanation for it...
> Dragos
> 
> On Fri, Apr 1, 2011 at 11:57 AM, Simon Morlat <address@hidden> 
wrote:
> > Hi Liviu,
> > 
> > Not related to alsa at all, but the bad consequence of this:
> > linphone-error : eXosip: Cannot bind socket node:0.0.0.0 family:2
> > Address already in use
> > linphone-error : eXosip: Cannot bind on port: 5060
> > 
> > Apparently another program is using port 5060.
> > However it should not crash so I'm fixing for this part.
> > 
> > Simon
> > 
> > Le mardi 29 mars 2011 à 11:50 +0200, Liviu Andronic a écrit :
> >> On Tue, 29 Mar 2011 11:40:12 +0200, Liviu Andronic <address@hidden>
> >> 
> >> wrote:
> >> > If I'm starting with a clean profile it generates the same pop-up
> >> > message (see attached shot), but doesn't crash (see second log).
> >> 
> >> address@hidden:~$ linphone --verbose &> /tmp/linphone1.log
> >> 
> >> I forgot the --verbose argument. Here's a new log when using a clean
> >> profile and there's no crash.
> >> Liviu