Re: [Ekiga-list] a few problems with 3.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hmm .. I'm getting that with 3.0.0 On powering up can I open xawtv successfully as root > Tohunga:~# xawtv > This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.26-1-686) > xinerama 0: 1280x1024+0+0 > /dev/video0 [v4l]: no overlay support > v4l-conf had some trouble, trying to continue anyway > ioctl: VIDIOCMCAPTURE(frame=0;height=120;width=160;format=7): > Invalid argument > ioctl: VIDIOCMCAPTURE(frame=0;height=264;width=352;format=5): > Invalid argument > scroll by 24length 150shown 0.00top 0.250004 => 0.282004 > ioctl: VIDIOCMCAPTURE(frame=0;height=264;width=352;format=5): > Invalid argument > ioctl: VIDIOCMCAPTURE(frame=0;height=264;width=352;format=5): > Invalid argument although the image is black and an orange-hued white it is a real-time video image. Following Eugen Dedu .. > Note that v4l is disabled by default in ptlib. To enable it, > execute > "./configure --enable-v4l' in ptlib. I enabled v4l in ptlib, recompiled Ekiga 3.0.0, and set up executable permissions on /dev/video0 > Tohunga:/dev# ls -la video** > crwxrwxrwx 1 root video 81, 0 2008-10-23 11:52 video0 However when starting Ekiga 3.0.0 and trying to "display images from the camera device" I get a pop-up message saying > Error while accessing video device /dev/video0 > There was an error while opening the 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 permissions and make > sure that the appropriate driver is loaded. > > A moving logo will be transmitted during calls. Notice that you can > always transmit a given image or the moving logo by choosing > "Picture" as video plugin and "Moving logo" or "Static picture" as > device. 'ekiga -d 4' gives me > 2008/10/23 12:30:15.756 26:58.698VideoPrevi...0xb4bcbb90 > GMVideoOutputManagerSkipped earlier local frame > 2008/10/23 12:30:15.919 26:58.861 ekiga > HalManager_dbusDetected V4L capabilities on /dev/video0 name: > Logitech QuickCam EC > 2008/10/23 12:30:15.920 26:58.862 ekiga > HalManager_dbusSkipped V4L2 device /dev/video0without name > 2008/10/23 12:30:18.500 27:01.443 ekiga > VidInputCoreConfBridgeUpdating preview > 2008/10/23 12:30:18.566 27:01.508 ekiga > VidInputCoreStopping Preview I seem to remember that there was a symlink from /dev/video0 to /dev/video .. why did it disappear ? > Tohunga:/dev# ln -s /dev/video0 /dev/video "ekiga -d 4" .. gives me the same error message as above when I try to "display images from your camera device". What seems to be happening here ? I'd be grateful for any ideas. Adam Bogacki, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkj/u6sACgkQ1T+vu741y32tMACgu0pEk3snFshjNeCK8QKhmI6y AQYAnRJioJydu8DVKdNyXLewYOKdOoSQ =1tSJ -END PGP SIGNATURE- ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] a few problems with 3.0.1
> > 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/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] a few problems with 3.0.1
Hi, Julien Puydt wrote: Palo S. a écrit : Hi everybody, I have compiled and tested 3.0.1 today and here is a few problems/comments/questions that I have. The test machine was Fedora 9, 2.6.25.6-55.fc9.i686 kernel. 1. My webcam does not work with Ekiga 3 although it works just fine with Ekiga 2 (and works fine with basically any other program I tried - mplayer, vlc). It is Labtec Webcam Pro using the gspca driver. I think that the problem is that Ekiga detects the device as V4L2, however it is V4L. It does not work as V4L2 under other programs too. With Ekiga 2 I could choose V4L or V4L2 as video plugin, however with Ekiga 3 this does not seem to be possible anymore and the automatic detection only provides V4L2... Any way to force V4L? (error message: Error while accessing video device /dev/video0 There was an error while opening the device. ...) Did you try installing the ptlib-plugins-v4l (or some similar name) package which provides the V4L plugin driver? Note that v4l is disabled by default in ptlib. To enable it, execute "./configure --enable-v4l' in ptlib. 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 ? Since about 3 weeks I have the same problem: all the contact indicators are greyed out. I thought that it is because ekiga developers are working on ekiga.net. 3. Microphone does not work with \"Default (PTLIB/ALSA)\", however it works with \"HDA Intel (PTLIB/ALSA)\" specified... Then that works... 4. At opal compilation, there is a new dependency which is not taken into account by configure, namely swig (compilation stopped with an error message and continued after I installed swig - so no big problem but it should be checked by configure I believe?) No idea on this one. I ran into the same problem. You can uninstall swig and execute once: "touch src/java/java_swig_wrapper.c". I will create a bug report for this. 5. This one is just an information if somebody gets into the same issue: originally I reproducibly got a segfault if I wanted to make a call and the following error message appeared if ekiga --sync was run (followed by an attempt to make a call): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)\' failed It turned out that this was an issue between GTK+ and KDE4 desktop efffects - after KDE4 desktop effects were turned off, the problem disappared. Oohhh... that is annoying. :-/ 6. Although I did not get a chance to use video, I have noticed that the \"side by side\" view option is no longer available. Is there a plan to include it again? Basically all people I talked to prefer this over PIP/no local because one can both see himself and it does not cut from the remote at the same time - for some it was one of the \"killer features\" of Ekiga, I believe! Ok I would be glad for any comments. Also, could a developer please let me know if (s)he thinks that any of these should be filed as a bug? I'm annoyed by point 5 -- but I'm not sure the bug is on our side. Eugen ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] a few problems with 3.0.1
Palo S. a écrit : Hi everybody, I have compiled and tested 3.0.1 today and here is a few problems/comments/questions that I have. The test machine was Fedora 9, 2.6.25.6-55.fc9.i686 kernel. 1. My webcam does not work with Ekiga 3 although it works just fine with Ekiga 2 (and works fine with basically any other program I tried - mplayer, vlc). It is Labtec Webcam Pro using the gspca driver. I think that the problem is that Ekiga detects the device as V4L2, however it is V4L. It does not work as V4L2 under other programs too. With Ekiga 2 I could choose V4L or V4L2 as video plugin, however with Ekiga 3 this does not seem to be possible anymore and the automatic detection only provides V4L2... Any way to force V4L? (error message: Error while accessing video device /dev/video0 There was an error while opening the device. ...) Did you try installing the ptlib-plugins-v4l (or some similar name) package which provides the V4L plugin driver? 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 ? 3. Microphone does not work with \"Default (PTLIB/ALSA)\", however it works with \"HDA Intel (PTLIB/ALSA)\" specified... Then that works... 4. At opal compilation, there is a new dependency which is not taken into account by configure, namely swig (compilation stopped with an error message and continued after I installed swig - so no big problem but it should be checked by configure I believe?) No idea on this one. 5. This one is just an information if somebody gets into the same issue: originally I reproducibly got a segfault if I wanted to make a call and the following error message appeared if ekiga --sync was run (followed by an attempt to make a call): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)\' failed It turned out that this was an issue between GTK+ and KDE4 desktop efffects - after KDE4 desktop effects were turned off, the problem disappared. Oohhh... that is annoying. :-/ 6. Although I did not get a chance to use video, I have noticed that the \"side by side\" view option is no longer available. Is there a plan to include it again? Basically all people I talked to prefer this over PIP/no local because one can both see himself and it does not cut from the remote at the same time - for some it was one of the \"killer features\" of Ekiga, I believe! Ok I would be glad for any comments. Also, could a developer please let me know if (s)he thinks that any of these should be filed as a bug? I'm annoyed by point 5 -- but I'm not sure the bug is on our side. Snark on #ekiga ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] a few problems with 3.0.1
Hi everybody, I have compiled and tested 3.0.1 today and here is a few problems/comments/questions that I have. The test machine was Fedora 9, 2.6.25.6-55.fc9.i686 kernel. 1. My webcam does not work with Ekiga 3 although it works just fine with Ekiga 2 (and works fine with basically any other program I tried - mplayer, vlc). It is Labtec Webcam Pro using the gspca driver. I think that the problem is that Ekiga detects the device as V4L2, however it is V4L. It does not work as V4L2 under other programs too. With Ekiga 2 I could choose V4L or V4L2 as video plugin, however with Ekiga 3 this does not seem to be possible anymore and the automatic detection only provides V4L2... Any way to force V4L? (error message: Error while accessing video device /dev/video0 There was an error while opening the device. ...) 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) 3. Microphone does not work with \"Default (PTLIB/ALSA)\", however it works with \"HDA Intel (PTLIB/ALSA)\" specified... 4. At opal compilation, there is a new dependency which is not taken into account by configure, namely swig (compilation stopped with an error message and continued after I installed swig - so no big problem but it should be checked by configure I believe?) 5. This one is just an information if somebody gets into the same issue: originally I reproducibly got a segfault if I wanted to make a call and the following error message appeared if ekiga --sync was run (followed by an attempt to make a call): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)\' failed It turned out that this was an issue between GTK+ and KDE4 desktop efffects - after KDE4 desktop effects were turned off, the problem disappared. 6. Although I did not get a chance to use video, I have noticed that the \"side by side\" view option is no longer available. Is there a plan to include it again? Basically all people I talked to prefer this over PIP/no local because one can both see himself and it does not cut from the remote at the same time - for some it was one of the \"killer features\" of Ekiga, I believe! I would be glad for any comments. Also, could a developer please let me know if (s)he thinks that any of these should be filed as a bug? __ http://sport.sme.sk - Najkomplexnejšie informácie zo športu ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
