Julien Puydt a écrit :
Thierry Simonnet a écrit :
checking whether the Boost::Signals library is available...
yes configure:
error: Could not link against
!
Could
Thierry Simonnet a écrit :
checking whether the Boost::Signals library is available...
yes configure:
error: Could not link against
!
Could you tell me more?
Snark
__
Eugen Dedu a écrit :
What does a forum have and a mailing list does not?
I never saw the search in the mailing-list archives work...
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-deve
Eugen Dedu a écrit :
Julien Puydt wrote:
Hi,
I'm crashing ekiga in various ways, and would like to know if I'm the
only one :
1) just launch and quit, and hit an assertion in ptlib (that one looks
awfully like something I had some time ago) ;
I have not tested it extensively,
Hi,
I'm crashing ekiga in various ways, and would like to know if I'm the
only one :
1) just launch and quit, and hit an assertion in ptlib (that one looks
awfully like something I had some time ago) ;
2) launch, call for example 5...@ekiga.net, stop the call, wait a few
seconds (it has someth
Julien Puydt a écrit :
Julien Puydt a écrit :
Unfortunately, it seems some parts of ekiga just crash -- and I'm not
finished investigating and fixing those. It's the case of the roster
view and the book view.
In fact I think the problem isn't with the signals but with the
Julien Puydt a écrit :
Unfortunately, it seems some parts of ekiga just crash -- and I'm not
finished investigating and fixing those. It's the case of the roster
view and the book view.
In fact I think the problem isn't with the signals but with the smart
pointers -- the ex
Hi,
I just pushed the last part of the transition to boost : now ekiga
doesn't depend on sigc++ anymore -- but on the boost signals library.
Unfortunately, it seems some parts of ekiga just crash -- and I'm not
finished investigating and fixing those. It's the case of the roster
view and the
Julien Puydt a écrit :
Thierry Simonnet a écrit :
../lib/engine/.libs/libekiga_engine.a(opal-bank.o):opal-bank.cpp:(.text$_ZN5boost6detail12shared_countC1IN4Opal7AccountEEEPT_[boost::detail::shared_count::shared_count(Opal::Account*)]+0x5d):
undefined reference to `boost::throw_exception(std
Eugen Dedu a écrit :
Julien Puydt wrote:
Thierry Simonnet a écrit :
here is the log of yesterday and today's cross compile log for win32.
Is it possible to have information to resolve this trouble?
Yes! Now ekiga uses boost' smart pointers!
Julien, what has changed in ekiga depen
Thierry Simonnet a écrit :
../lib/engine/.libs/libekiga_engine.a(opal-bank.o):opal-bank.cpp:(.text$_ZN5boost6detail12shared_countC1IN4Opal7AccountEEEPT_[boost::detail::shared_count::shared_count(Opal::Account*)]+0x5d):
undefined reference to `boost::throw_exception(std::exception const&)'
../lib/
Thierry Simonnet a écrit :
here is the log of yesterday and today's cross compile log for win32.
Is it possible to have information to resolve this trouble?
Yes! Now ekiga uses boost' smart pointers!
Snark
___
Ekiga-devel-list mailing list
Ekiga-deve
Julien Puydt a écrit :
here is how I think we should handle incoming calls in ekiga. It has
three parts : one in the local roster, one in the opal code and another
outside.
The local roster would need to enable two categories of contacts : the
white-listed ones, and the others. That cuts the
Michael Rickmann a écrit :
I pushed all your changes in.
There's something I don't get : why do you want to download ekiga if you
already have it on disk?
Perhaps it's something you don't know about autotools : they allow
out-of-tree builds. You have your sources in $WHATEVER_DIR, but wan
Damien Sandras a écrit :
Le vendredi 26 juin 2009 à 16:10 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
What does happen if the SIP PDU tells teh phone should auto-answer and
it is not configured that way ?
First remark : the opal code in ekiga makes the decision of what it
should do
Damien Sandras a écrit :
What does happen if the SIP PDU tells teh phone should auto-answer and
it is not configured that way ?
First remark : the opal code in ekiga makes the decision of what it
should do with the call : the Ekiga::Ostracism (arg... bad name!) is
just there to help make a de
Julien Puydt a écrit :
here is how I think we should handle incoming calls in ekiga. It has
three parts : one in the local roster, one in the opal code and another
outside.
The local roster would need to enable two categories of contacts : the
white-listed ones, and the others. That cuts the
Michael Cronenworth a écrit :
It depends on what OS you are building on. The files in win32/ are meant
for Debian. For Fedora or Windows you would need to customize it a little.
I'm using debian. I already had a few problems :
- libxml' 2.6.26 isn't available anymore ;
- the openldap compilatio
Hi,
I would like to know if the win32/ directory in ekiga's master is up to
date : can I use it to test things?
Snark
PS: sending to ekiga-devel instead of Michael more directly because the
answer may be of interest to others ;-)
___
Ekiga-devel-l
Hi,
here is how I think we should handle incoming calls in ekiga. It has
three parts : one in the local roster, one in the opal code and another
outside.
The local roster would need to enable two categories of contacts : the
white-listed ones, and the others. That cuts the contacts in three
Eugen Dedu a écrit :
Eugen Dedu wrote:
Julien Puydt wrote:
Eugen Dedu a écrit :
Luca Capello wrote:
Hi Julien!
On Sun, 07 Jun 2009 18:40:43 +0200, Julien Puydt wrote:
Luca Capello a écrit :
1) Ekiga requires too much disk space:
[...]
I would like a minimal version with no GNOME
Michael Rickmann a écrit :
This is Ekigas answer in the accounts window on Linux now. With the
current git version I cannot unregister my account at ekiga.net any
longer.
Ok, that problem was much older, and I just fixed it.
Also the subcriber threads do not terminate any longer. Ekiga
need
Julien Puydt a écrit :
Julien Puydt a écrit :
Michael Rickmann a écrit :
I was wondering about that one as well. All I can say is that the
unsubscribe was not used. When studying Ekiga#s exit, I had outcommented
it by a diff the file date of which is Mo 8 Jun and the linker did not
complain
Julien Puydt a écrit :
Michael Rickmann a écrit :
I was wondering about that one as well. All I can say is that the
unsubscribe was not used. When studying Ekiga#s exit, I had outcommented
it by a diff the file date of which is Mo 8 Jun and the linker did not
complain. Now unsubscribe is called
Michael Rickmann a écrit :
I was wondering about that one as well. All I can say is that the
unsubscribe was not used. When studying Ekiga#s exit, I had outcommented
it by a diff the file date of which is Mo 8 Jun and the linker did not
complain. Now unsubscribe is called.
Eh... I came to that
Julien Puydt a écrit :
Damien Sandras a écrit :
Le lundi 15 juin 2009 à 13:07 +0200, Eugen Dedu a écrit :
Julien Puydt wrote:
Michael Rickmann a écrit :
Eugen Dedu schrieb:
Michael Rickmann wrote:
longer. Also the subcriber threads do not terminate any longer.
Ekiga needs considerably
Damien Sandras a écrit :
Le lundi 15 juin 2009 à 13:07 +0200, Eugen Dedu a écrit :
Julien Puydt wrote:
Michael Rickmann a écrit :
Eugen Dedu schrieb:
Michael Rickmann wrote:
longer. Also the subcriber threads do not terminate any longer.
Ekiga needs considerably longer to shutdown than it
Michael Rickmann a écrit :
Eugen Dedu schrieb:
Michael Rickmann wrote:
longer. Also the subcriber threads do not terminate any longer. Ekiga
needs considerably longer to shutdown than it took one week ago and does
I noticed it too...
Another point: Ekiga cannot be compiled since opal versio
Julien Puydt a écrit :
Julien Puydt a écrit :
- I couldn't call 5...@ekiga.net ; or more precisely, I asked to place
the call and ended up with an ekiga which wasn't really in a call, and
wasn't really off a call (it would only allow me to "Hang up" but that
would
Julien Puydt a écrit :
- I couldn't call 5...@ekiga.net ; or more precisely, I asked to place
the call and ended up with an ekiga which wasn't really in a call, and
wasn't really off a call (it would only allow me to "Hang up" but that
wouldn't do anything).
Eh
Michael Rickmann a écrit :
Hello everybody,
I have a new Windows version of Ekiga head based on attached minimal but
rather effective patches. you find it in my directory at
http://wwwuser.gwdg.de/~mrickma/ekiga/ . As to the patches:
1) ekiga_linkmagic.diff : It allows the linker to chose WinMa
Eugen Dedu a écrit :
Luca Capello wrote:
Hi Julien!
On Sun, 07 Jun 2009 18:40:43 +0200, Julien Puydt wrote:
Luca Capello a écrit :
1) Ekiga requires too much disk space:
[...]
I would like a minimal version with no GNOME libraries (Bonobo &
Co.), just Opal, PTlib and the min
Luca Capello a écrit :
(ekiga:1855): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion
`atom != GDK_NONE' failed
The program 'ekiga' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
Let me guess
Peter Robinson a écrit :
trying to understand the following bug :
http://bugzilla.gnome.org/show_bug.cgi?id=575887
I stumbled on a terrible question : what if the X video output had always
been broken?!
Could you please answer to that mail stating whether ekiga is using XV or X
for the video ou
Hi,
trying to understand the following bug :
http://bugzilla.gnome.org/show_bug.cgi?id=575887
I stumbled on a terrible question : what if the X video output had
always been broken?!
Could you please answer to that mail stating whether ekiga is using XV
or X for the video output on your box?
Luca Capello a écrit :
Hi there!
On Sun, 17 May 2009 22:36:03 +0200, Luca Capello wrote:
OTOH, the last time I tried it (in August 2008 at DebConf8) I was not
able to make/receive any call and since then I just gave up.
I tried again, here the results...
1) Ekiga requires too much disk spac
Eneko Taberna a écrit :
We are planning to develop a VoIP capable application (we want to start calls
and manage reception from our code), and we realized that it would be
relatively easy to use ekiga through its dbus interface. After reading some
mails and wiki pages, we found out that Ekiga
Hi,
since I didn't know about .gitignore, I used .git/info/exclude, and put
this :
*.[oa]
*~
Makefile.in
Makefile
*.lo
*.loT
*.la
*.gmo
.deps
aclocal.m4
autom4te.cache
config.*
configure
missing
mkinstalldirs
depcomp
install-sh
libtool
ltmain.sh
gnome-doc-utils.make
intltool-*
help/*/*mo
help/*
Eugen Dedu a écrit :
Julien Puydt wrote:
I had once again checked the memory management in both the contact and
presence stacks, without finding any problem.
I read the valgrind errors again and decided they meant a problem with
sigc::trackable : I changed to manual tracking, and got a big
Hi,
I had once again checked the memory management in both the contact and
presence stacks, without finding any problem.
I read the valgrind errors again and decided they meant a problem with
sigc::trackable : I changed to manual tracking, and got a big
improvement of the valgrind log.
Doe
Balu a écrit :
I want to work with the best VoIP client, so i have selected 'ekiga'.
I'm also facing the same error like '[Ekiga-devel-list] Unable to load the
source in 'Eclipse IDE(3.4.1)', Siva'.
Can you please tell me, which IDE you have used to build the source in
'Linux' OS.? I wil
Siva a écrit :
Hi,
I'm the new member of this team. I'm working with 'ekiga-3.2.0' and I
have compiled the source without any issues. I have to work the source in
'Eclipse IDE (3.4.1)'. But when imported the source 'ekiga-3.2.0', in my
project, its shows some errors. The error is mentioned be
Peter Robinson a écrit :
There's about 2 weeks until gnome 2.26.2 tarballs are due, are we
planning on targetting ekiga 3.2.1 to coincide with that release? If
so what are the current plans, it seems to me alot of the fixes for
the release are in ptlib/opal?
It would be nice, but unfortunately,
Michael Cronenworth a écrit :
Craig Southeren wrote:
Last time I tried the procedure at the following URL, it didn't even
go close to working on Fedora:
http://wiki.ekiga.org/index.php/Cross-compile_Win32
Is that this what you did? Were any changes needed?
The Makefile in Gnome SVN/Git is n
Hi,
this morning I had to apply the attached changes to ptlib's threadpool.h
to get ptlib&opal to compile.
Hope this helps,
Snark
Index: include/ptclib/threadpool.h
===
--- include/ptclib/threadpool.h (révision 22498)
+++ include/
Eugen Dedu a écrit :
- ldap settings are not migrated from 2.0.x to 3.x,
http://bugzilla.gnome.org/show_bug.cgi?id=577881
That one is now dead.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinf
Eugen Dedu a écrit :
Julien Puydt wrote:
Hi,
we've been pushing fixes since 3.2.0, and it's now time to get over
the list of things to fix for 3.2.1, and see what can be done.
I'm not citing anything specific in this mail, so we can subthread for
each problem (there are
Julien Puydt a écrit :
I'm not citing anything specific in this mail, so we can subthread for
each problem (there are a few).
The call history is broken ; this is :
http://bugzilla.gnome.org/show_bug.cgi?id=580078
on our bugzilla, and :
https://sourceforge.net/tracker/?func=detail&ai
Hi,
we've been pushing fixes since 3.2.0, and it's now time to get over the
list of things to fix for 3.2.1, and see what can be done.
I'm not citing anything specific in this mail, so we can subthread for
each problem (there are a few).
Snark
___
Michael Rickmann a écrit :
It took me some time to come up with something satisfying. Actually
there are two patches which I use now, a minor one for cleaning up
Ekiga's config files and then the ekiga.rc patch.
I pushed them in.
Snark
___
Ekiga-deve
Michael Rickmann a écrit :
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html .
At the moment I work with Ubuntu Intrepid on git master and get circular
inclusion
Julien Puydt a écrit :
Michael Rickmann a écrit :
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major
Michael Rickmann a écrit :
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major issues: Where does
GMVid
Hi,
I had noticed something strange, but could only have a look today : call
history seems to be really, really broken.
Does anyone know when that started?
Snark
PS:
http://bugzilla.gnome.org/show_bug.cgi?id=580078
___
Ekiga-devel-list mailing list
Siva P a écrit :
Hi Team,
I tried to compile the source by './configure', I'm facing an
error. The error is mentioned below:
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking f
Michael Rickmann a écrit :
Windows does not know getpwuid, getuid and the associated header file
entries as introduced by 7862. However, glib-2.0 contains the function
g_get_real_name which works for Windows. Eugen, would something like
attached patch work for Linux too?
Yes ; it's in!
Snark
_
Michael Rickmann a écrit :
First we should decide whether the resources are moved to the win32
subdirectory. With my patch the resources would remain in the base
directory. I think that files containing copyright information, as the
resources do, could live there. Additionally, my patch is not qu
Michael Rickmann a écrit :
See attached patch as
an example for how one could handle the Win32 resources.
Do you want me to commit that patch?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/e
Eugen Dedu a écrit :
Is there a way to move ekiga.rc from root to win32?
1) git mv ekiga.rc win32/
2) make sure any file referencing ekiga.rc now searches for it in win32/
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail
Julien Puydt a écrit :
Michael Rickmann a écrit :
I try to get Win32 Ekiga built and running from current SVN HEAD and
experienced difficulties in the local rooster and the echo cancellation.
1) The crash when I right click local rooster to add a new contact is
due to SVN commit 7830 to local
Michael Rickmann a écrit :
I try to get Win32 Ekiga built and running from current SVN HEAD and
experienced difficulties in the local rooster and the echo cancellation.
1) The crash when I right click local rooster to add a new contact is
due to SVN commit 7830 to local-heap.cpp . When I reverse
yannick a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Puydt a écrit :
Julien Puydt a écrit :
Oh, yes, I know that bug... but I still haven't understood it... and
the fact that I can't reproduce it doesn't help (I get other
crashes... in ptlib/opal).
I got an
Julien Puydt a écrit :
Oh, yes, I know that bug... but I still haven't understood it... and the
fact that I can't reproduce it doesn't help (I get other crashes... in
ptlib/opal).
I got an idea and pushed a would-be fix... but since I can't reproduce
that particular cra
Eugen Dedu a écrit :
Michael Rickmann wrote:
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detail&aid=2728003&group_id=204472&atid=989748
https://sourceforge.net/tracker/?func=detail&aid=2728037&group_id=204472&atid=989748
Another Win32 issue, the "crash on
Akiva Torenheim a écrit :
We would like to contribute and take part of the Ekiga devlopment.
we are two students in HUJI and we are doing this as a part of a course.
the scope should be for 2 hours for 10 weeks.
It's difficult to answer your question since you don't tell much about
what you k
Michael Rickmann a écrit :
I made a preliminary patch to ekiga/configure.ac which allows
configuration --with-libsasl2-dir=$(LIBSASL2_DIR), see attachment. This
allows Ekiga to be compiled with ldap support.
Applied, thanks!
Snarj
___
Ekiga-devel-lis
Eugen Dedu a écrit :
jamesmikedup...@googlemail.com wrote:
On Sun, Mar 29, 2009 at 9:04 PM, Eugen Dedu
wrote:
I have made progress on the firewire stuff, but I am going to take the
time to be able to link in my plugins statically, it is driving me
crazy that I cannot debug properly and the depe
jamesmikedup...@googlemail.com a écrit :
patch for a more robust ptlib
Please on ptlib's bugtracker on sourceforge.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
jamesmikedup...@googlemail.com a écrit :
crash when no contacts are available
the error handling is neede, but at least there is no segfault.
please review.
Please on the bugzilla.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
ht
All is in the title,
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Damien Sandras a écrit :
Le jeudi 19 mars 2009 à 12:43 +, Peter Robinson a écrit :
I would think depending on the GSOC project that ekiga could fall
under an number of organisations. GNOME org would def be one. A couple
of other ones that comes to mind would be XIPH if it was related to
one
Hannes De Backer a écrit :
I am a trainee. They want me to port ekiga to osx. I have about 2 months to do this.
Could u people point me at the right direction? I am reading a pdf about porting unix to osx, but it is still kinda abstract how to start on this project.
Well, first you should open
Jon Pounder a écrit :
I have the source for 2.0.12 and it defines a dbus object called
net.ekiga.calls which looks like it has what I want already called
connect, disconnect, and transfer.
>
I also have the source for 3.0.2 and it has none of that, and the same
file dbus_stub.xml and the corre
Jon Pounder a écrit :
Damien Sandras wrote:
Hi,
Le mercredi 11 mars 2009 à 23:58 -0400, Jon Pounder a écrit :
Hello list,
Forgive me if this has already been discussed in the past. I ran
across the dbus bindings tonight in the python scripts and they seem
to do what I want except for be
Damien Sandras a écrit :
Am I the only one to experience deadlocks or 'unregistered' messages
when Ekiga is registered with recent trunk releases ?
Could you be more specific?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://
Damien Sandras a écrit :
On Monday evening (March 9th at 23:59 UTC), we'll enter hard code
freeze: no source code changes are allowed without approval from the
release team, but translation and documentation should continue. Simple
build fixes are, of course, allowed without asking.
When will i
Peter Robinson a écrit :
Hi Damien,
This is nanother unstable release of the next 3.2 release of Ekiga.
I'm having troubles compiling this on Fedora 10. The problem error is below.
Cheers,
Peter
g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../lib/gmconf
-I../../../../lib/engine/framewo
Peter Robinson a écrit :
Not at the moment. The current configure line looks like
--disable-static --enable-plugins --disable-oss --enable-v4l2
--disable-avc --disable-v4l but as I'm pretty sure DC cameras are also
supported by v4l I may well disable it at some point in the future as
with libv4l
Eugen Dedu a écrit :
Peter Robinson wrote:
* The AVC plugin is not compiled anymore (the package is still there,
but will be removed soon). Please tell if you really need it. It
seems
to me that ptlib needs libraw1394-dev v1, but v1 is not available
anymore on debian unstable and very soon i
Eugen Dedu a écrit :
Julien Puydt wrote:
Eugen Dedu a écrit :
We hope to release ekiga 3.1.1 this Monday. Please note that this
release corresponds to String Freeze!
(http://live.gnome.org/TwoPointTwentyfive)
String freeze... does that mean I can't hack on ekiga right now?
You can
Eugen Dedu a écrit :
Julien Puydt wrote:
Eugen Dedu a écrit :
In services.cpp, ~ServiceCore executes pop_back(), and this function
calls the destructor of the element
(http://www.cplusplus.com/reference/stl/list/pop_back.html).
However, the refcount of the objects so deleted is not
Eugen Dedu a écrit :
In services.cpp, ~ServiceCore executes pop_back(), and this function
calls the destructor of the element
(http://www.cplusplus.com/reference/stl/list/pop_back.html). However,
the refcount of the objects so deleted is not necessarily 0 (you can
print their refcount just be
Mike Massonnet a écrit :
Le Sun, 22 Feb 2009 20:13:44 +0100,
Julien Puydt a écrit :
Eugen Dedu a écrit :
We hope to release ekiga 3.1.1 this Monday. Please note that this
release corresponds to String Freeze!
(http://live.gnome.org/TwoPointTwentyfive)
String freeze... does that mean I
Eugen Dedu a écrit :
We hope to release ekiga 3.1.1 this Monday. Please note that this
release corresponds to String Freeze!
(http://live.gnome.org/TwoPointTwentyfive)
String freeze... does that mean I can't hack on ekiga right now?
Snark
___
Ekiga
Eugen Dedu a écrit :
Julien Puydt wrote:
Eugen Dedu a écrit :
If you could fix
http://bugzilla.gnome.org/show_bug.cgi?id=570008
I have unfortunately no idea what can start a thread on exit :-(
Could you check if on your machine the following lines from engine.cpp
are executed twice?
if
Eugen Dedu a écrit :
Julien Puydt wrote:
Damien Sandras a écrit :
We are not frozen. If your code improves teh current stability of Ekiga,
H... it's not exactly that.
or if your code does not affect next release, it can be pushed.
well, I do hope it will affect it for the b
Damien Sandras a écrit :
We are not frozen. If your code improves teh current stability of Ekiga,
H... it's not exactly that.
or if your code does not affect next release, it can be pushed.
well, I do hope it will affect it for the better!
However, I would be happy if developers could
I have some experimental code in my personal branches, which I don't
dare committing since we're frozen.
When will development start again?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga
Eugen Dedu a écrit :
Please apply the attached patch, which adds the kde-core directory to
the tarball.
Wait! We already have lib/engine/components/kde/ -- the code you're
trying to link is dead code!
Let's just kill it.
Snark
___
Ekiga-devel-list
Damien Sandras a écrit :
Le mercredi 11 février 2009 à 23:44 -0600, Michael Cronenworth a écrit :
-If I enable LDAP, SASL support is requested. Two SASL function calls
are being made when support is not available in mingw. I spent a few
hours trying to get a libsasl2.dll but it was fruitless. Cy
Audio input doesn't work correctly ; if you set the audio input to audio
test (and the rest using your usual pwlib devices), you'll hear a sound,
not very good.
What you should have heard is the following :
gst-launch-0.10 audiotestsrc !
audio/x-raw-int,rate=8000,channels=1,width=16 ! alsasink
Julien Puydt a écrit :
- video in a call should work, though I saw crashes with goom (which I
haven't debugged yet) ;
I reported that goom crash upstream as :
http://bugzilla.gnome.org/show_bug.cgi?id=570761
Snark
___
Ekiga-devel-list mailing
Let me give more information about sound output :
This is an example of what ekiga outputs when playing a sound event --
and it does play correctly :
Pipeline: appsrc is-live=true name=ekiga_src !
audio/x-raw-int,rate=44100,channels=2,width=16,depth=16,signed=true,endianness=1234
! volume na
Peter Robinson a écrit :
I'm not sure about the status of GStreamer. Snark, can you comment on
this ?
It compiles and I can get a list of devices like audio in/out and a
video picture (my lappie doesn't have webcam and haven't got around to
testing 3.1 on my netbook).
I did comment on it pret
Wayne a écrit :
I have some questions about the text chat in gnomemeeting(1.0.2) and
openh323(major version 1 and minor version 13).
gnomemeeting 1.0.2 !?
Are you joking!? The software is now named "ekiga" and is up to version
3.0.2 !
Snark
___
Ek
Julien Puydt a écrit :
Eugen Dedu a écrit :
Also, Snark, do you think we will have gstreamer code in release
status for gnome next release?
I recently got interesting feedback from the gstreamer developpers, but
we still have :
http://bugzilla.gnome.org/show_bug.cgi?id=565202
which is a bug
Eugen Dedu a écrit :
Snark, do you agree to remove API:: pages (see
http://wiki.ekiga.org/index.php/Special:Allpages)? If you still need
them, it is better to put them in one place and we will link to them
from one of the wiki pages.
Looking at the API::Addressbooks page : it's obsolete.
Th
Eugen Dedu a écrit :
Also, Snark, do you think we will have gstreamer code in release status
for gnome next release?
I recently got interesting feedback from the gstreamer developpers, but
we still have :
http://bugzilla.gnome.org/show_bug.cgi?id=565202
which is a bug in ekiga -- and which I'
Volker Bradley a écrit :
More of the hate-filled rhetoric that this world does not need.
Can this contributor be removed from this list?
He did NOT send this mail. That is a forged mail!
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.
Anoop C. Suku a écrit :
There was provision for text chat
I don't understand what "provision for text chat" means -- ekiga still
makes it possible to exchange text messages with people : right click on
them in the contact list and choose the right action.
Snark
_
301 - 400 of 663 matches
Mail list logo
