Le mardi 05 janvier 2010 à 15:55 +1000, bnc a écrit :
I always change the port too.
I normally go into gconf-editor and set the port to 5066.
When starting ekiga it still uses port 5060.
It then seems to allocate the next port up everytime it reregisters.
Now if you have a limited number of
Le mardi 05 janvier 2010 à 07:50 +, Dave Higton a écrit :
OK... let me see, there isn't a newer packaged version for Fedora 10,
is there? So it's a build-it-myself job?
I suspect that, at least with the version I'm currently running, it
wasn't designed (or tested) to run without an
Yannick wrote:
Le vendredi 01 janvier 2010 à 00:49 +0100, Damien Sandras a écrit :
Happy New Year to everyone !
Let all your dreams come true...
Happy new year folks!
Carpe diem quam minimum credula postero
Happy New Year! Let's have a better year than 2009!
--
Eugen
Okay, so first I'd like to say thank you for everything. I'm a little
further out of the water but I was wondering what this means:
[jetblackbivo...@localhost ~]$ pasuspender ekiga
ALSA lib conf.c:976:(parse_value) default is not a string
ALSA lib conf.c:1589:(snd_config_load1)
Hi,
One of the answers on this topic said that you had to use pasuspender,
and make some changes to alsa configuration files. the changes required
are non trivial.
Some people claim the changes are easy - just paste in these couple of
lines they say. Those people were lucky. Other
Derek,
pulse isn't right anywhere and the only the the pulse devs says is it's
the applications fault Which I would say OK to except it's ALL the
applications. That answer points to lousy devs who refuse to accept
that they've made an error
Bruce
P.S.
We've had this discussion before
Bruce,
Like you I tried pulse a while back and eventually deleted it so I
could get some sound to work.
With Suse 11,2 however it now works, including my Bluetooth
headset(this enables me to make calls via ekiga and leave my notebook on
the bench) 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15
