On Thu, Sep 11, 2008, Damien Sandras wrote: > > Please report a bug against your driver which do not support the > > standard for Linux. > In 2.6.27 they have a brand new driver which uses libv4l (unpackaged on > Ubuntu and Debian). It works with our V4L2 plugin and we also have > support for libv4l which makes it work perfectly. libv4l actually takes > care of the color conversion between various formats for us.
Ah that might be why it works despite me installing only the v4l2 plugin. To clarify, the problems I saw with this webcam were that: - the name of the device wasn't shown in the setup's dropdown instead I saw USB:blahblah; the device was detected as being usable, just not named properly - it wasn't selected by default > > > - locking assertion failures on console in libxcb :-/ > > Please try the latest package, or report the bug upstream. > We have not tested with libxcb. The current Ubuntu version doesn't suffer from this bug at least. It seems like a race as it doesn't happen all the time; I suspect it's triggerred by popups coming on startup from a different thread, or something along these lines. I'll post the backtrace which is sent to stderr if it happens to me again. Of course when this happens the UI is stuck. > Notice that this specific error and the one you report about the wrong > video device and alsa device being selected indicates a messed up gconf > configuration. Default values seem to have been ignored. Can you double > check that ? I guess I'll start afresh, resetting GConf settings and all; I know being backwards and forwards compatible with GConf settings is hard :-/ > > > - REGISTERs were sent twice because I had two local interfaces (one for > > > virtualbox); this was very confusing for the SIP registrars and > > > caused ekiga to think I wasn't registered when I really was (only the > > > second register was failing) > It is the way it is supposed to work. Ekiga now supports several > interfaces allowing you to connect to the VPN of the office at the same > time than you connect to the internet. I would need a debug log if you > think there is a bug here. But I think there is no bug on our side. > Perhaps you are testing with Asterisk which does not support SIP forking > (which is what we are doing to handle several interfaces at the same > time) I was testing against both ekiga.net and an asterisk company SIP server. I think you should simply use the default interface for a server, not send one REGISTER per possible source IP address. If one wants voip to go via the VPN, DNS should be setup as such or traffic should be routed as such; ekiga shouldn't second guess the routing tables IMO. But perhaps I misunderstand what ekiga is doing. On my host I had two IPs in 192.168; one 0.101 on eth0 and one 12.42 on vnet0; all applications on my host use eth0 because it allows contacting the default gateway and hence use 192.168.0.101. For some reason SIP REGISTERs were going out via eth0 from .0.101 and .12.42. -- Loïc Minier -- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
