Using the camsource and vlc packages as an example. If camsource is configured to use a given dev/video[n] device with a choice of resolution in the width and height fields of a camsource conf file then if camsource is the first application to access the device captured images are as-expected. However, if an application like vlc is used for the same device (and exited) before starting camsource (e.g. to check the view from the camera before starting camsource) and if the camera supports higher resolutions than used in the camsource configuration what occurs is that camsource will not setup the camera to use the configured resolution and has a broken view of the camera output based on the vlc chosen resolution chopped to the camsource configuration. For example, with camsource configuration set to use 640x480 on a camera that supports 720x480 and vlc is used and exited before camsource is started then the captured camsource images contain two non-continuous partial image blocks with a horizontal border dividing them. I assume either vlc fails to fully reset the device configuration when exiting or camsource fails to initialize the device "from scratch" when starting. The two applications use different video device APIs but the setup and cleanup for the camera in each case is a very limited part of the application's functionality.

Project Description

I'm totally new in k8s, when I hear Rancher's product in all-hands I couldn't image what's that is. I'd like to take some time to learn some basic knowledge about k8s and Rancher's products.

The user space interface of evdev is pretty generic. All hardware abstraction is done in the kernel driver, device properties are mapped to a set of generic properties. The properties can be queried thru a generic interface only very few parameters are set from user space. In user space the evdev API is used by Xorg's evdev driver and libinput.

Following up on Sunday's Kopano deployment workshop at oSC16, I deploy an instance of the FLOSS groupware, collecting important steps in https://w3.suse.de/~bwiedemann/contrib/kopano-setup.sh

I recently bought a Lioncast LK200 RGB keyboard which is a nice piece of hardware and has exactly the look and feel I want. All basic functions work well under Linux. Unfortunately the manufacturer only provides user software to upload/download profiles and control the LEDs for Windows. The device can be configured and operates autonomously from any OS but color setup is a PITA and it's very easy to factory-reset, and lose all config.

Enhance the YaST ncurses package installation to show the changelog of a package and the level of supportability (on SLE).

****The motivation is create a open source solution, base on this business astronomy products: AZWO Asiair

Description

I have a few ideas of improvements for the delogo filter included in ffmpeg's libavfilter.

Description

Improve UML handling of segmentation faults in kernel mode. Although such page faults are generally caused by a kernel bug, it is annoying if they cause an infinite loop, or panic the kernel. More importantly, a robust implementation allows to write KUnit tests for various guard pages, preventing potential kernel self-protection regressions.