Re: [Ekiga-devel-list] Crash on... startup!
Le mardi 13 octobre 2009 à 19:26 +0200, Michael Rickmann a écrit : Julien Puydt schrieb: Julien Puydt a écrit : I had a nice surprise this morning, trying to launch ekiga : I'll try to update my ptlibopal to see if I have just been unlucky. I retried this evening : still crashing :-( Snark ___ I tried this evening on WIN32 : still crashing. I guess we will have to exercise patience. I made shure that the reason for the crash is mainly in Opal's handlers.cxx index maps and not in Ekiga's heap. With attached patch Ekiga works. I'll insist with Robert, but currently he does not answer me anymore. -- _ 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-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Crash on... startup!
Le mardi 13 octobre 2009 à 20:19 +0200, Damien Sandras a écrit : Le mardi 13 octobre 2009 à 19:26 +0200, Michael Rickmann a écrit : Julien Puydt schrieb: Julien Puydt a écrit : I had a nice surprise this morning, trying to launch ekiga : I'll try to update my ptlibopal to see if I have just been unlucky. I retried this evening : still crashing :-( Snark ___ I tried this evening on WIN32 : still crashing. I guess we will have to exercise patience. I made shure that the reason for the crash is mainly in Opal's handlers.cxx index maps and not in Ekiga's heap. With attached patch Ekiga works. I'll insist with Robert, but currently he does not answer me anymore. Is this your crash : (gdb) bt #0 0xb6f7d44f in __exchange_and_add (__mem=0xb521ab02, __val=-1) at /usr/include/c++/4.3/ext/atomicity.h:51 #1 0xb6f8cc3b in PAtomicInteger::operator-- (this=0xb521ab02) at /usr/include/ptlib/critsec.h:248 #2 0xb6ac0dfb in PContainer::Destruct (this=0xb541bb18) at ptlib/common/contain.cxx:123 #3 0xb7f19e8d in ~PAbstractArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:69 #4 ~PBaseArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:271 #5 ~PCharArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:564 #6 ~PString (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/pstring.h:102 #7 0xb73cf93d in ~pair (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/c++/4.3/bits/stl_pair.h:73 #8 0xb73cf961 in __gnu_cxx::new_allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::destroy (this=0xb555013f, __p=0xb541bb18) at /usr/include/c++/4.3/ext/new_allocator.h:118 #9 0xb73cf9a5 in std::_Rb_treePString, std::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::_Select1ststd::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::lessPString, std::allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::_M_destroy_node (this=0xb540f82c, __p=0xb541bb08) at /usr/include/c++/4.3/bits/stl_tree.h:390 #10 0xb74191ac in std::_Rb_treePString, std::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::_Select1ststd::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::lessPString, std::allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::erase ( this=0xb540f82c, __position=...) at /usr/include/c ++/4.3/bits/stl_tree.h:1319 #11 0xb74191e6 in std::mapPString, PSafePtrSIPHandler, PSafePtrBase, std::lessPString, std::allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::erase (this=0xb540f82c, __position=...) at /usr/include/c++/4.3/bits/stl_map.h:523 #12 0xb740c19f in SIPHandlersList::Remove (this=0xb540f748, handler=0x825b288) at /home/damien/Workspace/ekiga/opal/src/sip/handlers.cxx:1650 #13 0xb73c8637 in SIPEndPoint::GarbageCollection (this=0xb540f450) at /home/damien/Workspace/ekiga/opal/src/sip/sipep.cxx:378 #14 0xb6f7e38e in OpalManager::GarbageCollection (this=0x82094d0) at /home/damien/Workspace/ekiga/opal/src/opal/manager.cxx:1587 #15 0xb6f7e454 in OpalManager::GarbageMain (this=0x82094d0) at /home/damien/Workspace/ekiga/opal/src/opal/manager.cxx:1607 #16 0xb6f8665b in OpalManager::GarbageMain_PNotifier::Call (this=0x820bf28, note=..., extra=0) at /home/damien/Workspace/ekiga/opal/include/opal/manager.h:1452 #17 0xb7f19667 in PNotifierTemplateint::operator() (this=0x8208ca8, notifier=..., extra=0) at /usr/include/ptlib/notifier.h:129 #18 0xb6a9eef9 in PSimpleThread::Main (this=0x8208c08) at ptlib/common/osutils.cxx:1964 #19 0xb6a5cd1a in PThread::PX_ThreadStart (arg=0x8208c08) at ptlib/unix/tlibthrd.cxx:459 #20 0xb673d4b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #21 0xb6381a5e in clone () from /lib/i686/cmov/libc.so.6 I get it by simply disabling an account. -- _ 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-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Crash on... startup!
Damien Sandras wrote: Le mardi 13 octobre 2009 à 20:19 +0200, Damien Sandras a écrit : Le mardi 13 octobre 2009 à 19:26 +0200, Michael Rickmann a écrit : Julien Puydt schrieb: Julien Puydt a écrit : I had a nice surprise this morning, trying to launch ekiga : I'll try to update my ptlibopal to see if I have just been unlucky. I retried this evening : still crashing :-( Snark ___ I tried this evening on WIN32 : still crashing. I guess we will have to exercise patience. I made shure that the reason for the crash is mainly in Opal's handlers.cxx index maps and not in Ekiga's heap. With attached patch Ekiga works. I'll insist with Robert, but currently he does not answer me anymore. Is this your crash : (gdb) bt #0 0xb6f7d44f in __exchange_and_add (__mem=0xb521ab02, __val=-1) at /usr/include/c++/4.3/ext/atomicity.h:51 #1 0xb6f8cc3b in PAtomicInteger::operator-- (this=0xb521ab02) at /usr/include/ptlib/critsec.h:248 #2 0xb6ac0dfb in PContainer::Destruct (this=0xb541bb18) at ptlib/common/contain.cxx:123 #3 0xb7f19e8d in ~PAbstractArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:69 #4 ~PBaseArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:271 #5 ~PCharArray (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/array.h:564 #6 ~PString (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/ptlib/pstring.h:102 #7 0xb73cf93d in ~pair (this=0xb541bb18, __in_chrg=value optimized out) at /usr/include/c++/4.3/bits/stl_pair.h:73 #8 0xb73cf961 in __gnu_cxx::new_allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::destroy (this=0xb555013f, __p=0xb541bb18) at /usr/include/c++/4.3/ext/new_allocator.h:118 #9 0xb73cf9a5 in std::_Rb_treePString, std::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::_Select1ststd::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::lessPString, std::allocatorstd::pairPString const, PSafePtrSIPHandler, PSafePtrBase ::_M_destroy_node (this=0xb540f82c, __p=0xb541bb08) at /usr/include/c++/4.3/bits/stl_tree.h:390 #10 0xb74191ac in std::_Rb_treePString, std::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::_Select1ststd::pairPString const, PSafePtrSIPHandler, PSafePtrBase , std::lessPString, std::allocatorstd::pairPString const, PSafePtrSIPHandler, My crash has _Rb_tree inside, as shown above in #10, I think it's the same. -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Crash on... startup!
Damien Sandras schrieb: Le mardi 13 octobre 2009 à 19:26 +0200, Michael Rickmann a écrit : Julien Puydt schrieb: Julien Puydt a écrit : I had a nice surprise this morning, trying to launch ekiga : I'll try to update my ptlibopal to see if I have just been unlucky. I retried this evening : still crashing :-( Snark ___ I tried this evening on WIN32 : still crashing. I guess we will have to exercise patience. I made shure that the reason for the crash is mainly in Opal's handlers.cxx index maps and not in Ekiga's heap. With attached patch Ekiga works. I'll insist with Robert, but currently he does not answer me anymore. I guess we interrupted Robert's workflow. I trust in his expertise. Things may be more complicated than we can imagine. Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-list] LPC10
Le mardi 13 octobre 2009 à 00:28 +0200, W.P. a écrit : Użytkownik Damien Sandras napisał: Le dimanche 20 septembre 2009 à 08:58 +1000, Nichol Hill a écrit : Hi, I am in need of running LPC10 with Sip on a windows box. The codec compatabiity table for Ekiga seems to suggest this is supported, but I can not see LPC10 in the list of codecs. Can sombody please confirm if the Windows version of Ekiga supports LPC10. It doesn't. You will need to modify the code for it to work. Notice it is supported by OPAL (the underlying library), so it is not hard to make it work. Damien, some years ago we conducted tests with version 2.xx of ekiga on Linux and there WAS an option of LPC10 codec. You even set up ekiga.net for some time to support it. (Altrough tests failed - I tested possibility of VoIP on GPRS link). Was it only on Linux? It can be reenabled on Linux, but you need to recompile ekiga and change a line (do a grep LPC-10 on the source code and remove the appropriate line). -- _ 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] Transfer between machines
Le mardi 13 octobre 2009 à 13:58 +1300, Adam Bogacki a écrit : Hi, I have set up Ekiga 3.2.5 on a new machine but cannot remember all the settings I used last time. Would it be possible to transfer config files via USB ? If so, where should I look to find them ? I think it should be possible using gconftool . Something like gconftool -R /apps/ekiga will give you all the settings. I'm sure there is a way to reimport them, but you will need to read the manpage. -- _ 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] ekiga.net
Le mardi 13 octobre 2009 à 00:31 +0200, W.P. a écrit : Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be. (because of lacking of possibility to edit account?, etc - some time in the past it WAS possible). What relationship do you see between the possibility to edit an account and the fact that it would be dead ? -- _ 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] Transfer between machines
Adam, the program gconf-editor is your friend In your home directory (assuming you are using Linux) there is a file called .gconf. In this file under apps/egiga you will find a series of folders. One of which is contacts. I replaced this folder with the one from my old system to get all my old numbers. You should be able to replace the other directories too. Suggest you do a BACKUP first. Remember some formats may have changed from one version to the next so YMMV, Brian On Tue, 13 Oct 2009 13:58:08 +1300 Adam Bogacki a...@paradise.net.nz wrote: Hi, I have set up Ekiga 3.2.5 on a new machine but cannot remember all the settings I used last time. Would it be possible to transfer config files via USB ? If so, where should I look to find them ? Regards, Adam Bogacki, a...@paradise.net.nz ___ 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.net
Ok. So this is why I've never been able to register on Ubuntu... /JimmyVolatile On Tue, Oct 13, 2009 at 6:11 AM, yannick sev...@free.fr wrote: W.P. a écrit : Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be. (because of lacking of possibility to edit account?, etc - some time in the past it WAS possible). I will start working on this in a few days (in 1 week or 2 most probably) Best regards, Yannick W.P. ___ 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.net
JimmyVolatile a écrit : Ok. So this is why I've never been able to register on Ubuntu... It is not related. I'm using Ubuntu, and I can register. You issue is something else. /JimmyVolatile On Tue, Oct 13, 2009 at 6:11 AM, yannick sev...@free.fr wrote: W.P. a écrit : Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be. (because of lacking of possibility to edit account?, etc - some time in the past it WAS possible). I will start working on this in a few days (in 1 week or 2 most probably) Best regards, Yannick W.P. ___ 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] ekiga.net
Speaking of ekiga.net, can a donation be submitted _via_ Paypal? I have money in an account and prefer to use that rather than a credit card. Also, I wonder whether https://www.ekiga.net might have a graphical indicator of donation progress vs. target. A thermometer is often used in fundraising, for example. Thanks, ... Peter E. -- Google pathology workshop ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Jack Support
I'm the host of the Open Source Musician Podcast. One of the major hurdles for pod casters is having the ability to do interviews and/or have remote show hosts. Our current setup uses skype to hold the conversation using the alsa-jack bridge and an asoundrc pcm device. From there we record using Ardour and send to an icecast server using darkice. Being able to use a sip phone with native jack support would enable a much cleaner setup as well as conference calling ect.. I hope this can be a planned addition to ekiga or at the very least resolve the alsa pcm device issue. Thank you so much, Daniel Worth ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] some issues in current ekiga 3.2.6
On 10/13/2009 02:23 PM, Damien Sandras wrote: Le mardi 13 octobre 2009 à 11:13 +0200, Wolfgang Rosenauer a écrit : Attached is a full backtrace as created by the above command after the audio stopped one way and tried to hang up. Is it reproducable if you disable sound events in the preferences ? We have several problems introduced by pulseaudio itself on some systems. I've unchecked all the sound events in the preferences now and made a call. And again after a few minutes I got the same issue. :-( I've captured the backtrace again but as it was actually the same error behaviour I won't attach it again unless you tell me to. Wolfgang ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
