Re: [Ekiga-list] a few problems with 3.0.1

[Palo S. <palos post sk>]

> 
> Did you try installing the ptlib-plugins-v4l (or some similar name)
>  package which provides the V4L plugin driver?

I compiled from source, but I have now sorted this 
out - it was caused by opal configure script which 
only enabled v4l2 support by default - simply 
providing --enable-v4l did the trick... shame on me,
I  should have checked this before! My only excuse
is that this manual specification was not required 
when I compiled Ekiga previously...
Update: now I see that in the meantime Eugen already 
has mentioned this too!

> 
> > 2. The presence indication does not work for any
> > of my ekiga contacts, including echo test and
> > conference room - all are displayed without any
> > presence indication (ie the same as \\\\\\\"IPBX\\\\\\\"
>  > contacts on this screenshot:
>  > http://blog.ekiga.net/?p=61)
> 
> Are your registered to ekiga.net ?

Yes, of course. I am registred, I can make a call
(now including video part!) etc. Just no presence
indication. Is there another option required at
compilation time? Or is it a bug?

> 
> > 3. Microphone does not work with \\\\\\\"Default (PTLIB/ALSA)\\\\\\\",
> > however it works with \\\\\\\"HDA Intel (PTLIB/ALSA)\\\\\\\"
>  > specified...
> 
> Then that works...

In principle yes but is it ok if default does not work? 
What could be the reason?

> 
> I\\\'m annoyed by point 5 -- but I\\\'m not sure the bug is on our side.

I was thinking it was not on Ekiga side. However now 
I am bit puzzled because I just tested that other GTK+ 
applications work fine. I am posting the error message:

The program \\\'ekiga\\\' received an X Window System error.
This probably reflects a bug in the program.
The error was \\\'BadAlloc (insufficient resources for operation)\\\'.
  (Details: serial 42 error_code 11 request_code 141 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x440007b unexpectedly destroyed

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400080 unexpectedly destroyed
^@
(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400083 unexpectedly destroyed

(ekiga:3734): Gdk-WARNING **: GdkWindow 0x4400084 unexpectedly destroyed

(ekiga:3734): GLib-GObject-WARNING **: invalid uninstantiatable type `\\\' in cast to `GtkWidget\\\'

(ekiga:3734): GLib-GObject-WARNING **: invalid uninstantiatable type `\\\' in cast to `GObject\\\'

(ekiga:3734): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)\\\' failed

Segmentation fault


It seems that the last error message actually changes,
I can also get
(ekiga:3916): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0\' failed
(ekiga:4687): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)\' failed
Gtk:ERROR:(gtkwidget.c:7942):gtk_widget_real_map: assertion failed: (GTK_WIDGET_REALIZED (widget))
Aborted

etc

I am not sure how much useful this is and what to do
to get a better error description? -d 4 does not seem
to be useful and I did not succeed to run ekiga with
gdb



__________
Svetova kniznica SME - literarne klenoty 20. storocia - http://knihy.sme.sk/