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 [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
