|Index||index by Group||index by Distribution||index by Vendor||index by creation date||index by Name||Mirrors||Help||Search|
|Name: libXi6||Distribution: openSUSE Tumbleweed|
|Version: 1.7.10||Vendor: openSUSE|
|Release: 1.3||Build date: Wed Nov 27 05:29:30 2019|
|Group: System/Libraries||Build host: obs-arm-9|
|Size: 67944||Source RPM: libXi-1.7.10-1.3.src.rpm|
|Summary: X Input Extension library|
libXi is the client-side library for the X Input Extension.
* Fri Jun 21 2019 Stefan Dirsch <firstname.lastname@example.org> - Update to version 1.7.10 * Fix the FIXME in XIValuatorClass case of copy_classes function in XExtInt.c * _XIPassiveGrabDevice needs to set time value * Replace open-coded FP3232_TO_DOUBLE * autogen: add default patch prefix * autogen.sh: use quoted string variables * autogen.sh: use exec instead of waiting for configure to finish * Update configure.ac bug URL for gitlab migration * Update README for gitlab migration * man: add a bunch of missing spaces * Update XIChangeHierarchy.txt * Mon Jan 23 2017 email@example.com - Update to version 1.7.9: * Plug a memory leak * Check that allocating a buffer succeeded * Fix possible free of uninitialized pointer * Fri Oct 28 2016 firstname.lastname@example.org - Update to version 1.7.8: The changes of 1.7.7 are included. + Fix a crash introduced in the 1.7.7 release. + Properly validate server responses. * Tue Dec 22 2015 email@example.com - Update to version 1.7.6: One significant change here: libXi was using raw serial numbers in event cookies, the one read off the wire. All other events don't use that number but a Xlib-internal serial number which is similar but not always the same. This could cause events to look out of order. With this release, libXi is now using the same serial number for event cookies as it uses for all other events. * Fri Sep 11 2015 firstname.lastname@example.org - Update to version 1.7.5: A couple of important bugfixes that have accumulated over the last year. + Fix version check in _XIAllowEvents + Advance the request buffer by the right amount in XIChangeHierarchy + Fix double unlock when _XiCheckExtInit return -1. + XIChangeHierarchy: Add missing unlock. + Do not return NoSuchExtension casted to pointer as an error. + XIGetClientPointer: Return False on error. + Fix logic in _XIAllowEvents and prevent double unlock. + Refactor XGetExtensionVersion. + XIGrabDevice: Unlock display in error path. * Fri Jul 18 2014 email@example.com - Update to version 1.7.4 * Fix locking bugs with XIAllowTouchEvents() and XIUngrabTouchBegin() * Fri Jul 11 2014 firstname.lastname@example.org - Update to version 1.7.3 * Two important patches fixing deadlocks when using XIPassiveGrab requests. You're recommended to updated. Note that we now require libX11 1.6, that's a new dependency over 1.7.2 but it's over a year old by now anyway. - added baselibs.conf as source to specfile * Wed Jul 03 2013 email@example.com - Update to version 1.7.2: Only one minor change since the RC. Again, this release contains the fixes for CVE-2013-1998, CVE-2013-1984 and CVE-2013-1995 so you're encouraged to update. + Remove check that can never be true. * Fri Jun 28 2013 firstname.lastname@example.org - Update to version 184.108.40.2061: First and likely only RC for libXi 1.7.2. This one has a bunch of changes for CVE-2013-1998, CVE-2013-1984 and CVE-2013-1995. These relate to various integer overflows and other corruption that happens if we trust the server a bit too much on the data we're being sent. On top of those fixes, the sequence number in XI2 events is now set propertly too (#64687). * Fri Apr 05 2013 email@example.com - Update to version 1.7.1: Only a single fix: including the XFixes header to get the typedef for PointerBarrier. Naturally, this adds a pkgconfig build-time dependency on XFixes. Why? The header shipped with 1.7 typedef'd PointerBarrier. If you #include both XI and Xfixes headers, you will end up with a duplicate typedef. This is not an issue on gcc >= 4.6 since the two typedef's are the same. On earlier versions this will trigger an error. gcc 4.6 -pedantic-errors will trigger the same error.
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue May 26 00:41:37 2020