[Ekiga-devel-list] Segmentation fault when caller clears the call
I've had this issue since I moved to 3.0.1 I am on Fedora 9. Someone calls (in this case I call via a real phone) and I cancel the call before answering. The it crashes always. I've used only SILENT and LOGO as devices (just to be sure it is not a Pulseaudio or Alsa issue). The SIP server is messagenet. I've attached the output of ekiga -d 4 Program received signal SIGSEGV, Segmentation fault. 0x4eab08d2 in g_type_check_instance_cast () from /lib/libgobject-2.0.so.0 Thread 17 (Thread 0xb6e33b90 (LWP 5452)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00ad9ba5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x4ec937d3 in PSyncPoint::Wait (this=value optimized out) at ptlib/unix/tlibthrd.cxx:1419 #3 0x4f496a06 in SIPEndPoint::SIP_PDU_Thread::Main (this=value optimized out) at /usr/src/debug/opal-3.4.2/src/sip/sipep.cxx:1299 #4 0x4ec982d8 in PThread::PX_ThreadStart (arg=value optimized out) at ptlib/unix/tlibthrd.cxx:806 #5 0x00ad632f in start_thread () from /lib/libpthread.so.0 #6 0x00a1120e in clone () from /lib/libc.so.6 Thread 15 (Thread 0xb6e74b90 (LWP 5450)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00a09671 in select () from /lib/libc.so.6 #2 0x4ec951d8 in PThread::PXBlockOnIO (this=value optimized out, handle=value optimized out, type=value optimized out, timeout=value optimized out) at ptlib/unix/tlibthrd.cxx:903 #3 0x4ec8a302 in PChannel::PXSetIOBlock (this=value optimized out, type=value optimized out, timeout=value optimized out) at ptlib/unix/channel.cxx:119 #4 0x4ec872ec in PSocket::os_accept (this=value optimized out, listener=value optimized out, addr=Could not find the frame base for PSocket::os_accept(PSocket, sockaddr*, int*). ) at ptlib/unix/socket.cxx:206 #5 0x4ecad50a in PTCPSocket::Accept (this=value optimized out, socket=value optimized out) at ptlib/common/sockets.cxx:2263 #6 0x4f0a16ab in OpalListenerTCP::Accept (this=value optimized out, timeout=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:613 #7 0x4f09f796 in OpalListener::ListenForConnections (this=value optimized out, thread=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:448 #8 0x4f0a1a22 in OpalListener::ListenForConnections_PNotifier::Call (this=Could not find the frame base for OpalListener::ListenForConnections_PNotifier::Call(PObject, int) const. ) at /usr/src/debug/opal-3.4.2/include/opal/transports.h:350 #9 0x08107667 in PNotifier::operator() (this=0x9fb6cac, notifi...@0x9fb6c28, extra=0) at /usr/include/ptlib/notifier.h:95 #10 0x4ecbb278 in PSimpleThread::Main (this=Could not find the frame base for PSimpleThread::Main(). ) at ptlib/common/osutils.cxx:1971 #11 0x4ec982d8 in PThread::PX_ThreadStart (arg=value optimized out) at ptlib/unix/tlibthrd.cxx:806 #12 0x00ad632f in start_thread () from /lib/libpthread.so.0 #13 0x00a1120e in clone () from /lib/libc.so.6 Thread 14 (Thread 0xb6ebcb90 (LWP 5449)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00a09671 in select () from /lib/libc.so.6 #2 0x4ec87073 in PSocket::Select (read=value optimized out, write=value optimized out, except=value optimized out, timeout=value optimized out) at ptlib/unix/socket.cxx:328 #3 0x4ecae82e in PSocket::Select (read=value optimized out, timeout=value optimized out) at ptlib/common/sockets.cxx:1037 #4 0x4ecb6f5a in PMonitoredSockets::ReadFromSocket (this=value optimized out, readers=value optimized out, socket=value optimized out, buf=value optimized out, len=value optimized out, addr=value optimized out, port=value optimized out, lastReadCount=value optimized out, timeout=value optimized out) at ptclib/psockbun.cxx:577 #5 0x4ecb752d in PMonitoredSocketBundle::ReadFromBundle (this=value optimized out, buf=value optimized out, len=value optimized out, addr=value optimized out, port=value optimized out, iface=value optimized out, lastReadCount=value optimized out, timeout=value optimized out) at ptclib/psockbun.cxx:980 #6 0x4f09e15a in OpalListenerUDP::Accept (this=value optimized out, timeout=value optimized out) ---Type return to continue, or q return to quit--- at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:717 #7 0x4f09f796 in OpalListener::ListenForConnections (this=value optimized out, thread=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:448 #8 0x4f0a1a22 in OpalListener::ListenForConnections_PNotifier::Call (this=Could not find the frame base for OpalListener::ListenForConnections_PNotifier::Call(PObject, int) const. ) at /usr/src/debug/opal-3.4.2/include/opal/transports.h:350 #9 0x08107667 in PNotifier::operator() (this=0x9ef3db4, notifi...@0x9ef3d30, extra=0) at /usr/include/ptlib/notifier.h:95 #10 0x4ecbb278 in PSimpleThread::Main (this=Could not find the frame base for PSimpleThread::Main(). ) at ptlib/common/osutils.cxx:1971 #11 0x4ec982d8 in PThread::PX_ThreadStart (arg=value optimized out) at
Re: [Ekiga-devel-list] Segmentation fault when caller clears the call
Can you try Ekiga TRUNK ? Le samedi 10 janvier 2009 à 19:04 +, Andrea a écrit : I've had this issue since I moved to 3.0.1 I am on Fedora 9. Someone calls (in this case I call via a real phone) and I cancel the call before answering. The it crashes always. I've used only SILENT and LOGO as devices (just to be sure it is not a Pulseaudio or Alsa issue). The SIP server is messagenet. I've attached the output of ekiga -d 4 Program received signal SIGSEGV, Segmentation fault. 0x4eab08d2 in g_type_check_instance_cast () from /lib/libgobject-2.0.so.0 Thread 17 (Thread 0xb6e33b90 (LWP 5452)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00ad9ba5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x4ec937d3 in PSyncPoint::Wait (this=value optimized out) at ptlib/unix/tlibthrd.cxx:1419 #3 0x4f496a06 in SIPEndPoint::SIP_PDU_Thread::Main (this=value optimized out) at /usr/src/debug/opal-3.4.2/src/sip/sipep.cxx:1299 #4 0x4ec982d8 in PThread::PX_ThreadStart (arg=value optimized out) at ptlib/unix/tlibthrd.cxx:806 #5 0x00ad632f in start_thread () from /lib/libpthread.so.0 #6 0x00a1120e in clone () from /lib/libc.so.6 Thread 15 (Thread 0xb6e74b90 (LWP 5450)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00a09671 in select () from /lib/libc.so.6 #2 0x4ec951d8 in PThread::PXBlockOnIO (this=value optimized out, handle=value optimized out, type=value optimized out, timeout=value optimized out) at ptlib/unix/tlibthrd.cxx:903 #3 0x4ec8a302 in PChannel::PXSetIOBlock (this=value optimized out, type=value optimized out, timeout=value optimized out) at ptlib/unix/channel.cxx:119 #4 0x4ec872ec in PSocket::os_accept (this=value optimized out, listener=value optimized out, addr=Could not find the frame base for PSocket::os_accept(PSocket, sockaddr*, int*). ) at ptlib/unix/socket.cxx:206 #5 0x4ecad50a in PTCPSocket::Accept (this=value optimized out, socket=value optimized out) at ptlib/common/sockets.cxx:2263 #6 0x4f0a16ab in OpalListenerTCP::Accept (this=value optimized out, timeout=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:613 #7 0x4f09f796 in OpalListener::ListenForConnections (this=value optimized out, thread=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:448 #8 0x4f0a1a22 in OpalListener::ListenForConnections_PNotifier::Call (this=Could not find the frame base for OpalListener::ListenForConnections_PNotifier::Call(PObject, int) const. ) at /usr/src/debug/opal-3.4.2/include/opal/transports.h:350 #9 0x08107667 in PNotifier::operator() (this=0x9fb6cac, notifi...@0x9fb6c28, extra=0) at /usr/include/ptlib/notifier.h:95 #10 0x4ecbb278 in PSimpleThread::Main (this=Could not find the frame base for PSimpleThread::Main(). ) at ptlib/common/osutils.cxx:1971 #11 0x4ec982d8 in PThread::PX_ThreadStart (arg=value optimized out) at ptlib/unix/tlibthrd.cxx:806 #12 0x00ad632f in start_thread () from /lib/libpthread.so.0 #13 0x00a1120e in clone () from /lib/libc.so.6 Thread 14 (Thread 0xb6ebcb90 (LWP 5449)): #0 0xb7f10424 in __kernel_vsyscall () #1 0x00a09671 in select () from /lib/libc.so.6 #2 0x4ec87073 in PSocket::Select (read=value optimized out, write=value optimized out, except=value optimized out, timeout=value optimized out) at ptlib/unix/socket.cxx:328 #3 0x4ecae82e in PSocket::Select (read=value optimized out, timeout=value optimized out) at ptlib/common/sockets.cxx:1037 #4 0x4ecb6f5a in PMonitoredSockets::ReadFromSocket (this=value optimized out, readers=value optimized out, socket=value optimized out, buf=value optimized out, len=value optimized out, addr=value optimized out, port=value optimized out, lastReadCount=value optimized out, timeout=value optimized out) at ptclib/psockbun.cxx:577 #5 0x4ecb752d in PMonitoredSocketBundle::ReadFromBundle (this=value optimized out, buf=value optimized out, len=value optimized out, addr=value optimized out, port=value optimized out, iface=value optimized out, lastReadCount=value optimized out, timeout=value optimized out) at ptclib/psockbun.cxx:980 #6 0x4f09e15a in OpalListenerUDP::Accept (this=value optimized out, timeout=value optimized out) ---Type return to continue, or q return to quit--- at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:717 #7 0x4f09f796 in OpalListener::ListenForConnections (this=value optimized out, thread=value optimized out) at /usr/src/debug/opal-3.4.2/src/opal/transports.cxx:448 #8 0x4f0a1a22 in OpalListener::ListenForConnections_PNotifier::Call (this=Could not find the frame base for OpalListener::ListenForConnections_PNotifier::Call(PObject, int) const. ) at /usr/src/debug/opal-3.4.2/include/opal/transports.h:350 #9 0x08107667 in PNotifier::operator() (this=0x9ef3db4, notifi...@0x9ef3d30, extra=0) at
Re: [Ekiga-devel-list] Segmentation fault when caller clears the call
Damien Sandras wrote: Le samedi 10 janvier 2009 à 20:40 +, Andrea a écrit : Damien Sandras wrote: Can you try Ekiga TRUNK ? Do I need trunk of Ekiga, Opal and PTLib or can I use some of the archives released as 3.1.0? You can use what was released with 3.1.0. The only issue in 3.1.0 is that ekiga crashes upon exit with assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 Mind you, I installed it in $HOME/usr and I got some installation errors of scheme files. ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-list] Yet an other post on Pulseaudio
Hi, I've just upgraded from 2.x to 3.0.1 on Fedora 9. There are some issues with Pulseaudio This is when an incoming call is received. *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error Segmentation fault I've read the mailing list and it seems the best thing to do is to switch off pulseaudio of the devices used by ekiga. I was just wondering is anybody has found a more friendly way to let ekiga work with pulseaudio. Would the support for oss help? Cheers ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Suse 11.1 Compile problems
All, This thread is an attempt to document compile problems on SUSE 11.1 As mentioned in previous emails one of my main problems has been that the compile goes looking for libs in /opt/gnome/lib when all libs seem to be put into /usr/lib now. I managed to get a compile done using this. $ ./configure --prefix=/usr --enable-debug --disable-eds --disable-gdu --disable-libtool-lock --disable-gnome However, I cannot make or recieve calls now. I will update this later when I get the problem resolved. The purpose of this email is to highlight the resmgr problem. After I got the libs problem sorted the compile then failed with a 'cannot load resmgr' message. This is correct there is no resmgr on 11.1. So I did a contents search of the 3.0.1 src and found the following have the word resmgr in them. /ekiga-3.0.1/lib/engine/libekiga_engine.la /ekiga-3.0.1/lib/engine/.libs/libekiga_engine.la /ekiga-3.0.1/lib/libekiga.la /ekiga-3.0.1/lib/.libs/libekiga.la /ekiga-3.0.1/lib/engine/addressbook/evolution/libgmevolution.la /ekiga-3.0.1/lib/engine/addressbook/evolution/.libs/libgmevolution.la /ekiga-3.0.1/lib/engine/gui/gtk-core/libgmgtk-core.la /ekiga-3.0.1/lib/engine/gui/gtk-core/.libs/libgmgtk-core.la /ekiga-3.0.1/lib/engine/gui/gtk-frontend/libgmgtk-frontend.la /ekiga-3.0.1/lib/engine/gui/gtk-frontend/.libs/libgmgtk-frontend.la /ekiga-3.0.1/lib/toolbox/libtoolbox.la /ekiga-3.0.1/lib/toolbox/.libs/libtoolbox.la I am not aware at this stage if any/all of the above actually do a call to load resmgr, they just have the word in there. To be clear, with the normal ./configure I get the resmgr problem, with the above configure I don't. Brian -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] echo canceller
If I lower the microphone, the people tell me that they cannot hear me anymore because my voice is too low. I dont want an extern microphone. Thats not convenient. Echo canceller in Ekiga is activated with a hook. What do you mean by disable mic boost, put mic out to 0? It says in Audio-Codecs Jitter-Puffer is between 20 and 500 ms automatically. What does it mean? Palo S. schrieb: several possibilities: external microphone headphones audio channels settings (disable mic boost, put mic out to 0, lower mic record) have you tried echo canceller in Ekiga? P. - Originálna Správa - Od: Judith Meili Komu: Ekiga mailing list Poslaná: 10.01.2009 13:05 Predmet: [Ekiga-list] echo canceller I have no echo problems with skype but with Ekiga there is a big echo and the receivers of my calls complain. Is there no way to get rid of this echo? Br jm ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list __ http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Registration Failed: Timeout
On Sat, Jan 10, 2009 at 2:24 PM, Palo S. pa...@post.sk wrote: make a new account? if that works then you know something was broken with your old one, jaysus! i should have don't that as the first thing!!! it works! so the old account is busted... thanks! if even that does not work then you know something if wrong with your network/other settings... P. - Originálna Správa - Od: Damien Sandras Komu: Ekiga mailing list Poslaná: 10.01.2009 12:14 Predmet: Re: [Ekiga-list] Registration Failed: Timeout Le vendredi 09 janvier 2009 Ă 17:34 +, Daniel Castro a ĂŠcrit : On Fri, Jan 9, 2009 at 12:18 PM, Damien Sandras wrote: Le vendredi 09 janvier 2009 Ă 11:24 +, Daniel Castro a ĂŠcrit : On Thu, Jan 8, 2009 at 9:40 PM, Damien Sandras wrote: Le jeudi 08 janvier 2009 Ă 21:13 +, Daniel Castro a ĂŠcrit : OK then login/password combination is wrong. But I requested a new password using the forgot password tool from the website. I created my account long ago (23/12/07) and never used it since could it be a problem with the sip? Create a new one? Please contact accou...@ekiga.net so that we verify your password. I contacted them. They said everything is ok with the account. Did they check the pass is what you expect ? yes they did... any other ideas? No... Unfortunately not. -- _ Damien Sandras (o- //\\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.netsip%3adsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list __ BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje myšlienky, zážitky a nové informácie - http://blog.sme.sk/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] ekiga irc - what am I doing wrong?
of course, sorry! ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Registration Failed: Timeout
jaysus! i should have don\'t that as the first thing!!! it works! so the old account is busted... thanks! The simplest solutions are often the best :) I am glad it helped, Palo __ http://zabava.sme.sk/ - Stránka čo usmeje ti tvár ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Yet an other post on Pulseaudio
Le samedi 10 janvier 2009 à 13:03 +, Andrea a écrit : Hi, I've just upgraded from 2.x to 3.0.1 on Fedora 9. There are some issues with Pulseaudio This is when an incoming call is received. *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error Segmentation fault I've read the mailing list and it seems the best thing to do is to switch off pulseaudio of the devices used by ekiga. I was just wondering is anybody has found a more friendly way to let ekiga work with pulseaudio. Would the support for oss help? I don't think so. Perhaps you should report the problem to the pulseaudio guys. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Yet an other post on Pulseaudio
Damien Sandras wrote: Le samedi 10 janvier 2009 à 13:03 +, Andrea a écrit : Hi, I've just upgraded from 2.x to 3.0.1 on Fedora 9. There are some issues with Pulseaudio This is when an incoming call is received. *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error *** PULSEAUDIO: Unable to create stream. Cannot set parameters Input/output error Segmentation fault I've read the mailing list and it seems the best thing to do is to switch off pulseaudio of the devices used by ekiga. I was just wondering is anybody has found a more friendly way to let ekiga work with pulseaudio. Would the support for oss help? I don't think so. Perhaps you should report the problem to the pulseaudio guys. First I need to learn how to disable pulseaudio, then I will have a better clue where the issue is. Cheers ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Yet an other post on Pulseaudio
Hi, I think that we have to recognise that pulse audio is here to stay. Yes, pulseaudio has design issues. Take for instance pulseaudio on ubuntu 8.10. I cannot see how to direct pulseaudio to put sound from one app to one audio device , and sound for a different app to a second audio device. --- Asking users to remove pulse audio to make ekiga work is not an option. On some distributions, taking the pulse audio package off will remove a whole host of other packages. The only reasonable solution is to write a pulse audio plugin for ptlib. But I was reading elsewhere from some expert who said that if you have alsa code that works, you should not need to write anything. Last time I looked on the pulse audio web page, there was no information on writing a pulse audio plugin for readingwriting sound. Can anyone provide a definitive web page on how to write a valid pulse audio plugin? If you can provide a definitive web page on writing a valid pulse audio plugin that does record and play correctly, then I can write a pulseaudio plugin. == rant We have had over the years numerous sound systems on linux. OSS, ESD, ARTS, jack, alsa, pulseaudio, coreaudio come to mind. Admittedly, some are based on others.. Yet, after years of development, we have no clear winner as being suitable for the desktop. Since sound is a crucial part of gui applications, and since sound deos not work reliably on linux, I find it ludicrous to think that Linux is ready for the masses. Some users have to write custom asound.conf files. Some have to disable pulseaudio. Conclusion: Should windows users switch to linux, they will have to battle hard to get basic things (like sound) to work. /rant Question: Is the deficiencies of audio in ekiga Damien's, or the plib/opal authors fault? No, these people all struggled hard with appalling documentation to write something that worked. Derek. On Sat, 10 Jan 2009, Andrea wrote: Damien Sandras wrote: Le samedi 10 janvier 2009 à 13:03 +, Andrea a écrit : Hi, I was just wondering is anybody has found a more friendly way to let ekiga work with pulseaudio. Would the support for oss help? I don't think so. Perhaps you should report the problem to the pulseaudio guys. First I need to learn how to disable pulseaudio, then I will have a better clue where the issue is. Cheers ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: de...@indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): Re^6: Audio-Problems
I have a similar problem. I have an Audigy sound card using ca0106, and a USB
headset using snd-usb-audio. I have adapted your modprobe.conf, but how do
you switch between them? For a while they were loaded automatically
according to the application I opened, but no longer.
Doug.
On Sunday 04 January 2009 4:49:36 am Palo S. wrote:
You can specify the order of sound drivers loading
in your modprobe file. I have three sound devices
in my main home computer (every device used with
different program) and the specification of order
is very reliable. These are the lines I use
(I think they are self-explanatory, if not then you
can certainly find more info with google):
alias snd-card-0 snd-emu10k1
options snd-emu10k1 index=0
remove snd-emu10k1 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; };
/sbin/modprobe -r --ignore-remove snd-emu10k1 alias snd-card-1 snd-intel8x0
remove snd-ca0106 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; };
/sbin/modprobe -r --ignore-remove snd-ca0106 options snd-intel8x0 index=1
remove snd-intel8x0 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; };
/sbin/modprobe -r --ignore-remove snd-intel8x0 alias snd-card-2
snd-usb-audio
options snd-usb-audio index=2
Hope this helps,
Palo
- Originálna Správa -
Od: PETER EASTHOPE
Komu:
Poslaná: 03.01.2009 18:02
Predmet: [Ekiga-list] Re (2): Re^6: Audio-Problems
Folk,
... versions of Ekiga and Skype ... problem ...
The worst difficulties for me are with audio
devices rather than with applications which use
them. The USB-audio adapter always initializes
but the on-board Intel audio sometimes fails.
I\'ll guess that this involves timing of startup
processes.
When the Intel audio is absent, the Skype icon
appears as usual. Hours or days later, after
a correspondent complains that I didn\'t answer
a call, ringing is found to be redirected
from the speakers to the headset. Skype never
indicates this of course.
Appears that when Ekiga fails to find a device,
the toolbar icon is not displayed. A rational
behaviour; thanks to Ekiga.
I\'m phasing out Skype DID in favour of Ekiga
DID and hoping the flaws in Linux device
initialization are fixed, sooner rather than
later.
Regards,... Peter E.
--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
__
http://chat.post.sk - zachatujte si s priatelmi na IRC.POST.SK
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Fwd: Audio-Problems]
Open Mandriva Control Centre - Hardware - and you will see listed, the driver module your soundcard uses. Doug (same distro.) On Monday 05 January 2009 4:12:20 am Judith Meili wrote: I use Ekiga 2.0.12 and Skype 2.0.0.72 Mandriva 2009. Where do I see the name of the soundcard? It's a REFURB IMAC 17/2.0/1G/160/SD/AP/BT-SWM. When I closed Skype it didnt help and when I closed Ekiga and wanted to open Ekiga again, it said that Ekiga is still open. So I restarted the whol machine. Now it is fine. I dont understand whats going on. Judith Palo S. schrieb: - Originálna Správa - Od: Judith Meili Komu: Ekiga mailing list Poslaná: 04.01.2009 10:07 Predmet: [Ekiga-list] [Fwd: Audio-Problems] Dear all What do I need to do? After closing skype, Ekiga is still not working. Always the same message below. It should. Which version of Ekiga, Skype, which operating system and which soundcard do you use? Does it also not work if you restart Ekiga after closing Skype? It looks like Skype blocks the soundcard which could be caused by an older version of Skype for instance... Br jm Original-Nachricht Betreff: Audio-Problems Datum: Tue, 30 Dec 2008 08:29:19 +0100 Von: Judith Meili An:Ekiga mailing list Hello Why do I get this message? \Audiokanal zum Audioempfang konnte nicht geöffnet werden Beim Versuch, Audio für den Audio-Empfang über die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte überprüfen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterstützt. Der Audioempfang wurde deaktiviert.\ Br jm ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list __ http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): Re^6: Audio-Problems
It just occurred to me that my webcam has a microphone, and probably, that
should be listed as well.
I see Judith's error message regularly with Xmms.
Doug.
On Sunday 11 January 2009 10:58:45 am Doug Laidlaw wrote:
I have a similar problem. I have an Audigy sound card using ca0106, and a
USB headset using snd-usb-audio. I have adapted your modprobe.conf, but
how do you switch between them? For a while they were loaded automatically
according to the application I opened, but no longer.
Doug.
On Sunday 04 January 2009 4:49:36 am Palo S. wrote:
You can specify the order of sound drivers loading
in your modprobe file. I have three sound devices
in my main home computer (every device used with
different program) and the specification of order
is very reliable. These are the lines I use
(I think they are self-explanatory, if not then you
can certainly find more info with google):
alias snd-card-0 snd-emu10k1
options snd-emu10k1 index=0
remove snd-emu10k1 { /usr/sbin/alsactl store 0 /dev/null 21 || : ; };
/sbin/modprobe -r --ignore-remove snd-emu10k1 alias snd-card-1
snd-intel8x0 remove snd-ca0106 { /usr/sbin/alsactl store 0 /dev/null
21 || : ; }; /sbin/modprobe -r --ignore-remove snd-ca0106 options
snd-intel8x0 index=1 remove snd-intel8x0 { /usr/sbin/alsactl store 0
/dev/null 21 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias snd-card-2
snd-usb-audio
options snd-usb-audio index=2
Hope this helps,
Palo
- Originálna Správa -
Od: PETER EASTHOPE
Komu:
Poslaná: 03.01.2009 18:02
Predmet: [Ekiga-list] Re (2): Re^6: Audio-Problems
Folk,
... versions of Ekiga and Skype ... problem ...
The worst difficulties for me are with audio
devices rather than with applications which use
them. The USB-audio adapter always initializes
but the on-board Intel audio sometimes fails.
I\'ll guess that this involves timing of startup
processes.
When the Intel audio is absent, the Skype icon
appears as usual. Hours or days later, after
a correspondent complains that I didn\'t answer
a call, ringing is found to be redirected
from the speakers to the headset. Skype never
indicates this of course.
Appears that when Ekiga fails to find a device,
the toolbar icon is not displayed. A rational
behaviour; thanks to Ekiga.
I\'m phasing out Skype DID in favour of Ekiga
DID and hoping the flaws in Linux device
initialization are fixed, sooner rather than
later.
Regards,... Peter E.
--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
__
http://chat.post.sk - zachatujte si s priatelmi na IRC.POST.SK
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): Re^6: Audio-Problems
I have a similar problem. I have an Audigy sound card using ca0106, and a USB headset using snd-usb-audio. I have adapted your modprobe.conf, but how do you switch between them? For a while they were loaded automatically according to the application I opened, but no longer. The index keyword in modprobe only defines the order of the devices, ie you can be sure that eg device 0 is always ca0106 and device 1 is snd-usb-audio. You still need to say each application which of your devices it should use, every application dealing with sound should have settings enabling to specify the device (eg in Ekiga under Preferences-Audio Devices). index in modprobe then assures that the devices will be assigned always the same and you won\'t need to change the application settings after reboots. P. __ http://www.tahaj.sk - Najnavstevovanejsia stranka slovenskeho downloadu ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Yet an other post on Pulseaudio
First I need to learn how to disable pulseaudio, then I will have a better clue where the issue is. yum remove pulseaudio P. __ http://kultura.sme.sk/ - Informačný server o kultúre a šoubiznise ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Hello Ekiga list. BerkeleyTIP you
On Sat, 03 Jan 2009 15:23:49 +0100, Damien Sandras dsand...@seconix.com said: Le samedi 03 janvier 2009 à 02:47 -0800, john_re a écrit : Hi Ekiga list readers :) I thought you might like to be aware that: Ekiga the Ekiga VOIP conferencing system are being used for communication for a global GNU(Linux), BSD All Free SW HW monthly meeting, called BerkeleyTIP. [...] Excellent ! Thanks for letting us know about the use of Ekiga :-) Thanks for all your work on Ekiga, Damien. :) 1) Is it OK for me to post a once or twice monthly announcement regarding the BerkeleyTIP meeting to this list? Probably about 3 weeks 1 week ahead of time. It would note the meeting date, the lecture/talks topics, maybe a few other significant items. I posted the 1 week style announcement to this list just after the message you responded to here. That's what it looks like. List readers here might like to know about the meeting to: a) work on improving or using Ekiga, especially in the ProgrammingParty Installfest parts of the meeting, b) just learn or talk with other members, in the other parts of the meeting. An important part of the current ProgrammingParty part of the meeting is to improve our knowledge of, the sw for, VOIP technology, to improve the VOIP communication experience for people attending the meeting wherever in the world they are. 2) Two of our local attendees at the Jan meeting had Apple Macs. What is the time schedule, if any, for providing a Mac version of Ekiga? 3) About 1 or 2 months ago, a friend who know more about VOIP than I, recommended I use the Ekiga 2 in KUbuntu 8.04, rather than E 3. In your opinion, is E3 now more suitable for general VOIP use than E2? Thanks. :) ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Re (2): Re^6: Audio-Problems
On Sunday 11 January 2009 12:11:05 pm Palo S. wrote: I have a similar problem. I have an Audigy sound card using ca0106, and a USB headset using snd-usb-audio. I have adapted your modprobe.conf, but how do you switch between them? For a while they were loaded automatically according to the application I opened, but no longer. The index keyword in modprobe only defines the order of the devices, ie you can be sure that eg device 0 is always ca0106 and device 1 is snd-usb-audio. You still need to say each application which of your devices it should use, every application dealing with sound should have settings enabling to specify the device (eg in Ekiga under Preferences-Audio Devices). index in modprobe then assures that the devices will be assigned always the same and you won\'t need to change the application settings after reboots. P. Everything works if I put snd-usb-audio as No. 0, and ca0106 as No.1. Otherwise the USB chamnnel is blocked. Thanks for your guidance. Doug. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
