KDE Frameworks 6.31 Overhauls Encoding Detection and DAV Sync

A monthly release with more in it than usual

KDE published Frameworks 6.31 on October 9, 2026. It is the newest stable version of the project's set of more than 80 add-on libraries for Qt, which support the Plasma desktop and the KDE Gear applications.1 KDE developer Nicolas Fella posted the announcement to the project's release-team mailing list that same Friday.8 The date matched the plan: the project's public schedule had already listed October 9 as the expected release date and October 2 as the tagging date.9

Most outlets wrote it up as a routine maintenance release, and much of it is. Headlines put the emphasis in different places, though. Some led with file-management fixes, some with text encoding, and some with calendar and contact synchronization.13 Taken as a whole, the coverage shows two real changes inside the usual list of small fixes. The first is a substantial rework of how KDE software guesses a file's text encoding. The second is new plumbing that lets KDE applications get push-based, incremental updates from DAV servers. The many small fixes matter too, but these two are where the release breaks new ground.

What changed for users

The fixes users will notice first are in System Settings. In some applications, the "Frames and Outlines Contrast" theme option had no effect, and that is now fixed. A second bug, in which marking the home folder as "Indexed" on the Search page created a clone that could not be removed, is also gone.12

KIO, the framework that handles file operations, got a set of accuracy fixes for copy and move jobs. Skipped files and folders no longer throw off the byte totals or the progress percentage.3 The changelog lists separate commits that remove skipped files from the byte total, stop counting a skipped directory as processed, and keep a move's percentage from going past 100.13 Search results now refresh when a file is renamed or deleted. Thumbnails that already exist are no longer regenerated over and over. The trash now watches its physical directories for changes.2 FTP modification times now follow RFC 3659.1

The remaining fixes are smaller. In Kirigami, rapid touch taps are no longer dropped while an animation is running. Breeze gains Bluetooth speaker icons and a proper tab-close icon.2 KFileMetaData's FFmpeg extractor now reads GPS coordinates, creation times and Apple-specific metadata from media files. KImageFormats improves its OpenEXR support, including metadata saved by Photoshop and correct handling of alpha channels.1

The encoding overhaul, and what "statistical" means here

For the release's machine-learning-adjacent work, look at KCodecs. The outlets agree that KEncodingProber, the component that guesses which character encoding a file uses, was heavily reworked. Coverage lists better accuracy for Latin-1, Big5 and Windows-1252, plus a new statistical method for telling UTF-8 and UTF-16 apart.12 One outlet said this means the prober is "no longer purely heuristic." It also described a new universal prober for Chinese, Korean, Japanese and general Unicode subsets, along with sub-probers that can now be selected individually.

This is not neural-network ML, and it should not be described that way. The changelog describes the work as classic probabilistic detection: adjusted Latin-1 sequence models, corrected code-point classifications, repaired Big5 state tables, and a better Latin-1 confidence calculation.13 The approach is closer to the language-model-based charset detectors that browsers have used for years than to anything in today's AI boom. Even so, the problem is the same one machine learning works on: deciding under uncertainty with a confidence score, then cutting down false positives.

For that reason, the most important single line in the change list may be the one that stops the prober from falling back to UTF-8 when the input is invalid.13 Several outlets singled it out, saying that labeling invalid text as UTF-8 caused misread files, especially ones in non-English languages.2 Most software assumes UTF-8 by default. Reporting "uncertain" instead of confidently giving a wrong answer is a sensible design choice, and AI product teams are dealing with the same question in their own systems.

The coverage differs on how big this change is. One report called it a full rewrite of the detector. Other outlets called it a deep overhaul or a refinement.12 The changelog is a long list of targeted commits, including new tests for Spanish and French Windows-1252 input and expanded Big5 tests.13 That supports "overhaul" better than "rewrite": the detector was improved one commit at a time, with tests added along the way, not replaced.

KDav and the move to push-based sync

The second notable change is in KDav, the library behind CalDAV and CardDAV calendar and contact sync. It adds jobs for registering and unregistering DavPush notifications.1 It also adds a sync job that uses a sync token to fetch only the items that have changed, plus a flag that suppresses notification side effects on specific operations.13

One outlet argued that incremental sync is the more useful of the two in practice, because clients no longer have to re-download an entire collection. A sister site said the gain is largest on low-bandwidth connections. That seems right. Push support only helps once servers implement DavPush. Sync tokens make every refresh cheaper starting now. Together they move KDE's personal-information stack away from polling, which mobile and cloud calendar platforms dropped long ago.

A release aimed at developers

Beyond the headline changes, 6.31 is mostly about developer tooling and build quality. Nearly every framework in the changelog includes a commit adopting ECMInstalledLibraryCheck.13 One outlet described this as CI verification aimed at build reliability, and the same report said the release requires Qt 6.10.0. None of the other coverage mentioned the Qt requirement, so packagers should confirm it against KDE's own documentation. KCalendarCore turned on the leak sanitizer in CI and fixed memory leaks that appeared with libical 4.13

There are new APIs as well. KCoreAddons adds KSafeStringError and exposes KJob's type to QML.13 One outlet described KSafeStringError as a type for handling error strings safely without exceptions. The same report said KWallet's secret-service daemon was modernized to use QFuture for asynchronous operations, with rollback that is safe if an exception is thrown.

For people who write code in KDE's editors, KTextEditor, the component behind Kate and KWrite, adds several Vi-mode features. Numpad digits now work as count prefixes, addition and subtraction work in visual mode, and arithmetic supports binary format.1 The color theme selector moved to the View menu, because the setting applies only to the current view. The syntax-highlighting framework now supports LRC lyrics files, updates systemd unit highlighting for version 262, and fixes a long list of Zsh issues, including the brace command-substitution forms introduced in zsh 5.10.313

The cadence is part of the product

From a product-management view, the release process is as interesting as the code. Frameworks are tagged on the first Friday of every month and released one week later. A two-week string freeze before tagging gives translators stable text to work with.9 The project has no feature freeze. New features can land at any point as long as they have unit tests and reviews and do not interfere with the string freeze.9 One outlet described this as a schedule meant to give developers predictable, frequent improvements.2 A daily digest called the monthly cadence "relentless."

The arrangement works because quality gates replace calendar gates. A new feature such as DavPush support does not wait for a big annual release. It ships in the next monthly build once it passes review and tests. The trade-off is that individual releases look small. That explains why most headlines simply said "improvements and bug fixes" while the encoding and sync work got less attention than it deserved.

The timing also places 6.31 just ahead of Plasma 6.8, which was set for release on October 14 after a second beta.3 Comments under one report suggest how users see that larger release: they argued over Plasma 6.8 dropping X11 and moving from desktop OpenGL to OpenGL ES.1 Those comments are opinions, not reporting, but they show the gap in visibility between large desktop releases and the steady library work underneath them.

Getting it

KDE again recommends installing Frameworks through a distribution's package manager, so when users get 6.31 depends on each distribution's update schedule.3 Rolling-release users will likely see it within days. Users of fixed-release distributions may wait much longer.

Overall, Frameworks 6.31 contains no single major feature. Its value is in many tested, incremental fixes, plus two architectural changes: an encoding detector that reports uncertainty instead of guessing UTF-8, and a sync layer that fetches only what has changed.