LibreOffice 26.2.5 Ships with 21 Bug Fixes and Pulls Back Skia Rendering After Crash Reports

The Document Foundation has released LibreOffice 26.2.5, the fifth maintenance update to the 26.2 branch of the open-source office suite. Coming seven weeks after 26.2.4, this point release is not about new features; it is about stability. Twenty-one bugs are addressed across Writer, Calc, Base, and the shared interface, and one graphics-rendering change is significant enough that anyone who upgraded recently should pay attention.

Building on a February Foundation

LibreOffice 26.2.5 builds on the major feature release that The Document Foundation published back on February 4, 2026. Point releases in the 26.2 series follow a predictable rhythm: the .0 release introduces new capabilities, and each subsequent maintenance update, .1 through .5 and beyond, focuses purely on squashing bugs and steadying performance based on real-world reports from the suite’s global community of developers, QA testers, and partner organizations. This is the fifth such stop along that path, and it is a meaningful one.

The Big Change: Skia Rendering Moves to Experimental

The most consequential change in this release has nothing to do with a specific document format or formula. Skia, the open-source 2D graphics library that LibreOffice adopted on Windows and macOS to improve rendering performance, has been moved behind an experimental flag and is no longer active by default. The reason is straightforward: a meaningful number of users reported crashes and hangs after upgrading from earlier LibreOffice versions, and rather than let that instability keep affecting new installs, the project has opted to make Skia opt-in again until the underlying issues are resolved.

Anyone who specifically wants the performance benefits Skia offers, and who has not been affected by the crashes, can still turn it back on manually. The path is Tools, then Options, then LibreOffice, then Advanced, where enabling experimental features surfaces the relevant toggle under the View settings page. Linux users, particularly on Ubuntu, have a couple of additional workarounds available, including setting the SAL_USE_VCLPLUGIN=gen environment variable or adjusting the VCL backend through the Expert Configuration dialog. For the vast majority of everyday users, though, the default behavior is now the safer, more conservative rendering path.

Writer: Small Fixes That Matter More Than They Look

Writer, LibreOffice’s word processor, picks up several fixes that specifically target document round-tripping and everyday editing reliability:

• Empty paragraphs that are supposed to stay hidden inside Microsoft Word .DOC files were incorrectly becoming visible after opening; that behavior is now corrected.
• Editing a conditional text field no longer risks corrupting the field type, a bug that could quietly break document logic without any obvious warning.
• Pressing Shift+Enter on the numeric keypad no longer crashes the application, a small but startling bug for anyone who hit it unexpectedly mid-document.
• AutoCorrect now correctly preserves a space after a single-letter word at the start of a paragraph, under specific AutoCorrect configurations, rather than silently deleting it.
• An HTML export issue affecting punctuation and other weak-directionality characters inside right-to-left text spans has been resolved, which matters considerably for users working in Arabic, Hebrew, or other right-to-left scripts alongside embedded left-to-right punctuation.

Calc Gets Formula and Regional Fixes

Spreadsheet users benefit from a batch of fixes that address both formula correctness and regional formatting. The SUMIF function had a regression where wildcard matching would fail whenever an asterisk appeared before certain supplementary Unicode characters, a subtle bug that could silently produce wrong totals for anyone working with extended character sets. That is now fixed. Calc’s currency formatting database also gains the Saudi riyal symbol, closing a small but real regional gap for finance users in that market.

On the interface side, this release restores right-click context menu functionality that had been lost somewhere in the 26.2 cycle, a regression that would have quietly annoyed anyone relying on right-click shortcuts for day-to-day spreadsheet work. A separate fix addresses unexpected behavior where pressing Ctrl+Shift could change horizontal cell alignment when that was clearly not the user’s intent.

Base and Accessibility

LibreOffice Base, the suite’s database front end, fixes an issue where column orientation inside tabular subforms was being lost, which could scramble the layout of forms built against a linked database table. On the accessibility side, long text displayed inside the Accessibility sidebar now wraps properly instead of being truncated with an ellipsis, specifically on non-GTK3 desktop interfaces. It is a small fix, but an important one for users who depend on screen-reader-adjacent tooling to navigate documents.

