KDE Plasma 5.24.5, Bugfix Release for May
Tuesday, 3 May 2022. Today KDE releases a bugfix update to KDE Plasma 5,
versioned 5.24.5.
Plasma 5.24 was released in February 2022 with many feature refinements
and new modules to complete the desktop experience.
This release adds a month's worth of new translations and fixes from
KDE's contributors. The bugfixes are typically small but important and
include:
* Discover Flatpak backend: Improve stability of different sources
integration.
* Plasma Audio Volume Control: SpeakerTest: Fix subwoofer test.
* xdg-desktop-portal-kde: Fix saving file dialog view options.
Full Changelog:
https://kde.org/announcements/changelogs/plasma/5/5.24.4-5.24.5
Bugs Fixed
InnoDB: A failure occurred when attempting to purge undo records for a table with an instantly added column. (Bug #33924532)
InnoDB: High-priority transactions were not permitted to stop waiting when interrupted or to timeout while waiting for a lock, preventing deadlocks from being resolved. In cases where the blocking transaction is also high-priority, high-priority transactions are now permitted to stop waiting when interrupted or timeout when exceeding the lock wait timeout period. If a blocking transaction is not high-priority, high-priority transactions wait for the blocking transaction to release its locks. (Bug #33856332)
InnoDB: The AIO synchronization queue used on Windows was removed. The synchronous file I/O read-write function (SyncFileIO::execute) was revised to handle files opened for both normal and overlapped I/O, as it does on Linux. (Bug #33840645)
InnoDB: Table version metadata was not reset after truncating all partitions of a table with an instantly added column. (Bug #33822729)
InnoDB: The srv_error_monitor_thread() function, which prints warnings about semaphore waits, failed to handle a long semaphore wait as expected. To address this issue, a blocking call was moved to a more appropriate location. Related monitor thread code was simplified and improved, and missing shutdown signals were added for several server threads.
Enabling and disabling of the standard monitor by InnoDB is now performed independently of the user-settable innodb_status_output variable. This change addresses an issue in which the monitor was enabled by InnoDB in a particular scenario but not set back to its previous value. Thanks to Yuhui Wang for the contribution. (Bug #33789526, Bug #93878)
InnoDB: Valgrind testing identified an off-by-one error in rec_convert_dtuple_to_rec_old() in the InnoDB sources. (Bug #33784672)
InnoDB: The UNIV_DEBUG variant of the mem_heap_alloc() function in the InnoDB sources was modified to improve Valgrind error detection. (Bug #33783709)
InnoDB: A fast shutdown did not wait for all active I/O operations to finish before closing all files. (Bug #33768584)
InnoDB: A Clang warning reported an incorrectly placed @return command. (Bug #33734011)
InnoDB: Values of the new record locks array (m_prebuilt->new_rec_locks[]) were not properly synchronized when switching between partitions, causing an assertion failure due to locks being freed or not freed as expected. (Bug #33724166)
InnoDB: A race condition in the function that updates the double write buffer when a write request is completed caused a long semaphore wait error. (Bug #33712370)
InnoDB: A function wrongly assumed that changing a record in an indexed column always requires creating a new record in the secondary index, resulting in an lock-related assertion failure. To address this and other similar cases, the lock_rec_convert_impl_to_expl() function that converts an implicit record lock to an explicit record lock is now used only when an implicit record lock is actually held. (Bug #33657235)
InnoDB: A number of Doxygen issues in the InnoDB sources were addressed. (Bug #33603036)
InnoDB: A missing null pointer check for an index instance caused a failure. (Bug #33600109)
Full (and long) relnotes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html
Sponsored by: Netzkommune GmbH
When rust's internal LLVM does not match the LLVM used for building
gecko ports, LTO-built binaries will be unstable, exhibit crashes
and other undesirable behaviour. Rust 1.60 created such a situation.
Disabling LTO will allow these ports to be used, and keeping it off
will safe on build and debug time.
The patch is still needed at least on rockchip platform where
we probably don't do everything correctly for usb bring up.
This is also needed is the next boot stage is usb.
Reported by: kevans
GitHub is now generating a longer short commit ID in the patch.
PR: 262705
Reported by: thetanix (thetanix@gmail.com)
MFH: 2022Q2
Sponsored by: BBOX.io
The packages are switched from XZ to ZSTD compression, the compression level
is set at the maximum possible because it creates packages which are closed
in size between XZ and ZSTD, the compression time is close as well,
but decompression time is way bigger.
Exp-run: antoine
Differential revision: https://reviews.freebsd.org/D35095
Mostly just typos and assigning PORTREVISION multiple times.
This commit doesn't fix up PORTREVISION between master-slave
ports where the master port often overwrites PORTREVISION from
the slaves which means the slaves don't actually get bumped.
These probably just need PORTREVISION?= but care must be taken
to not decrease the package versions of all the master-slave
packages and to actually bump PORTREVISION as intended. For the
record the currently visible broken master ports are:
databases/libgda5
emulators/virtualbox-ose
emulators/virtualbox-ose-legacy
graphics/atril
multimedia/mlt7
textproc/uim
But all master ports should be looked at here and get an explicit
PORTREVISION?= where it's currently missing to prevent this.
Reported by: portscan
