Re: [Ekiga-list] core dump on suse 12.1
Am 23.12.2011 21:07, schrieb Eugen Dedu: On 23/12/11 18:45, Franz Fuder wrote: Hi all, I got a core dump with ekiga, here is the output: 2011/12/23 18:40:39.091 0:00.759 OPAL SetMediaFormatOrder(SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,iLBC,G.711-uLaw-64k,G.711-ALaw-64k,G.722-64k,CELT-48K,CELT-32K,H.261,H.261-CIF,H.261-QCIF,theora) 2011/12/23 18:40:39.099 0:00.767 Housekeeper:0x740c4700 PTLib MONITOR:timers=1 2011/12/23 18:40:39.102 0:00.769 PWLib File handle high water mark set: 34 Thread unblock pipe 2011/12/23 18:40:39.102 0:00.770 PTLib Created thread 0x968520 2011/12/23 18:40:39.102 0:00.770 PTLib Thread high water mark set: 10 2011/12/23 18:40:39.102 0:00.770 StunDetector:0x67983700 PTLib Started thread 0x968520 StunDetector:0x67983700 2011/12/23 18:40:39.102 0:00.770 StunDetector:0x67983700 PWLib File handle high water mark set: 36 PUDPSocket Speicherzugriffsfehler I am using suse 12.1 and installed ekiga via rpm version 3.2.7.1.2-x89_64 The information you provided is not sufficient. Is the crash reproducible? If yes, could you please retry it under gdb, as shown at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze Thanks for the quick answer even at x-mass. I tried today the 32bit vesion and it works! Then I switched back to the 64 bit version and it works too. No clue what happesn might be the reboot managed it. However thanks for your time It works now. Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] core dump on suse 12.1
Hi all, I got a core dump with ekiga, here is the output: 2011/12/23 18:40:39.091 0:00.759 OPAL SetMediaFormatOrder(SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,iLBC,G.711-uLaw-64k,G.711-ALaw-64k,G.722-64k,CELT-48K,CELT-32K,H.261,H.261-CIF,H.261-QCIF,theora) 2011/12/23 18:40:39.099 0:00.767 Housekeeper:0x740c4700 PTLib MONITOR:timers=1 2011/12/23 18:40:39.102 0:00.769 PWLib File handle high water mark set: 34 Thread unblock pipe 2011/12/23 18:40:39.102 0:00.770 PTLib Created thread 0x968520 2011/12/23 18:40:39.102 0:00.770 PTLib Thread high water mark set: 10 2011/12/23 18:40:39.102 0:00.770 StunDetector:0x67983700 PTLib Started thread 0x968520 StunDetector:0x67983700 2011/12/23 18:40:39.102 0:00.770 StunDetector:0x67983700 PWLib File handle high water mark set: 36 PUDPSocket Speicherzugriffsfehler I am using suse 12.1 and installed ekiga via rpm version 3.2.7.1.2-x89_64 Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Can not connect to echo server
Damien Sandras schrieb: Le samedi 07 février 2009 à 14:00 +0100, Franz Fuder a écrit : Damien Sandras schrieb: Le vendredi 06 février 2009 à 11:52 +0100, Franz Fuder a écrit : Today I compiled the Ekiga out of the svn tree all three components. The build was made on a suse 11.1 and ran without any problems. However when I tried to connect to the echo server it fails. I seems to me that the listner fails for some reasons ? Any thought what I have done wrong, the firewall rules are in place. For some reason (that I ignore), it can not bind to the 5060 port. It could happen if you do not have any network interface 'up', or if something prevents it to bind to that port (some kernel security patch for example). Ops pressed the send button too early, here the final mail. I checked the port 5060 and the network, there is only one eth0 up and running. I installed the ekiga from suse: -- 2009/02/07 11:58:47.510 0:00.131ekiga Version 3.0.1 by on Unix Linux (2.6.27.7-9-pae-i686) at 2009/2/7 11:58:47.510 2009/02/07 11:58:47.510 0:00.131ekiga Ekiga SVN revision: unknown --- and it runs fine, I can connect to the echo server. I guess from the network everything should be fine in case not the suse ekiga versions should also not connect to the echo server. When I run the last svn version with ekiga -d 3 I get: - 2009/02/07 13:49:38.447 0:07.164 Opal Liste...0xb489bb90 OpalUDP Binding to interface: 88.152.92.142:5060 2009/02/07 13:49:38.448 0:07.165 Opal Liste...0xb489bb90 SIP PDU 202 OK received: rem=udp$86.64.162.35:5060,local=udp $88.152.92.142:5060,if=192.168.1.3% eth0 - seems to me that the binding is ok of the port. I get some messages with PDU too large ? Is the PDU the problem ? after I get: 009/02/07 13:49:55.432 0:24.149 Housekeeper:0xb48dcb90 SIP Transaction 1 INVITE timeout, making retry 1 2009/02/07 13:49:55.436 0:24.153 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option MaxBR from 0 to 40960 2009/02/07 13:49:55.449 0:24.166 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option MaxBR from 0 to 40960 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP PDU is likely too large (1703 bytes) for UDP datagram. 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP Sending PDU INVITE sip:5...@ekiga.net (1703 bytes) to: rem=udp $86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3% eth0 2009/02/07 13:49:55.455 0:24.172 Housekeeper:0xb48dcb90 OpalUDP Setting interface to 192.168.1.3% eth0 2009/02/07 13:49:56.455 0:25.172 Housekeeper:0xb48dcb90 SIP Transaction 1 INVITE timeout, making retry 2 2009/02/07 13:49:56.459 0:25.176 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option MaxBR from 0 to 40960 2009/02/07 13:49:56.469 0:25.186 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option MaxBR from 0 to 40960 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP PDU is likely too large (1703 bytes) for UDP datagram. 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP Sending PDU INVITE sip:5...@ekiga.net (1703 bytes) to: rem=udp $86.64.162.35:5060,local=udp$88.152.92.142:5060
Re: [Ekiga-list] Can not connect to echo server
Damien Sandras schrieb: Le samedi 07 février 2009 à 14:18 +0100, Franz Fuder a écrit : Perhaps you enabled all codecs with all options ? Yes I have done, is this not correct ? Which one could I use ? Just those you need... Thanks for the tip, in the audio section all the codecs are fine. In the video section only the h261 the first one is working. If I activate one of the others it can not connect only with the h261 it can connect wiht the server. I used the echo cancellation but when I use the USB Cam mic I get terrible echoes. Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] compile error /usr/lib64/libgnomeui-2.so: undefined reference to `g_dgettext'
I just trying to compile the Ekiga with the Suse 11 X64 and got the following error: compile error /usr/lib64/libgnomeui-2.so: undefined reference to `g_dgettext' I thought it has something to do with the ebook evolution server so I used the --disable-eds switch. However it does not help. Any thoughts do I use the wrong evolution-devel package ? I am using 2.23.6-5 version Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] opal plugins
All, I compiled today the opal lib with the new suse 11 I got a bunch of problems in: 1. h264pipe_unix.cxx I add the #include string.h for stderror() 2. h264helper_unix.cxx I add the #include stdlib.h for atoi() 3. x264loader_unix.cxx I add the #include string.h for strlen() 4. h263-1998.h I add the the #include string.h for memset() 5. h263pframe.cxx I add the #include string.h for memset() 6. mpi.cxx I add the #include stdlib.h for abs() I am sure that I put the include on the wrong place, might be there is an global import file. However it compiles now Regards Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] svn Ekiga crash on suse 10.3
Just on x-mess I have the time to build the ekiga from the SVN. However the compilation went nice. I used the new ptlib and opal from the svn and the new ekiga too. The system is a suse 10.3. However, I get two blinking lights from the usb cam and than ekiga dies with a : ekiga: symbol lookup error: ekiga: undefined symbol: _ZN15OpalMediaFormat19argetBitRateOptionEv I ran it a gain with d 6 and the last the I got is: 2007/12/26 20:08:31.899 0:04.195 Detected video codecs: H.261,RFC4175_YCbCr-4:2:0,theora,RFC4175_RGB,H.261-CIF,H.261-QCIF Any ideas what is wrong ? Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] svn Ekiga crash on suse 10.3
Damien Sandras schrieb: Le mercredi 26 décembre 2007 à 20:56 +0100, Franz Fuder a écrit : Damien Sandras schrieb: Le mercredi 26 décembre 2007 à 20:09 +0100, Franz Fuder a écrit : Just on x-mess I have the time to build the ekiga from the SVN. However the compilation went nice. I used the new ptlib and opal from the svn and the new ekiga too. The system is a suse 10.3. However, I get two blinking lights from the usb cam and than ekiga dies with a : ekiga: symbol lookup error: ekiga: undefined symbol: _ZN15OpalMediaFormat19argetBitRateOptionEv I ran it a gain with d 6 and the last the I got is: 2007/12/26 20:08:31.899 0:04.195 Detected video codecs: H.261,RFC4175_YCbCr-4:2:0,theora,RFC4175_RGB,H.261-CIF,H.261-QCIF Any ideas what is wrong ? You compiled Ekiga with different headers than the version of the library Ekiga is running against. I justed checked with yast if there is an old devel package or a anything else. Nothing at all and also I compiled ptlib and opal fresh. The following I used the following for the compilation: /configure --prefix=/usr --enable-plugins for ptlib /configure --prefix=/usr for opal and ./autogen.sh --prefix=/usr --sysconfdir=/etc/ --disable-scrollkeeper for ekiga. Where can I find the wrong headers on the system ? Other possibility : an old version of the library somewhere (and ekiga runs against it). You can try 'ldd' on ekiga or 'find' on some header files. Thanks, yes I found an old ptlib and an opal lib strange that it was not replaced from the new one. Howewer, ekiga starts now but now it gets the hauptauge wintv 500 and it crashs again. I start the configuration druit and there I found the usb cam, after I select the cam I can see me but than ekiga got frozen and nothing happens, the last message that I got was: GMVideoGrabber:089e9500 Skipped earlier local frame this message runs forever. Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] No audio plungin found on X64
Am Sa, 16.12.2006, 11:53, schrieb Damien Sandras: Le samedi 16 décembre 2006 à 10:37 +, A. James Lewis a écrit : On Sat, 2006-12-16 at 10:44 +0100, Jan Schampera wrote: On Sat, 16 Dec 2006 01:02:20 + A. James Lewis [EMAIL PROTECTED] wrote: I also found that ekiga doesn't try very hard to find pwlib... since pwlib isn't really a library as the OS understands it, it will not help to add it to ld.so.conf... it looks only where hard coded to look, PREFIX/lib... I hope this could be a bit more flexable at runtime... ekiga could either look at the config, ld.so.conf or allow the pwlib location to be configured... I've not tried with a 64 bit machine, but this can also be an issue on 32 bits. True for the plugins in some way. But PWLib itself is searched and found by the dynamic linker, it IS a normal library. I found that a version of ekiga installed in /usr/local, will not find its pwlib codecs in /usr/lib... I think that mabe there is an arguement for having a few fallback locations if the compile time option is not available /usr/lib, /usr/local/lib and the 64 bit equivalents would be a good start... Is there any reason not to do this? Ekiga does not look for the plugins itself, but PWLIB is doing it, independently of the location from which Ekiga is executed. When you compile PWLIB, you give a --prefix option (defaults to /usr/local/), that option determines where plugins will be installed, and where it should look for them. If it doesn't find the plugins, it means that : - you have not run make install - you have conflicting versions installed and the process is not linked to the version of the library you expect it to be linked -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list My experience is different. I installed with checkinstall and prefix /usr. All the staff end then in /usr/lib below /usr which is in one sense correct. However, ekiga is searching the plugins (audio and vidio) in /usr/lib64. It is easy to see this, I made just a symbolic link from /usr/lib/pwlib to /usr/lib64 and this fixes the problem. For me this is fine, but I suppose a lot of other x64 user will have problems. Pwlib and opal has different build systems. Pwlib is taking care of diffrent OS and machtype but opal did not even look at this. Unfourtunatelly I do not understand enough, if I would I would fix it. I did it succesfully for pwib but opal donsn't work. so it make no sense to send the patch. Checkinstall works fine, I run it also on a 32 bit system and everything worked fine without any problems, so it is not due to checkinstall it is a problem with opal and pwlib I guess Franz ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Ekiga X86_64 compiling error
Hi, I tried to compile the cvs version (I checked it out via cvs) and got the following error. The funny thing is I do exakt the same thing on my i386 system and it went ok. On the x86_64 it failed. I have no idea why. I used exact the same recipie to do it. Any help Franz accounts.o: In function `gm_account_new()': gui/accounts.cpp:967: undefined reference to `PGloballyUniqueID::PGloballyUniqueID()' gui/accounts.cpp:967: undefined reference to `PGloballyUniqueID::AsString() const' /usr//lib/libopal.so: undefined reference to `PGloballyUniqueID::PGloballyUniqueID(PASN_OctetString const)' /usr//lib/libopal.so: undefined reference to `PGloballyUniqueID::PGloballyUniqueID(PString const)' /usr//lib/libopal.so: undefined reference to `vtable for PGloballyUniqueID' /usr//lib/libopal.so: undefined reference to `PGloballyUniqueID::IsNULL() const' /usr//lib/libopal.so: undefined reference to `PGloballyUniqueID::PGloballyUniqueID(char const*)' collect2: ld returned 1 exit status ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
