Palo S. a écrit :
> There is just too much
> competition in VOIP under Linux
You mean you know other VoIP apps which do H323+SIP in audio+video with
support for a wide range of devices and good stability under gnu/linux?
Snark
___
Ekiga-devel-list m
Julien Puydt a écrit :
> I committed preliminary call history code today. It won't make the
> contacts appear in the addressbook yet, but will print some data in the
> console.
I committed more complete call history code today ; as far as I know,
the last missing piece is
Julien Puydt a écrit :
> Julien Puydt a écrit :
>> I committed preliminary call history code today. It won't make the
>> contacts appear in the addressbook yet, but will print some data in the
>> console.
>
> I committed more complete call history code today
Hi,
I was investigating the problems with gmconf-glib when I met this crash:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb45e7b90 (LWP 32657)]
GMAccountsEndpoint::Main (this=0x85f0e70) at
endpoints/accountshandler.cpp:131
131 if (accounts_iter->data) {
(g
Carlos Hernandez a écrit :
> Where can I donwload Ekiga 3.0 for windows?, can't find the link in ekiga.org
3.0 isn't released.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Hi,
I had a crash through the following code in opal-gmconf-bridge.cpp:
GMManager::VideoOptions options;
manager.get_video_options (options);
options.maximum_received_bitrate = gm_conf_entry_get_int (entry);
manager.set_video_options (options);
The reason for the crash is that
Matthias Schneider a écrit :
> However I do not know if this is the correct place to do this. Perhaps there
> should be a centralized place to check for value ranges and reset to defaults,
> perhaps even using the schemas.in.in as input for the defaults in case a key
> does not exist?
>
> In case
Matthias Schneider a écrit :
> make sure you have dbus properly installed and that rights have been correctly
> set, it seems dbus is detected at compile time but there seems to be some
> trouble at runtime. You can also try to disable dbus at compile time.
> Matthias
Those are only warnings : the
Matthias Schneider a écrit :
> I prefer the bridge if its in the object or the specific gmconf, since if I
> have
> to do all these checks in the object itself, the already complicated code will
> look even more complicated. And the gmconf-bridge does not do anything really,
> apart from those che
Damien Sandras a écrit :
> http://www.ietf.org/internet-drafts/draft-kaplan-sip-four-oh-00.txt
April fool, I would say ;-)
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
clients/stun.cpp: In member function 'virtual void GMStunClient::Main()':
clients/stun.cpp:337: error: 'class GMManager' has no member named
'GetCurrentAddress'
With svn snapshots one hour old :-/
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-li
Damien Sandras a écrit :
> I forgot to commit the stun.cpp file yesterday.
> I just did it.
Thanks!
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Hi,
again, there is a problem with the bridge : it gets something from
gmconf, doesn't check before use, and triggers a floating point exception.
I'm not sure whether the issue is in ekiga or in opal though :
0x08132c71 in GMManager::set_video_options (this=0x8303238,
[EMAIL PROTECTED]) at
Matthias Schneider a écrit :
> Quoting Damien Sandras <[EMAIL PROTECTED]>:
>
>> Le vendredi 11 avril 2008 à 11:26 +0200, Matthias Schneider a écrit :
>>> Quoting Julien Puydt <[EMAIL PROTECTED]>:
>>>
>>>> Hi,
>>>>
>&
[EMAIL PROTECTED] a écrit :
> I am using this tutorial to compile Ekiga.
> http://wiki.ekiga.org/index.php/Compile_your_own_SVN_version_of_Ekiga_on_Ubuntu
>
> Someone can help me? Here is the command line output when Ekiga Crash,
You did notice that it was SVN, hence unstable, not for any random
yannick a écrit :
> Hi,
>
> fabrice called me this morning (up to date Ekiga SVN on both sides)
>
> he had a crash and me too. here is mine:
> http://pastebin.ca/982088
>
> Have a nice day ;)
Did someone hack on pstring this night?
Snark
___
Ekiga-de
Julien Puydt a écrit :
> Did someone hack on pstring this night?
Did you both recompile pwlib, opal and ekiga freshly this morning?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-de
Damien Sandras a écrit :
> No, it looks weird.
Indeed.
> The code is this one :
> PString token;
> endpoint.SetUpCall ("pc:*", dial_uri.c_str (), token);
I saw ; may I just ask why we extract the C string from a std::string
before calling a C++ method?
Snark
___
Damien Sandras a écrit :
> Le samedi 12 avril 2008 à 11:26 +0200, Julien Puydt a écrit :
>> Damien Sandras a écrit :
>>> No, it looks weird.
>> Indeed.
>>
>>> The code is this one :
>>> PString token;
>>> endpoint.SetUpCall ("pc:*
Damien Sandras a écrit :
> I'm using code like this to ensure sane values:
> SetAudioJitterDelay (PMAX (min_val, 20), PMIN (max_val, 1000));
That is wrong : you're protecting the call to SetAudioJitterDelay, not
the method itself!
If I have a method which receives an integer which shouldn't be z
Damien Sandras a écrit :
> The problem was that I dial from a separate thread and the URI is passed
> as a const reference instead of using a copy of the string. But the
> original variable is already destroyed when the thread begins its work
> as that work is done in a separate thread!
>
> It sho
Hi,
I got a crash ; I suppose ekiga doesn't like when run on a non-networked
box...
Snark
PS: here is the trace:
Thread 17 (Thread 0xb3aa0b90 (LWP 19608)):
#0 0xb6af3209 in PList::front ()
from /usr/lib/libpt_linux_x86_r.so.2.3-beta0
#1 0xb6aefed4 in PSTUNClient::GetNatType ()
from /u
Damien Sandras a écrit :
> If it is a crash in PTLIB or OPAL, it should be reported on their
> bugtracker.
I see there have been quite a few changes since saturday : I'm
recompiling everything again to check.
Snark
___
Ekiga-devel-list mailing list
Eki
Peter Robinson a écrit :
> Just a fyi on the building ekiga as a rpm with the current Fedora 9.
Wouldn't you use a very recent g++ which has tighter include
requirements than previous versions?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@
Hi,
I just found a big problem (and fixed it) in the configuration handling
on non-gconf installations (which includes win32).
I'd like our dear win32 testers to tell me if things improved.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnom
Peter Robinson a écrit :
Does MacOS X come with a built-in SIP app, like it comes with a
built-in email app?
>>> Yes, iChat, but its network is closed. :(
>> I've read that SIp is only used to established the RTP session But it can't
>> register to any SIp server I guess ?
>>
>> So it's n
Here it is :
/usr/include/opal/opal/rtpconn.h: In copy constructor
‘OpalRTPSessionManager::OpalRTPSessionManager(const
OpalRTPSessionManager&)’:
/usr/include/opal/opal/rtpconn.h:160: warning: base class ‘class
PObject’ should be explicitly initialized in the copy constructor
/usr/include/opal/o
Martin Ebourne a écrit :
> Fix trunk compilation on Fedora 9.
How does it compare to the patch already here :
http://bugzilla.gnome.org/show_bug.cgi?id=533266
(which I was going to apply when your mail arrived)
Snark
___
Ekiga-devel-list mailing list
Ek
Matthias Apitz a écrit :
> El día Tuesday, May 20, 2008 a las 02:28:48PM +0200, Damien Sandras escribió:
>
>> Le mardi 20 mai 2008 à 14:25 +0200, Matthias Apitz a écrit :
>>> Hello,
>>>
>>> I've the following problem with the new copiled ekiga; it says on start
>>> on sdterr:
>>>
>>> "Bad NAT type
Martin Ebourne a écrit :
> On Mon, 2008-05-19 at 23:23 +0100, Peter Robinson wrote:
>> ../../../../lib/engine/presence/local-roster/local-presentity.cpp:272:
>> error: no matching function for call to
>> 'find(std::_Rb_tree_const_iterator> std::char_traits, std::allocator > >,
>> std::_Rb_tree_cons
Hi,
I have a hard time compiling ptlib+opal+ekiga those days : since I
upgraded my libavcodec-dev package, avcodec.h is to be found in :
/usr/include/ffmpeg/libavcodec/avcodec.h
but is searched in :
libavcodec/avcodec.h
ffmpeg/avcodec.h
in fact, if the configure script were doing things right, i
Matthias Schneider a écrit :
> Quoting Julien Puydt <[EMAIL PROTECTED]>:
>
>> Hi,
>>
>> I have a hard time compiling ptlib+opal+ekiga those days : since I
>> upgraded my libavcodec-dev package, avcodec.h is to be found in :
>> /usr/include/ffmpeg/
Julien Puydt a écrit :
> Matthias Schneider a écrit :
>> Quoting Julien Puydt <[EMAIL PROTECTED]>:
>>
>>> Hi,
>>>
>>> I have a hard time compiling ptlib+opal+ekiga those days : since I
>>> upgraded my libavcodec-dev package, avcodec
Do we have win32 ekiga snaps handy for that :
http://wiki.winehq.org/DogfoodChallenge
?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Matthias Schneider a écrit :
> in my opinion all this dir stuff sucks a lot. I have added your path to the
> list of searched dirs, thinking that this way forward will cost less boring
> and useless work to me than the other possibilities. In case you feel like it
> you could still report this a
Matthias Schneider a écrit :
> could you please try again?
As I told on IRC : ok.
(but I want it visible in the archives that you got it)
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-dev
When things are passed-by-values, "const" is useless...
Snark
diff -ur opal.orig/h323/h323con.h opal.patched/h323/h323con.h
--- opal.orig/h323/h323con.h 2008-06-06 15:26:49.926507140 +0200
+++ opal.patched/h323/h323con.h 2008-06-06 15:34:12.302396814 +0200
@@ -1859,7 +1859,7 @@
0 - Just t
Hi,
I fixed quite a few warnings, but there are still a few annoying ones :
A series of ambiguous 'else', where I'd rather see the code author add
braces, to be sure :
videooutput-manager-common.cpp:159
videooutput-manager-common.cpp:171
xwindow.cpp:749
xwindow.cpp:868
The compiler suggests par
Hi,
I have fixed a few bugs in the gtk-only version lately ; are there known
issues with that version since then?
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Conrad Beckert a écrit :
Hi Damien,
It was you !!!
It is a shame I did not know it was you, I would have drunk a beer with
you ;-)
Well, I was in a hurry that day. But next time you're in Berlin, we should do
this.
I see yannick answered you, but :
- I'm not sure the gtkonly version actuall
Julien Puydt a écrit :
I have fixed a few bugs in the gtk-only version lately ; are there known
issues with that version since then?
No issue? The gtk-only is perfect?
Is there some place we have ready-to-download win32 packs?
Snark
___
Ekiga-devel
Eugen Dedu a écrit :
The "Display video from camera" button does not get the saved value from
the init file. To reproduce: start ekiga, suppose the video is on.
Press the button, the video turns off. Stop ekiga. Restart ekiga. The
video is seen but the button is off.
It's in! I only remov
Eugen Dedu a écrit :
Mauricio Teixeira wrote:
Hey guys,
I'm trying to build the 20080611 snapshot, and I get the following error:
make[3]: Leaving directory `/builddir/build/BUILD/ekiga/src'
make[2]: Leaving directory `/builddir/build/BUILD/ekiga/src'
Making all in po
make[2]: Entering direct
Anacharsis a écrit :
I've tried to compile ekiga on my notebook running Linux and I got the
following message:
Which version?
I do not see any reason why should I install LDAP. Are there any
chances for --disable-ldap configure option to appear in future
versions?
You should install LDAP t
Anacharsis a écrit :
Which version?
2.0.12
You should install LDAP to find other users with whom to connect.
Yes, I know, but I do not need to: we use h.323 inside LAN and we know
everybody by IP address (static IPs, no DHCP).
2.0.12 doesn't compile without LDAP... and I have to check wh
Julien Puydt a écrit :
2.0.12 doesn't compile without LDAP... and I have to check whether 3.0
will.
It's possible to compile 3.0 without LDAP.
Snark
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailma
Hi,
I would need a way to setup ekiga with something in front of it, which
will send presence/status information on a pretty high rate.
The goal is to trigger the crash in sigc::trackable much, much more
easily, to kill it.
I was thinking a pseudo-server could do the trick (ie: a false serv
Damien Sandras a écrit :
Le lundi 28 juillet 2008 à 21:41 +0200, Julien Puydt a écrit :
Hi,
I would need a way to setup ekiga with something in front of it, which
will send presence/status information on a pretty high rate.
The goal is to trigger the crash in sigc::trackable much, much more
Damien Sandras a écrit :
Le mardi 29 juillet 2008 à 10:05 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
Le lundi 28 juillet 2008 à 21:41 +0200, Julien Puydt a écrit :
Hi,
I would need a way to setup ekiga with something in front of it, which
will send presence/status information on
Julien Puydt a écrit :
Running :
sipp -sn uas -aa
is supposed put sipp in server mode (-sn uas), and answer ok to
everything (-aa)...
Not sure uas is what I thought it was...
I have to dig further.
Snark
___
Ekiga-devel-list mailing list
Ekiga
Jan Schampera a écrit :
due to some discussions about this topic in chat and on the bugzilla,
here the official discussion thread ;-)
Which GTK+ to choose as platform for Ekiga 3.0?
My suggestion is 2.12, since it's relatively mature now, and part of
Debian Lenny.
I vote for 2.12.
Notice
Mauricio Teixeira a écrit :
Mauricio Teixeira wrote:
Hi guys,
I was trying to build ekiga-2.9.90, and I got this error:
codecsbox.cpp: In function 'void codecs_box_init(CodecsBox*)':
codecsbox.cpp:476: error: 'gtk_widget_set_tooltip_text' was not declared
in this scope
Well... At the end, I
Christopher Warner a écrit :
Yeah I remember playing around with the quicktime stuff a very long
time ago and I hit some hurdles with it because of my webcam at the
time. I was using some driver interface called MaCam which seems to be
the default driver for "other" webcams not associated with A
yannick a écrit :
Le jeudi 11 septembre 2008 à 07:13 +0200, yannick a écrit :
Hello,
Compiling Ekiga on Ubuntu Gutsy (september 2007), i've the following
error. Build on more recent versions of ubuntu seems to compile right.
Hi,
The error seems to be g_async_queue_new_full was introduced in
Jared D. McNeill a écrit :
The attached patch (against 20080907 snapshot) enables detection of
NetBSD on configure.ac. Apart from this change ekiga requires no further
changes to run on this platform.
It's in, thanks!
Snark
___
Ekiga-devel-list mail
Damien Sandras a écrit :
A mix of both :
- ekiga depends on libopal and libpt
- libopal depends on libpt
- libpt depends on pt plugins
I disagree :
* ptlib could be used without plugins ;
* opal too probably (it provides its own plugins, doesn't it?) ;
* but ekiga definitely needs the plugins.
Damien Sandras a écrit :
OPAL and PTLIB have been branched for the Ekiga 3.00 release.
Please use the new branches and not SVN TRUNK anymore.
Is it possible to do the same for ekiga too?
I have a few patches for after 3.0 already.
And a few ideas too.
Snark
_
Damien Sandras a écrit :
Le mercredi 17 septembre 2008 à 13:39 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
OPAL and PTLIB have been branched for the Ekiga 3.00 release.
Please use the new branches and not SVN TRUNK anymore.
Is it possible to do the same for ekiga too?
I have a
Damien Sandras a écrit :
Le mercredi 17 septembre 2008 à 15:05 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
Le mercredi 17 septembre 2008 à 13:39 +0200, Julien Puydt a écrit :
Damien Sandras a écrit :
OPAL and PTLIB have been branched for the Ekiga 3.00 release.
Please use the new
Peter Robinson a écrit :
I think uPnP support would be a pretty reasonable user facing change.
While not bling, would make it much easier for a lot of people.
No idea on that one :-)
And the move to the GTK Ridley update (deprecation of use of older libraries).
We already pushed our demands
Peter Robinson a écrit :
Not so much push it up higher (I think we've moved to 2.12?) but
rather move some of the libgnome related stuff to the new GTK features
instead
http://live.gnome.org/ProjectRidley
I think we still use gnome_program_init, but the rest is gone already.
Snark
___
Damien Sandras a écrit :
We should remove bonobo. I had removed all the includes. The problem is
that it still is linked through libgnome or libgnomeui, thus we can not
get rid of it.
Let's get rid of libgnomeui & libgnome then : they're supposed to die
anyway.
Snark
Peter Robinson a écrit :
We should remove bonobo. I had removed all the includes. The problem is
that it still is linked through libgnome or libgnomeui, thus we can not
get rid of it.
Let's get rid of libgnomeui & libgnome then : they're supposed to die
anyway.
The only reason why we keep them
Jan Schampera a écrit :
Since some users reported buggy behaviour, I tested some 5 minutes:
- EVO: Add contact, enter Video URL: Nothing shows up in Ekiga
- EVO: Add contact, enter Businessphone Number: Shows up in Ekiga (as
Phone)
- Ekiga: Edit existing empty contact, add Video URI, Shows up a
Hi,
I committed very basic XCAP+resource-list to svn this afternoon. It's
not complete in any way, but it's still there.
It currently uses libsoup for the XCAP part.
You have to use --enable-xcap to enable it.
It will by default try to load the resource list at the uri
http://localhost/test
Hi,
I would really like to progress on that bug : I have ideas for the
XCAP/resource-list code, but don't dare going through before I have a
reasonable way to manage memory in it (the RL::Cluster is going to be
pretty complex...).
It would be nice if you read the code (and the example code).
Jan Schampera a écrit :
Julien Puydt wrote:
It would be nice if you read the code (and the example code).
I see nothing wrong with the code - though, I'm not really a C++ guy
(but I understand it, of course).
What do you worry about?
I'm worried about the code not being nice
Epelde Gorka a écrit :
So, I've found that for a videoconference scenario, Ekiga is an interesting
option. Right now, our platform is running on windows, so I'm interested in
having a stable version of Ekiga for windows and having a working
cross-building environment.
We do already build ekiga
Hi,
I implemented basic XCAP+resource-lists code in trunk yesterday evening.
I would like to find several things :
(1) sites to connect to and check if the code behaves well, for testing
and compatibility to the server purposes ;
(2) sample resource-lists documents as created by other client
Peter Robinson a écrit :
Quick query, is there a reason why this release has added a direct
dependency to speex over the old release which only had the dep in
opal?
Opal's embedded version was very very old, if I remember well.
Snark
___
Ekiga-devel-
Julien Puydt a écrit :
(2) I have seen only a document created by eyebeam (and we're already
only partially compatible...).
Ok, here is an example of what I am looking for -- this is a
resource-lists as made by ey
Hi,
I have still no news from anyone about the way other clients than
eyebeam store their resource-lists.
I still worked on the issue :
- I fixed a big memory leak in the current XCAP code ;
- I managed (five minutes ago after a very long fight) to get openXCAP
up and running on my box -- and
yannick a écrit :
Simply put, I do believe XCAP technology is one way to reach the social
level IM client or VoIP client is meant to be. The goal is not only to
get working communication (text, audio and video and...) between 2
peers, it is to have a tool to manage/organise/deal with groups of
pe
Heiser Michael a écrit :
I downloaded the ekiga 3.01 sources from the homepage an generated a
documentation via Doxygen. The documentation seem to be only about the
Ekiga-Engine.
So where can I find the code for DBUS handling to have a look at it?
The DBUS code in ekiga 3.x is mostly dead at
Damien Sandras a écrit :
Without feedback :
- do we consider that people are too lazy to test and that no test has
been done
- do we consider that it works well
?
Le mercredi 29 octobre 2008 à 23:19 +0100, yannick a écrit :
It's been less than a week!
I have personally been mostly *offline*
Hi,
I committed log-printing code in ekiga -- and I need help to make sense
of it. This is very directly related to the crash-on-exit bug which
cripples ekiga since too long.
The problem is found in that piece of log :
void on_heap_updated(gmref_ptr, gmref_ptr,
void*), 0xb5602144 -> 11
GmR
Damien Sandras a écrit :
Multithreading ?
Perhaps you could check the thread name. What would be nice to do, is
being able to monitor the ref count value in real time for that object.
The lines of code which give that are next to each other : they can't be
from different threads. And what you
Hi,
here is the source of a backtrace dumper to follow each and every
gmref_inc/gmref_dec in ekiga (and can print "THIS:" for objects of
interest though that is commented out).
It uses nemiver-as-a-lib (needs svn from nemiver and snapshot from gdb,
and the target program can't print anything
Julien Puydt a écrit :
the crash-on-exit bug which cripples ekiga since too long.
I have no clue why. Help!
If :
- I compile out evolution-data-server ;
- I disconnect forcefully the GUI from the engine in the
roster&addressbook windows (which makes ekiga unusable...) ;
- I put back
Julien Puydt a écrit :
sigc::bind_functor<0,
sigc::bound_const_mem_functor2gmref_ptr, gmref_ptr, sigc::nil>,
gmref_ptr const&, gmref_ptr const&>,
gmref_ptr, sigc::nil, sigc::nil, sigc::nil, sigc::nil,
sigc::nil, sigc::nil> >
I banged my head to the wall a few tim
Eugen Dedu a écrit :
Julien Puydt wrote:
Damien Sandras a écrit :
Multithreading ?
Perhaps you could check the thread name. What would be nice to do, is
being able to monitor the ref count value in real time for that object.
The lines of code which give that are next to each other : they
Hi,
after days of fight, I managed to get a simpler program to crash like
ekiga yesterday evening. This night, I made that program simpler.
You'll find attached what's needed to reproduce the crash. You'll need
to unpack the tarball somewhere, and modify the EKIGA_DIR line to point
to your f
Julien Puydt a écrit :
Hi,
after days of fight, I managed to get a simpler program to crash like
ekiga yesterday evening. This night, I made that program simpler.
You'll find attached what's needed to reproduce the crash. You'll need
to unpack the tarball somewhere, and modif
Julien Puydt a écrit :
There is definitely a problem with gmref_ptr, but I still don't know
which :-/
I kicked all uses of gmref_inc/gmref_dec out of the GUI, and it doesn't
crash anymore. Sigh...
Snark
___
Ekiga-devel-list mailing
Heiser Michael a écrit :
Is it possible to find some documentation about the DBUS-Integration for Ekiga
and perhaps some code snippets?
In the sources of Ekiga itself I only found the HAL-DBUS integration. But I
want to know how to integrate selfwritten DBUS-Code into Ekiga.
For 2.0.x, the
Eugen Dedu a écrit :
For gstreamer support I must install libgstreamermm-0.10-dev.
No, I used gstreamer only. But GstApp isn't packaged by debian because
they don't consider it stable enough.
You should recompile gstreamer-plugins-bad yourself.
Sorry, I don't have simpler : the current situ
Eugen Dedu a écrit :
The reason is that gtk_file_chooser_button_new_with_backend is
deprecated, cf.
http://library.gnome.org/devel/gtk/stable/GtkFileChooserButton.html#gtk-file-chooser-button-new-with-backend
Unfortunately, the API does not inform about the function to be used in
this case.
Julien Puydt a écrit :
Eugen Dedu a écrit :
The reason is that gtk_file_chooser_button_new_with_backend is
deprecated, cf.
http://library.gnome.org/devel/gtk/stable/GtkFileChooserButton.html#gtk-file-chooser-button-new-with-backend
Unfortunately, the API does not inform about the function to
Peter Robinson a écrit :
Saw your blog on using gtk_timeout_add_seconds
Not sure why we only depend on glib 2.8 when we depend on gtk+ 2.12.
I'm pretty sure gtk 2.12 depends on glib 2.14 anyway so its a bit of a
mute point and you can probably increase the depend on glib to what
ever gtk 2.12 re
Eugen Dedu a écrit :
Julien Puydt wrote:
Julien Puydt a écrit :
Eugen Dedu a écrit :
The reason is that gtk_file_chooser_button_new_with_backend is
deprecated, cf.
http://library.gnome.org/devel/gtk/stable/GtkFileChooserButton.html#gtk-file-chooser-button-new-with-backend
Unfortunately
Hi,
I'm having issues compiling opal when libavcodec-dev is installed on my
system :
h263-1998.cxx: In member function ‘virtual bool
H263_RFC2190_EncoderContext::Open()’:
h263-1998.cxx:453: error: ‘struct AVCodecContext’ has no member named
‘rtp_mode’
h263-1998.cxx:460: error: ‘CODEC_FLAG_H263
Hi,
this evening didn't start well, and doesn't go on well either :
assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock
failed, file ptlib/unix/tlibthrd.cxx, line 1304
Assertion fail: Function pthread_mutex_lock failed, file
ptlib/unix/tlibthrd.cxx, line 1304
Does that rem
yannick a écrit :
I just saw Gnome has a build bot:
http://build.gnome.org/
People responsible for that can be found at the end of this document:
http://live.gnome.org/BuildBrigade
Sadly it does not build Ekiga correctly yet.
Maybe we can get in touch with those people ?
They can't do anythi
Peter Robinson a écrit :
FAQ, TODO files should be removed, they are nearly empty.
Rather than removing them maybe just put a reference in them to the
FAQ and ToDo lists on the website/wiki so people can find the current
version if they're looking for it.
Isn't the presence of TODO required b
Damien Sandras a écrit :
Le dimanche 04 janvier 2009 à 15:35 +0100, Eugen Dedu a écrit :
Damien Sandras wrote:
Le samedi 03 janvier 2009 à 20:29 +0100, Eugen Dedu a écrit :
Hi,
CELT is not shown in the codec list (current trunk), is it normal?
(G722 is shown.)
Did you compile it ?
That's
Peter Robinson a écrit :
There's also a heap of the following errors which I don't think are
fatal but probably need to be added to a todo list somewhere.
gnome-doc-utils.make:160: wildcard $(_DOC_ABS_SRCDIR: non-POSIX variable name
gnome-doc-utils.make:160: (probably a GNU make extension)
help/
Andrea a écrit :
The only issue in 3.1.0 is that ekiga crashes upon exit with
assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock
failed, file
ptlib/unix/tlibthrd.cxx, line 1304
Assertion fail: Function pthread_mutex_lock failed, file
ptlib/unix/tlibthrd.cxx, line 1304
Hi,
I committed some gstreamer work yesterday. The short summary is that it
doesn't work, but is better at it.
The longer version is :
- for video input, it works pretty well -- the main problem is an
initialization bug in the video input code, which means that if you
enable video preview a
Eugen Dedu a écrit :
I have the latest gstreamer (from exp, 0.10.9.3-1)
(gstreamer-plugins-base-0.10 >= 0.10.21.3 gstreamer-interfaces-0.10)
Uh... Eugen, 0.10.9.3-1 is older than 0.10.21.3... so it's normal you
don't have what it takes!
You should try :
$ apt-cache show gstreamer0.10-plugin
Eugen Dedu a écrit :
Ah, I thought that it's the version of -plugins-bad which is taken...
The point is : as long as it was in -bad, then distributions like debian
didn't want to package it... now that it moved in -base, it gets packaged!
I have installed gstreamer dependencies and the comp
1 - 100 of 663 matches
Mail list logo