Who Should Upgrade, and a Note for 25.8 Users

The Document Foundation is not shy about who should install this update: anyone running LibreOffice 26.2 is encouraged to move to 26.2.5 as soon as practical, particularly given the crash-related Skia change. There is also a sharper deadline for a separate group of users. LibreOffice 25.8 reached its official end of life on June 12, 2026, meaning that branch no longer receives security updates of any kind. Anyone still on 25.8 should treat this less as an optional upgrade and more as a security requirement, since unpatched vulnerabilities in an end-of-life branch will not be addressed going forward.

Editor’s take: pulling back a performance feature after real-world crash reports is exactly the kind of unglamorous, trust-building decision that tends to get overlooked in release notes but matters enormously to day-to-day reliability. LibreOffice’s point-release cadence, boring on purpose, is precisely why so many institutions and governments have been comfortable standardizing on it.

Why Point Releases Like This One Matter More Than They Seem To

It is easy to skim past a maintenance release like 26.2.5 because nothing in it is new. There is no headline feature to screenshot, no marketing push, no keynote moment. But for the institutions, schools, and businesses that make up a large share of LibreOffice’s user base, this kind of release is arguably more important than a feature update. Government agencies and enterprises that standardize on open-source office software tend to prioritize predictability and stability above all else, and a steady cadence of focused bug fixes, arriving roughly every seven weeks in this case, is exactly the signal that reassures IT departments they made the right call. The Document Foundation has built its reputation less on flashy new capabilities and more on this kind of unglamorous reliability engineering, and 26.2.5 is a clean example of that pattern in action.

The decision to walk back Skia rendering to an experimental, opt-in state is a particularly good illustration of that philosophy. It would have been easy to leave Skia enabled by default and simply patch around the reported crashes over successive point releases, but that approach risks leaving a meaningful number of users dealing with instability in the meantime. Defaulting back to the safer, more battle-tested rendering path, while still leaving an opt-in switch for users who want the performance upside and have not hit the bug, is the kind of conservative call that prioritizes the broadest possible base of users over chasing a specific performance number.

A Closer Look at the SUMIF Fix

Among the Calc fixes, the SUMIF wildcard regression deserves a bit more explanation, because it is the sort of bug that can cause real financial or analytical errors without ever throwing a visible warning. SUMIF with wildcard matching is commonly used to total values based on partial text matches, for example, summing all rows where a product code starts with a certain prefix. The regression meant that when an asterisk wildcard appeared immediately before certain supplementary Unicode characters, characters outside the most common character ranges, the match would silently fail, and rows that should have been included in the sum simply were not counted. For most spreadsheets working purely in Latin text, this would never have surfaced. But for multilingual datasets, particularly ones incorporating characters from certain East Asian, emoji, or extended symbol ranges, the bug could produce a total that looked plausible but was quietly wrong. That is precisely the kind of bug that erodes trust in a spreadsheet once discovered, and its inclusion in this release is a good reminder to double check any wildcard-based SUMIF formulas that touch non-Latin text if you were running an affected 26.2 build.

Practical Advice for Upgrading

For most individual users, upgrading is as simple as downloading the new installer and running it over the existing installation; LibreOffice does not typically require an uninstall step first. Organizations managing larger fleets of machines should, as always, test the update against a representative sample of their standard document templates and macros before a full rollout, particularly if those workflows touch Base subforms or heavily formatted DOCX round-trips, given the fixes in those specific areas this release. Anyone who previously disabled Skia manually to work around crashes on an earlier 26.2 point release does not need to do anything further, since the new default already reflects that safer configuration.

Availability

LibreOffice 26.2.5 is available immediately as a free download for Windows, macOS, and Linux directly from the official LibreOffice website, with DEB and RPM binaries provided for Linux distributions. As always, the suite remains entirely free of subscription fees, covering the full range of document, spreadsheet, presentation, database, and PDF-handling tasks that make up the modern office workflow. Given the scope of Writer and Calc fixes in this release, most current 26.2 users should see a noticeably smoother experience simply by installing the update through their existing update channel.