Re: [Ekiga-devel-list] Win32 Opal datasize, please help
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and rendered WinXP and Win7 unusable. Today I found the reason: commit
23036 to opal trunk which coresponds to 23028 opal v3_6 and is
contained in the archives needed by Ekiga 3.2.5.
Attached patch fixes this for ekiga head - it just reverses the opal
commit - no final solution. I am really no opal expert and a bit lost
here. Why has only Win32 been hit here?
Good news is that Split ekiga into an exec and helper libs - it
happend at about the same time as the opal change - seems to work for
Win32.
Would you have a -d 4 output of the problem when it occurs without your
patch?
Robert will examine it.
Thanks a lot. I produced the -d 4 logs with my Win32 version of current
Ekiga stable, i.e. Ekiga 3.2.5, Opal 3.6.4 and Ptlib 2.6.4. So commit
23028 to opal v3_6 seems to cause the error. The logs are rather long,
you find them at
http://wwwuser.gwdg.de/~mrickma/ekiga/data-size-logs.tar.gz.
5...@ekiganet-ekiga-killed-stderr.txt is when calling 5...@ekiga.net. As
soon as the call was accepted empty windows were piling up and I had to
kill Ekiga. fritzbox-nosound-ekiga-stderr.txt is when calling my
audio-only SIP-phone-box at home. Ekiga told me that it was unable to
open the audio driver, exit gracefully. The programs which I used can be
found at http://wwwuser.gwdg.de/~mrickma :
buggy-ekiga-setup-3.2.5-release.exe fails, ekiga-setup-3.2.5-release.exe
is ok with patch reversed, ekiga_build-3.2.5.tgz documents how I built
the stuff.
Can you try with the following patch ?
The error will stay, but we will have more information and you won't
have windows popping up again and again.
You will also have an indication of what the problem can be.
Robert thinks the problem could be in Ekiga, but due to the API change.
--
_ 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
diff --git a/lib/engine/components/ptlib/audioinput-manager-ptlib.cpp b/lib/engine/components/ptlib/audioinput-manager-ptlib.cpp
index 0d70fc0..69cb50d 100644
--- a/lib/engine/components/ptlib/audioinput-manager-ptlib.cpp
+++ b/lib/engine/components/ptlib/audioinput-manager-ptlib.cpp
@@ -183,8 +183,8 @@ bool GMAudioInputManager_ptlib::get_frame_data (char *data,
bytes_read = input_device-GetLastReadCount();
}
if (bytes_read != size) {
- PTRACE(1, GMAudioInputManager_ptlib\tEncountered error while trying to read data);
- Ekiga::Runtime::run_in_main (sigc::bind (sigc::mem_fun (this, GMAudioInputManager_ptlib::device_error_in_main), current_state.device, Ekiga::AI_ERROR_READ));
+ PTRACE(1, GMAudioInputManager_ptlib\tEncountered error while trying to read data, read bytes_read instead of size);
+// Ekiga::Runtime::run_in_main (sigc::bind (sigc::mem_fun (this, GMAudioInputManager_ptlib::device_error_in_main), current_state.device, Ekiga::AI_ERROR_READ));
}
}
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32 Opal datasize, please help
Damien Sandras schrieb: Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit : Damien Sandras schrieb: Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit : I was stuck testing the latest changes to Ekiga since about 10 days. Once a call to 5...@ekiga.net had been established windows were piling up and rendered WinXP and Win7 unusable. Today I found the reason: commit 23036 to opal trunk which coresponds to 23028 opal v3_6 and is contained in the archives needed by Ekiga 3.2.5. Attached patch fixes this for ekiga head - it just reverses the opal commit - no final solution. I am really no opal expert and a bit lost here. Why has only Win32 been hit here? Good news is that Split ekiga into an exec and helper libs - it happend at about the same time as the opal change - seems to work for Win32. Would you have a -d 4 output of the problem when it occurs without your patch? Robert will examine it. Thanks a lot. I produced the -d 4 logs with my Win32 version of current Ekiga stable, i.e. Ekiga 3.2.5, Opal 3.6.4 and Ptlib 2.6.4. So commit 23028 to opal v3_6 seems to cause the error. The logs are rather long, you find them at http://wwwuser.gwdg.de/~mrickma/ekiga/data-size-logs.tar.gz. 5...@ekiganet-ekiga-killed-stderr.txt is when calling 5...@ekiga.net. As soon as the call was accepted empty windows were piling up and I had to kill Ekiga. fritzbox-nosound-ekiga-stderr.txt is when calling my audio-only SIP-phone-box at home. Ekiga told me that it was unable to open the audio driver, exit gracefully. The programs which I used can be found at http://wwwuser.gwdg.de/~mrickma : buggy-ekiga-setup-3.2.5-release.exe fails, ekiga-setup-3.2.5-release.exe is ok with patch reversed, ekiga_build-3.2.5.tgz documents how I built the stuff. Can you try with the following patch ? The error will stay, but we will have more information and you won't have windows popping up again and again. You will also have an indication of what the problem can be. Robert thinks the problem could be in Ekiga, but due to the API change. I applied the patch, the Windows went and Win32 Ekiga is better than it ever was. The large audio delay ( 1.5 sec) is nearly gone, must have been the changes to Opal. However, as you said, the error stayed - somehow I like it, audio is next to perfect. In the logs we get now lines saying Media Patch:3096 GMAudioInputManager_ptlib Encountered error while trying to read data, read 160 instead of 320 The complete -d 4 log you find at http://wwwuser.gwdg.de/~mrickma/ekiga/ekiga-stderr.txt.gz . Attached backtrace shows what happens when calling 5...@ekiga.net and where the request for 320 comes from. Thanks for the help so far. Michael (gdb) Num Type Disp Enb AddressWhat 1 breakpoint keep y 0x00488564 in GMAudioInputManager_ptlib::get_frame_data(char*, unsigned int, unsigned int) at ../../../../lib/engine/components/ptlib/audioinput-manager-ptlib.cpp:186 breakpoint already hit 2 times (gdb) Continuing. (gdb) Continuing. [New thread 2020.0x4f4] [New thread 2020.0x190] [New thread 2020.0xe88] [New thread 2020.0xbd4] warning: Lowest section in C:\WINDOWS\system32\mfc42loc.dll is .rsrc at 61dc1000 [New thread 2020.0x9b8] [New thread 2020.0x748] [New thread 2020.0x9bc] [New thread 2020.0x7c4] [New thread 2020.0xac4] [New thread 2020.0xcfc] [New thread 2020.0x4b0] [New thread 2020.0x538] [New thread 2020.0x870] [New thread 2020.0xa24] [New thread 2020.0xac8] [New thread 2020.0xc54] [New thread 2020.0xf48] [New thread 2020.0x4e8] [New thread 2020.0xd24] [New thread 2020.0x9b4] [New thread 2020.0x74c] [New thread 2020.0xd34] [New thread 2020.0xd04] [New thread 2020.0x600] [New thread 2020.0xd00] [Switching to thread 2020.0x9b4] Breakpoint 1, GMAudioInputManager_ptlib::get_frame_data (this=0x8429580, data=0x8439c74 , size=320, bytes_read=0xc95fe14) at ../../../../lib/engine/components/ptlib/audioinput-manager-ptlib.cpp:186 186 ../../../../lib/engine/components/ptlib/audioinput-manager-ptlib.cpp: No such file or directory. in ../../../../lib/engine/components/ptlib/audioinput-manager-ptlib.cpp Current language: auto; currently c++ (gdb) #0 GMAudioInputManager_ptlib::get_frame_data (this=0x8429580, data=0x8439c74 , size=320, bytes_read=0xc95fe14) at ../../../../lib/engine/components/ptlib/audioinput-manager-ptlib.cpp:186 #1 0x00444bba in Ekiga::AudioInputCore::get_frame_data (this=0x83e3eb8, data=0x8439c74 , size=320, bytes_read=0xc95fe14) at ../../../lib/engine/audioinput/audioinput-core.cpp:374 #2 0x0048b68b in PSoundChannel_EKIGA::Read (this=0x8435198, buf=0x8439c74, len=320) at ../../../../lib/engine/components/opal/opal-audio.cpp:176 #3 0x0054eecf in OpalRawMediaStream::ReadData (this=0xa562588, buffer=0x8439c74 , size=320, leng...@0xc95fe80) at
Re: [Ekiga-devel-list] Win32 Opal datasize, please help
Le mardi 14 juillet 2009 à 18:06 +0200, Michael Rickmann a écrit : Damien Sandras schrieb: Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit : Damien Sandras schrieb: Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit : I was stuck testing the latest changes to Ekiga since about 10 days. Once a call to 5...@ekiga.net had been established windows were piling up and rendered WinXP and Win7 unusable. Today I found the reason: commit 23036 to opal trunk which coresponds to 23028 opal v3_6 and is contained in the archives needed by Ekiga 3.2.5. Attached patch fixes this for ekiga head - it just reverses the opal commit - no final solution. I am really no opal expert and a bit lost here. Why has only Win32 been hit here? Good news is that Split ekiga into an exec and helper libs - it happend at about the same time as the opal change - seems to work for Win32. Would you have a -d 4 output of the problem when it occurs without your patch? Robert will examine it. Thanks a lot. I produced the -d 4 logs with my Win32 version of current Ekiga stable, i.e. Ekiga 3.2.5, Opal 3.6.4 and Ptlib 2.6.4. So commit 23028 to opal v3_6 seems to cause the error. The logs are rather long, you find them at http://wwwuser.gwdg.de/~mrickma/ekiga/data-size-logs.tar.gz. 5...@ekiganet-ekiga-killed-stderr.txt is when calling 5...@ekiga.net. As soon as the call was accepted empty windows were piling up and I had to kill Ekiga. fritzbox-nosound-ekiga-stderr.txt is when calling my audio-only SIP-phone-box at home. Ekiga told me that it was unable to open the audio driver, exit gracefully. The programs which I used can be found at http://wwwuser.gwdg.de/~mrickma : buggy-ekiga-setup-3.2.5-release.exe fails, ekiga-setup-3.2.5-release.exe is ok with patch reversed, ekiga_build-3.2.5.tgz documents how I built the stuff. Can you try with the following patch ? The error will stay, but we will have more information and you won't have windows popping up again and again. You will also have an indication of what the problem can be. Robert thinks the problem could be in Ekiga, but due to the API change. I applied the patch, the Windows went and Win32 Ekiga is better than it ever was. The large audio delay ( 1.5 sec) is nearly gone, must have been the changes to Opal. However, as you said, the error stayed - somehow I like it, audio is next to perfect. In the logs we get now lines saying Media Patch:3096 GMAudioInputManager_ptlib Encountered error while trying to read data, read 160 instead of 320 The complete -d 4 log you find at http://wwwuser.gwdg.de/~mrickma/ekiga/ekiga-stderr.txt.gz . Attached backtrace shows what happens when calling 5...@ekiga.net and where the request for 320 comes from. Thanks for the help so far. Michael The purpose of that fix (from Robert) was to improve the audio quality. Now, even if it works, we need to determine where those 320 and 160 values come from and which one is correct (I suppose 160 is correct as it works). -- _ 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
[Ekiga-list] Google Voice Ekiga Gizmo5
I have setup an GV account to work with Gizmo5 and then forwarding all calls to Ekiga. I able to send and recieve calls but the call drops after 15 seconds every time. I forwarded the port on my wireless router. Still having trouble. My debug log attached. debug.tar.gz Description: GNU Zip compressed data ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Ekiga freezing on start-up
Hi guys, this is my first post to the list. I'm trying to set up Ekiga. I've made a few calls semi-successfully last week and am back again trying with a new headset and knowledge of aumix to better control the volume. I'm using PCLinuxOS 09. I've bought a Diamond subscription and my calls last week were long distance so I have or had that part right. I think my issue is getting the IDs right in the configuration assistant. The issue is Ekiga is freezing permanently after finishing the assistant. I assume I'm entering the wrong information but I can't figure out what. I believe my user name is: dixonpete. The password is clearly indicated from the Ekiga password reminder email. The Diamond card info seems to be clearly indicated as well: Account InformationSignup date :30.06.2009 Account Id :*xxx* PIN code :*xxx* What am I missing? Pete -- A computer consultant advocating Windows is like a doctor prescribing cigarettes. It creates a lot of extra work. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
There was such a bug (freeze at end of assistant) fixed in 3.2.5 or 3.2.4, could you use the 3.2.5 version? Eugen Pete Dixon wrote: Hi guys, this is my first post to the list. I'm trying to set up Ekiga. I've made a few calls semi-successfully last week and am back again trying with a new headset and knowledge of aumix to better control the volume. I'm using PCLinuxOS 09. I've bought a Diamond subscription and my calls last week were long distance so I have or had that part right. I think my issue is getting the IDs right in the configuration assistant. The issue is Ekiga is freezing permanently after finishing the assistant. I assume I'm entering the wrong information but I can't figure out what. I believe my user name is: dixonpete. The password is clearly indicated from the Ekiga password reminder email. The Diamond card info seems to be clearly indicated as well: Account InformationSignup date :30.06.2009 Account Id :*xxx* PIN code :*xxx* What am I missing? Pete ___ 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 freezing on start-up
I checked About, I'm using 3.2.5. My previous issue was with volume of listening and the mic. I think I've resolved those. The lock up is happening every time now. I had a look at the accounts to see if I could fix the problem without the Assistant. Turned out every time I had used it it had created another pair of accounts, some with incorrect entries from previous attempts. I deleted all but the two and corrected their entries and was able to register with both Ekiga and Diamondcard. I called a friend's phone and was able to hear him almost perfectly but my voice was nearly unrecognizable. This is with a modern Logitech headset that I just brought hom. Any suggestions on that front? I tried manipulating the Aumix settings, no dice. I wasn't any more audible last week with older headsets or mics so I don't think it's the headset. Pete Pete On Tue, Jul 14, 2009 at 3:35 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: There was such a bug (freeze at end of assistant) fixed in 3.2.5 or 3.2.4, could you use the 3.2.5 version? Eugen Pete Dixon wrote: Hi guys, this is my first post to the list. I'm trying to set up Ekiga. I've made a few calls semi-successfully last week and am back again trying with a new headset and knowledge of aumix to better control the volume. I'm using PCLinuxOS 09. I've bought a Diamond subscription and my calls last week were long distance so I have or had that part right. I think my issue is getting the IDs right in the configuration assistant. The issue is Ekiga is freezing permanently after finishing the assistant. I assume I'm entering the wrong information but I can't figure out what. I believe my user name is: dixonpete. The password is clearly indicated from the Ekiga password reminder email. The Diamond card info seems to be clearly indicated as well: Account InformationSignup date :30.06.2009 Account Id :*xxx* PIN code :*xxx* What am I missing? Pete ___ 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 -- A computer consultant advocating Windows is like a doctor prescribing cigarettes. It creates a lot of extra work. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
Pete Dixon wrote: I checked About, I'm using 3.2.5. My previous issue was with volume of listening and the mic. I think I've resolved those. The lock up is happening every time now. Could you send us the gdb backtrace, cf. http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash ? I had a look at the accounts to see if I could fix the problem without the Assistant. Turned out every time I had used it it had created another pair of accounts, some with incorrect entries from previous attempts. I deleted In order to understand the problem you need to tell us what you fill in the assistant (except the password). all but the two and corrected their entries and was able to register with both Ekiga and Diamondcard. Ok! I called a friend's phone and was able to hear him almost perfectly but my voice was nearly unrecognizable. This is with a modern Logitech headset that I just brought hom. Any suggestions on that front? I tried manipulating the Aumix settings, no dice. I wasn't any more audible last week with older headsets or mics so I don't think it's the headset. I have no idea :o( Is the echo the problem or is it another thing? Pete Pete On Tue, Jul 14, 2009 at 3:35 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: There was such a bug (freeze at end of assistant) fixed in 3.2.5 or 3.2.4, could you use the 3.2.5 version? Eugen Pete Dixon wrote: Hi guys, this is my first post to the list. I'm trying to set up Ekiga. I've made a few calls semi-successfully last week and am back again trying with a new headset and knowledge of aumix to better control the volume. I'm using PCLinuxOS 09. I've bought a Diamond subscription and my calls last week were long distance so I have or had that part right. I think my issue is getting the IDs right in the configuration assistant. The issue is Ekiga is freezing permanently after finishing the assistant. I assume I'm entering the wrong information but I can't figure out what. I believe my user name is: dixonpete. The password is clearly indicated from the Ekiga password reminder email. The Diamond card info seems to be clearly indicated as well: Account InformationSignup date :30.06.2009 Account Id :*xxx* PIN code :*xxx* What am I missing? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
Could you send us the gdb backtrace, cf. http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash? You know, I tried! I was able to follow the instructions re debugging but now when I deliberately make errors with the account information I can't get it to freeze. Go figure. Definitely part of the issue was I didn't understand that the Assistant was duplicating the accounts each time it was run. I was putting in the correct information but the system was still using the older, incorrect entries. The freezing? Maybe I put something bad in like the SIP address instead of my Ekiga username. I've made a few long distance calls successfully now. The call quality is fair to poor though. I'll keep on experimenting with the settings. I think the issue before was the MIC was set far too high blasting the callee with static. I also can't yet receive calls yet on the Toronto number I purchased. Big progress tho. Tx! Pete ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
Pete Dixon wrote: Could you send us the gdb backtrace, cf. http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash? You know, I tried! I was able to follow the instructions re debugging but now when I deliberately make errors with the account information I can't get it to freeze. Go figure. Definitely part of the issue was I didn't understand that the Assistant was duplicating the accounts each time it was run. I was putting in the correct information but the system was still using the older, incorrect entries. The Tell us how the duplicated entries appear, what do you type in the assistant. We could fix that (if it's a bug). freezing? Maybe I put something bad in like the SIP address instead of my Ekiga username. I've made a few long distance calls successfully now. The call quality is fair to poor though. I'll keep on experimenting with the settings. I think the issue before was the MIC was set far too high blasting the callee with static. I also can't yet receive calls yet on the Toronto number I purchased. Big progress tho. Tx! ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] (no subject)
Cameron K Denton wrote: Help! I recently did i fresh install of Ubuntu 9.04 and ekiga either 1.closes when I attempt to make a call with call button or 2.when I call for an echo test(double clicking it) it calls and immediately hangs up or connects with no sound. here it is ran -d 1 3.2.0 by on Unix Linux (2.6.30-020630rc2-generic-i686) with PTLib (v2.6.1) at 2009/5/4 3:33:52.130 2009/05/04 03:33:52.131 0:00.103 Ekiga SVN revision: unknown 2009/05/04 03:33:52.300 0:00.272 HalManager_dbusPopulating full interface list failed - Method getDevices with signature on interface org.freedesktop.NetworkManager doesn't exist 2009/05/04 03:33:52.301 0:00.273 Detecting V4L2 devices 2009/05/04 03:33:52.301 0:00.273 Unable to detect v4l2 directory 2009/05/04 03:33:52.371 0:00.343 OpalManRegistered endpoint with prefix pc I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root privileges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. 2009/05/04 03:33:52.543 0:00.515 OpalManRegistered endpoint with prefix sip 2009/05/04 03:33:52.548 0:00.520 OpalManRegistered endpoint with prefix sips 2009/05/04 03:33:52.551 0:00.523 OpalManRegistered endpoint with prefix h323 2009/05/04 03:33:52.552 0:00.524 OpalManRegistered endpoint with prefix h323s 2009/05/04 03:34:12.680 0:20.652 subscriber:0xb5506b90 OpalCould not find host ekiga.net 2009/05/04 03:34:12.680 0:20.652 subscriber:0xb5506b90 OpalCould not find host ekiga.net 2009/05/04 03:34:12.681 0:20.653 subscriber:0xb5506b90 OpalCould not find host ekiga.net 2009/05/04 03:34:12.681 0:20.653 subscriber:0xb5506b90 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:12.752 0:20.724 OpalCould not find host ekiga.net 2009/05/04 03:34:12.752 0:20.725 OpalCould not find host ekiga.net 2009/05/04 03:34:12.753 0:20.725 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:12.753 0:20.725 OpalCould not find host ekiga.net 2009/05/04 03:34:12.753 0:20.725 OpalCould not find host ekiga.net 2009/05/04 03:34:12.753 0:20.725 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:12.754 0:20.726 OpalCould not find host ekiga.net 2009/05/04 03:34:12.754 0:20.726 OpalCould not find host ekiga.net 2009/05/04 03:34:12.754 0:20.726 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:12.755 0:20.727 OpalCould not find host ekiga.net 2009/05/04 03:34:12.755 0:20.727 OpalCould not find host ekiga.net 2009/05/04 03:34:12.755 0:20.727 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:13.261 0:21.233 Ekiga version 3.2.0 2009/05/04 03:34:13.262 0:21.234 OPAL version 3.6.1 2009/05/04 03:34:13.263 0:21.235 PTLIB version 2.6.1 2009/05/04 03:34:13.263 0:21.235 GNOME support disabled 2009/05/04 03:34:13.264 0:21.236 Accelerated rendering support enabled 2009/05/04 03:34:13.264 0:21.236 DBUS support enabled 2009/05/04 03:34:13.264 0:21.236 GConf support enabled 2009/05/04 03:34:13.264 0:21.237 ESound support disabled 2009/05/04 03:34:24.812 0:32.784 CallSetup:0xb4914b90 OpalCould not find host ekiga.net 2009/05/04 03:34:24.812 0:32.784 CallSetup:0xb4914b90 OpalCould not find host ekiga.net 2009/05/04 03:34:24.812 0:32.784 CallSetup:0xb4914b90 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:24.812 0:32.784 CallSetup:0xb4914b90 OpalCould not find host ekiga.net 2009/05/04 03:34:24.812 0:32.785 CallSetup:0xb4914b90 OpalCould not find host ekiga.net 2009/05/04 03:34:24.813 0:32.785 CallSetup:0xb4914b90 SIPCould not find udp$ekiga.net:5060 2009/05/04 03:34:27.648 0:35.621 CallSetup:0xb4892b90 OpalCould not find host ekiga.net 2009/05/04 03:34:27.649 0:35.621 CallSetup:0xb4892b90 OpalCould not find host ekiga.net 2009/05/04
Re: [Ekiga-list] ekiga 3.2.x hates playing newmessage.wav
Chris Rankin wrote: Every time ekiga 3.2.x plays this WAV file, I get an error message saying: Error while opening audio output device SB Audigy 2 ZS [SB0353] No incoming sound will be played. The selected audio device was successfully opened but it is impossible to write data to this device. In case it is a pluggable device it may be sufficient to reconnect it. If not, or if it still is not accessible, please check your audio setup. Yes, it does play the sound too, so I'm thinking that the error is bogus. Sorry for this late reply. I created a bug report, not to forget it, http://bugzilla.gnome.org/show_bug.cgi?id=588532 . Thanks, -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] ekiga 3.2.x hates playing newmessage.wav
Chris Rankin wrote: Every time ekiga 3.2.x plays this WAV file, I get an error message saying: Error while opening audio output device SB Audigy 2 ZS [SB0353] No incoming sound will be played. The selected audio device was successfully opened but it is impossible to write data to this device. In case it is a pluggable device it may be sufficient to reconnect it. If not, or if it still is not accessible, please check your audio setup. Yes, it does play the sound too, so I'm thinking that the error is bogus. Sorry for this late reply. I created a bug report, not to forget it, http://bugzilla.gnome.org/show_bug.cgi?id=588532 . Thanks, -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
Tell us how the duplicated entries appear, what do you type in the assistant. We could fix that (if it's a bug). That's simple enough. Just run the Assistant multiple times. Pairs of Ekiga.net and Ekiga Call Out are created each time. I was varying the passwords each time to simulate the mistakes I had been making before. I think I had 10 pairs by the time I was moved to find this mailing list. Pete ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga freezing on start-up
Pete Dixon wrote: Tell us how the duplicated entries appear, what do you type in the assistant. We could fix that (if it's a bug). That's simple enough. Just run the Assistant multiple times. Pairs of Ekiga.net and Ekiga Call Out are created each time. I was varying the passwords each time to simulate the mistakes I had been making before. I think I had 10 pairs by the time I was moved to find this mailing list. Thanks, I remembered that this is a known issue, http://bugzilla.gnome.org/show_bug.cgi?id=380799 -- Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
