On Thu, Nov 21, 2013 at 03:13:01PM +0100, Dominik K. wrote: > >> @Kurt: Can you try starting Jitsi with the following shell command, please: > >> > >> $ LD_PRELOAD=/usr/lib/i386-linux-gnu/libv4l/v4l2convert.so jitsi > > > > Today I can't seem to start it for some reason. > > I forgot to mention that you'll need to install the package "libv4l-0" > before. Maybe that helps.
That is totally unrelated. It's installed. It's just gnome being really annoying. > > Maybe jitsi should link to that library instead? > > That's what I suggested on the dev mailinglist. Here an excerpt from > the README: > > "The preloadable libv4l2 wrapper which adds support for various > pixelformats to v4l2 applications is called v4l2convert.so." So let's quote the whole documentation here: | wrappers | -------- | | The functionality provided by libv4l1 for v4l1 apps and libv4l2 for v4l2 apps | can also be used by existing apps without modifying them. For this purpose | 2 wrapper libraries are provided which can be preloaded before starting the | application using the LD_PRELOAD environment variable. These wrappers will | then intercept calls to open/close/ioctl/etc. and if these calls directed | towards a video device the wrapper will redirect the call to the libv4lX | counterparts. | | The preloadable libv4l1 wrapper which adds v4l2 device compatibility to v4l1 | applications is called v4l1compat.so. The preloadable libv4l2 wrapper which | adds support for various pixelformats to v4l2 applications is called | v4l2convert.so. | | Example usage (after install in default location): | $ export LD_PRELOAD=/usr/local/lib/libv4l/v4l1compat.so | $ camorama So it's my understanding that it would be better that we use libv4l2 and then replace calls like open() with v4l2_open(). The wrapper is just there to fix broken applications. I can see no good reason why we don't use the library itself instead. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org