Markus Volk
25e2663a87
libinput 1.21.0 is now available for download.
This version includes a new configuration option that, similarly to its touchpad counterpart, allows disabling the trackpoint while typing.
Compositors can take advantage of it thanks to four new APIs:
libinput_device_config_dwtp_is_available, libinput_device_config_dwtp_set_enabled, libinput_device_config_dwtp_get_enabled and libinput_device_config_dwtp_get_default_enabled.
Those who use the flat acceleration profile on their touchpad are in luck, it has been improved in this version.
In addition to the changes already mentioned, new quirks have been added for multiple StarLabs laptops.
Last but not least, several bugs have been fixed, so make sure to update!
Thanks to everyone involved for making this new version possible ❤
Alexander Courtis (1):
AttrLidSwitchReliability quirk default unreliable->reliable
José Expósito (7):
evdev: check well-known keyboard keys on joystick/gamepad detection
evdev: modernize variable declaration in evdev_device_is_joystick_or_gamepad
coding style: allow C99 variable declaration
test: disable hold gestures when are not required
Remove "device-" file
wheel: fix Lenovo Scrollpoint quirk
libinput 1.21.0
Peter Hutterer (26):
gitlab CI: fail the sanity check stage if the fork is not public
util: auto-declare the element variable in ARRAY_FOR_EACH
meson: fix a meson warning
meson: replace a meson.source_root() with the explicit directory
doc/user: add a page to troubleshoot right-click Clickpads
tools/record: fix the indentation of the system: section
evdev: strip the device name of format directives
tools: allow limiting the axes in libinput analyse recording
tools: don't print a carriage return if we're not on a tty
tools/record: fix indentation for libinput events
tools/analyze-recording: add --print-state to always print values
tools/analyze-recording: improve the repeated-events line printing
tools: add a libinput test tool as entry point for our test suites
test: install libinput-test-utils as part of install-tests
quirks: move the canvas quirk enum to the right order
quirks: remove an unused quirk
tablet: remove an always-true part of an if condition
test: rename a test function to make it easier to select
tablet: use a helper variable to make the code more readable
tablet: require a minimum pressure before we process pressure events
test: fix the lowres-only wheel event tests
test: ensure we always have an axis event where we expect one
test: use a ranged test instead of a duplicated one
test: fix a typo
meson.build: check gtk targets before building
gitlab CI: bump to F35 and F36, as well as Ubuntu 21.10 and 22.04
Sean Rhodes (2):
quirks: Add quirk for StarLite Mk IV
Quirk all StarLabs trackpads
Tom Stellard (1):
Update valgrind.h to a newer version
pudiva chip líquida (1):
touchpad: new option dwtp (disable-while-trackpointing)
satrmb (1):
filter-touchpad: normalize for dpi on the touchpad-specific flat profile
libinput 1.20.1 is now available for download.
This release fixes CVE-2022-1215, see #752.
When a device is detected by libinput, libinput logs several messages through log handlers set up by the callers.
These log handlers usually eventually result in a printf call. Logging happens with the privileges of the caller,
in the case of Xorg this may be root.
The device name ends up as part of the format string and a kernel device with printf-style format string placeholders
in the device name can enable an attacker to run malicious code. An exploit is possible through any device where the
attacker controls the device name, e.g. /dev/uinput or Bluetooth devices.
Peter Hutterer (2):
evdev: strip the device name of format directives
libinput 1.20.1
(From OE-Core rev: 1f1888cc8a35b98ccde472eb345c1e483eb6b6d1)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.