Berlin, 4 September 2026 – The Document Foundation today announced the release of LibreOffice 26.2.6, the sixth maintenance update to the LibreOffice 26.2 branch. Building on the major feature release published on February 4, 2026, this update delivers targeted bug fixes and stability improvements contributed by a global community of developers and QA engineers.

LibreOffice 26.2.6 is available for immediate download at libreoffice.org/download for Windows, macOS, and Linux.

List of fixes in RC1: Releases/26.2.6/RC1. List of fixes in RC2: Releases/26.2.6/RC2.

LibreOffice users, free software advocates and community members can support The Document Foundation and the LibreOffice project with a donation at libreoffice.org/donate.

Q&A — LibreOffice 26.2.6

Q: What is LibreOffice 26.2.6?

LibreOffice 26.2.6 is the sixth maintenance update to the LibreOffice 26.2 branch, released by The Document Foundation on 4 September 2026. It delivers targeted bug fixes and stability improvements over the major feature release published on 4 February 2026.

Q: When was LibreOffice 26.2.6 released?

4 September 2026.

Q: Where can I download LibreOffice 26.2.6?

From https://www.libreoffice.org/download/, for Windows, macOS, and Linux.

Q: Which operating systems does LibreOffice 26.2.6 support?

Windows, macOS, and Linux.

Q: What is the next version of LibreOffice after 26.2.6?

The Document Foundation will announce LibreOffice 26.8.1 on 17 September 2026, and LibreOffice 26.2.7 on 29 October 2026.

Q: Where can I find the full list of fixes in LibreOffice 26.2.6?

RC1: https://wiki.documentfoundation.org/Releases/26.2.6/RC1 — RC2: https://wiki.documentfoundation.org/Releases/26.2.6/RC2

Q: Who develops LibreOffice 26.2.6?

A global community of volunteer and professional developers and QA engineers, coordinated by The Document Foundation, the Berlin-based non-profit behind LibreOffice.

Q: How much does LibreOffice 26.2.6 cost?

Nothing — LibreOffice is free and open source software. Users and advocates can support the project with a donation at https://www.libreoffice.org/donate.

One of the comments on the announcement of LibreOffice 26.8 was a simple question: “So, no AI is now a feature?”

LibreOffice does not reject artificial intelligence out of hand, but an office suite used by tens of millions of people – in schools, hospitals, public bodies, law firms and thousands of other organisations – will not add a feature to its default configuration until that feature can be delivered under the conditions defined by the project in accordance with its principles.

User-controlled execution. The user must be able to choose where inference takes place: on the local computer, on an infrastructure directly controlled by the user, or on a service chosen independently by the user. A default setting that silently redirects to a single provider is not a choice.

No content may leave the computer without authorisation. The content of documents is a user’s asset and, in many implementations, is also legally protected material: medical records, case files, tender documents and student data. Transmission must be the result of a user’s decision and not behaviour carried out in the background by the application.

No telemetry of any kind. LibreOffice does not collect usage data, and this must also apply to AI features.

No dependence on a single provider. An integration that only works with a single company’s API is a lock-in mechanism, regardless of how it is described in the release notes. Interfaces should be open and implementable by multiple backends.

No compromises on format. Generated content must be in ODF format, just like any other content, and must retain its structure, styles and semantics. An assistant that generates documents in a proprietary format perpetuates content lock-in.

Entirely optional. It must be installable, removable, and absent from the user interface for those who do not wish to use it, including administrators deploying the software across thousands of workstations who, due to company policy, do not authorise its use.

Where we stand today

In light of this list, there is no integration that meets all the requirements and that could be deployed, enabled by default, and supported throughout the entire lifecycle of a release. This is an assessment of the current state of the technology and the solutions based on it, and not a judgement on the value of the sector.

In the meantime, users who wish to use AI features can install one of the available extensions, which can be found either on the LibreOffice extensions website or distributed independently. Most connect to a locally running model via Ollama, LM Studio or another OpenAI-compatible endpoint, which means the document never leaves the computer.

These are third-party extensions at various stages of maturity, developed and maintained by their respective authors rather than by The Document Foundation. Users and administrators should assess them as they would any third-party component, checking whether a cloud endpoint is configured and what the provider does with the data it receives. The extension mechanism offers AI functionality to those who want it, without any consequences for all other users.

Why our motivations are different

The reason our position differs from that of the dominant suites has almost nothing to do with the technology.

For a company that sells subscriptions, an AI assistant justifies a price increase and strengthens the case for keeping all documents within its own infrastructure. The functionality and the business model reinforce each other, so integration is not only attractive but almost mandatory.

The Document Foundation is a not-for-profit organisation. There are no subscription tiers to protect, no upsells, no data to monetise. This does not make us wiser than others, but it means we can take the time needed to decide whether something is genuinely useful for our users, as we are not driven by quarterly results.

What lies ahead

The criteria we have listed do not amount to a definitive rejection. The AI sector is evolving rapidly; on-premises inference is becoming manageable on standard hardware; and open models are improving much faster than most of us had anticipated. Should an approach emerge that meets all the conditions, we will evaluate it very carefully.

Until then, there will be no AI of any kind in the default installation; extensions will be available for those who wish to integrate AI features, and we will closely monitor where the technology is actually heading.

One week ago, we announced LibreOffice 26.8, our brand new major update. It’s full of new features, and has many improvements to compatibility and performance too. So, what has happened in the week since then? Let’s check out some statistics…

1,031,162 downloads

This is the highest number of downloads in the first week of any LibreOffice release! These are just stats from our official downloads page, of course – many Linux users will have acquired the new release via their distribution’s package repositories.

50,061 views, shares and likes on social media

Combining our Mastodon, Bluesky, X/Twitter (not used so much now) and Facebook posts about the announcement, and all the likes, shares, views and comments, we get over 50,000. Thanks to everyone who spread the word on social media!

20,918 video views

Our “LibreOffice 26.8 – New Features” video (shown below), has subtitle translations in 32 languages, thanks to our worldwide community, who localised the video on this page. (The video is also available on PeerTube.)

Many thanks to our worldwide community of volunteers, and certified developers, for all their work on this release

Here’s our summary of updates, events and activities in the LibreOffice project in the last four weeks – click the links to learn more…

• We released LibreOffice 26.8, our latest major update, with tabbed UI improvements, professional typography, deeper support for the world’s writing systems, and no built-in artificial intelligence.

• To accompany the release, we made a video showcasing some of the user-facing new features – with subtitle translations in 25 languages, thanks to our worldwide community! (The video is also available on PeerTube.)

• Meanwhile, the Austrian Military (Bundesheer) has moved 16,000 PCs from Microsoft Office to LibreOffice – and we talked to the people behind the migration, to find out how they did it. Check out part 1 and part 2 of the interview.

• Then we talked to Karl-Heinz Gruner from the German-speaking LibreOffice community about his activities in the project.

• Extensions add extra features to LibreOffice, and we talked to Bora Yarkın about a new one which lets you control a LibreOffice Impress presentation from your phone or any other device with a modern web browser.

• In the middle of August, the schedule for the LibreOffice Conference 2026 went online. If you can make it, we look forward to seeing you there

• Then we did another Community Member Monday interview, this time talking to Aleksi Kallio about his work on fixing bugs in LibreOffice.

• There’s a lot of talk about “Digital Sovereignty” – but what does that actually mean? One vital part is an open document platform – like ODF.

• LibreOffice is a worldwide project made up of hundreds of people: volunteers, developers at ecosystem companies, and the 18-person team at The Document Foundation (the non-profit entity that coordinates the project and community). What has the team been working on recently? Check this post to find out.

• LibreOffice has a few user interface options, and none are forced on the user. We explored this topic more in a post called There Is No “Best” Interface, Only the Right Fit.

• How is LibreOffice funded? The vast majority of funding comes in the form of donations – mostly from end-users, but also occasionally from companies and organisations that use LibreOffice.

• Finally, we wrapped up August with another Community Member Monday, talking to Rohan Singh about his macOS-related development work.

Like what we do? Support LibreOffice with a donation – or join our community and help to make LibreOffice even better! Also keep in touch – follow us on Mastodon, Bluesky, Reddit and Facebook.

🚀 Features

• Added Bergamot local translation fallback (#1147) by @JaredTweed in #1147
• Add option to disable built-in audio player (#1192) by @spacecowboy in #1192
• Added setting to force single column feed (#1193) by @MB3hel in #1193
• Added ‘Apply to links’ toggle to blocklist feature (#1196) by @zork3000 in #1196

🐛 Bug Fixes & Minor Changes

• Update feed url if selfLink has a new address in the original feed (#1096) by @xn-7492 in #1096
• Reset TTS queue on article switch and resume same article only (#1203) by @atirna in #1203

🌐 Translations

• Updated French translation using Weblate by @Matth7878 in commit
• Updated Latvian translation using Weblate by @Coool in commit
• Updated Estonian translation using Weblate in commit
• Updated Ukrainian translation using Weblate by @G-H-User in commit
• Updated Hungarian translation using Weblate by @summoner001 in commit
• Updated Czech translation using Weblate in commit
• Updated Polish translation using Weblate by @Aga-C in commit
• Updated Chinese (Simplified Han script) translation using Weblate in commit
• Updated Serbian translation using Weblate by @eevan78 in commit
• Updated German translation using Weblate in commit
• Updated Danish translation using Weblate in commit
• Updated Italian translation using Weblate by @uovasbattute in commit
• Updated Tamil translation using Weblate by @TamilNeram in commit
• Updated Spanish translation using Weblate by @xuars in commit
• Updated Indonesian translation using Weblate by @arifpedia in commit
• Updated Turkish translation using Weblate in #1200

❤️ New Contributors

• @atirna made their first contribution in #1203
• @xuars made their first contribution
• @TamilNeram made their first contribution
• @uovasbattute made their first contribution
• @G-H-User made their first contribution
• @zork3000 made their first contribution in #1196
• @MB3hel made their first contribution in #1193

On August 26 we released LibreOffice 26.8. Here’s a video highlighting some of the user-facing new features and improvements, with subtitle translations in over 25 languages, thanks to our worldwide community! (Note: the video is also available on PeerTube.)

LibreOffice 26.8 is the first version to display a donation banner in the Launch Centre. This document explains the reasons behind this decision and provides information on The Document Foundation’s sustainability model.

All figures are taken from the financial statements of The Document Foundation Stiftung, based in Berlin, and have been published on the website for every year of the foundation’s existence since its registration.

TDF revenue in 2025

Total revenue amounted to approximately 2.2 million euros.

Of this, over 90 per cent comes from donations, and the remainder almost entirely from the sale of LibreOffice via Microsoft and Apple’s online stores, where the price is set to cover the costs of maintaining the applications on those platforms.

It is worth noting that the same versions available on Microsoft’s and Apple’s online stores can be downloaded freely – and therefore free of charge – from the LibreOffice website.

Over 90 per cent of donations come from private individuals, and less than 10 per cent from public bodies and companies. Therefore, although the suite is widely used by companies and public bodies, it is funded almost entirely by private individuals who contribute small sums according to their means.

How much did TDF spend in 2025

Total expenditure amounted to approximately 1.5 million euros.

Seventy-five per cent of this expenditure was allocated to staff salaries and social security contributions, as well as consultancy contracts. Today, the foundation employs 18 people, 11 of whom have contributed to software development or other related activities, such as quality control.

It is worth emphasising this proportion clearly. Three-quarters of the TDF’s expenditure goes on staff, and the largest share is accounted for by development work, community building and education on the themes of software freedom, open standards and digital sovereignty.

Donations are channelled into constructive activities, rather than administrative costs.

In the past, a significant proportion of development work was awarded to companies that submitted the best bid in response to a tender, but this strategy has changed, and it was decided to bring development expertise in-house so as to steer the software’s evolution and share knowledge with the community.

The surplus in 2025

The surplus is not left unused but is reinvested in the growth already underway: three developers were hired during 2026 and two more will be hired shortly. In addition, various marketing and community development projects are funded from the same source.

The foundation’s expenditure does not follow a uniform pattern relative to its income. The recruitment process takes months, and if income is received before new staff are hired, a surplus will arise that represents planned work rather than unspent money.

TDF also maintains reserves, with the aim of covering at least one year’s operating costs. This figure, of course, increases year on year.

For an organisation with a single predominant source of income, this represents a minimum target. Indeed, a foundation that employs 18 people and supports a community of thousands has obligations towards them that cannot be suspended if income from donations declines.

Why this banner, and why now?

TDF is in good financial health. However, when compared with similar projects, it is significantly underfunded.

Thunderbird, an open-source email client supported almost entirely by donations, received $10.3 million in 2024 – 19 per cent more than the previous year – from over 335,000 individual donors. The Wikimedia Foundation operates on an even larger scale.

LibreOffice has a user base comparable to or larger than that of Thunderbird and a more extensive source code, covering six applications, dozens of file formats and 120 languages, whilst generating revenue amounting to around one-fifth of Thunderbird’s.

The gap is significant because the market has changed. Most people compare LibreOffice with Microsoft 365, and this creates expectations regarding availability on the web, in the cloud and on mobile devices that a desktop-focused development effort is unable to meet.

TDF has published a roadmap for web, cloud and mobile development. Delivering this within a timeframe that keeps pace with market developments requires greater development capacity than current revenue can support.

The banner serves to partially bridge this gap. It appears in the Start Centre – the screen that appears when the suite is launched without any documents open – and is displayed periodically, for example at monthly intervals or following an update. The banner links to the donations page and does not appear anywhere else in the software.

What the banner is not

LibreOffice contains no adverts, does not collect telemetry data and does not require any account, subscription or activation. No features are reserved for paying users. The suite does not transmit documents to a remote service and does not require network access to function. LibreOffice 26.8 contains no generative artificial intelligence features.

Maintaining each of these features incurs costs, as each represents a source of revenue that the foundation has chosen not to exploit.

Advertising-supported software is funded by attention; subscription-based software is funded by the ability to revoke access; and data-driven software is funded by surveillance. TDF has ruled out all three of these options, leaving only the possibility of donations.

The problem with companies

The imbalance between individual and corporate donations is a specific problem that the foundation would like to rectify.

Companies and public bodies deploy LibreOffice on a large scale — in some cases on tens of thousands of computers — and derive a direct commercial benefit from it. Under the terms of the Mozilla Public Licence v2, they have the right to do so, and no one intends to revoke this right.

Unfortunately, very few of these organisations contribute financially to the project. The result is that private individuals are, in effect, subsidising the infrastructure costs of organisations that have considerably greater resources than they do.

Organisations that rely on LibreOffice have at least three ways of supporting it. They can make a donation to The Document Foundation, or purchase an enterprise version from a company within the LibreOffice ecosystem that offers a Service Level Agreement (SLA), professional support and security updates for a period of between three and five years, or pay a company or an individual to develop specific features tailored to their needs.

All these methods support the software, but none is used on a scale that is even remotely comparable to what one might expect given the widespread adoption of the product.

In fact, during 2026, the average monthly number of LibreOffice downloads approached one million, and there were nearly 600 million visits to the website from which updates are downloaded. Based on these two figures, even a very conservative estimate puts the number of LibreOffice users worldwide at over 100 million.

Digital sovereignty is usually discussed in terms of where servers are located and which company holds the contract. Both matter less than the format in which documents are written.

A document is not a piece of paper

The habit of thinking of a digital document as a sheet of paper is understandable and wrong. A sheet of paper carries its own content. Anyone who can read the language can read the page, with no equipment, no permission and no intermediary. A digital document carries no content at all until software interprets it. The file is a set of instructions, and what appears on screen is the result of a program executing those instructions. Change the program and the result may change with it.

This is why documents produced in one application so often look wrong in another: bullet points shift, tables lose their proportions, headings render differently. The content is present. The document, strictly speaking, is not.

The format is the specification that tells software how to perform that interpretation. Whoever controls the format therefore controls what the document means, how faithfully it can be reproduced, and for how long.

What makes a format open

Openness is not a marketing description. It has established criteria, set out in instruments such as the Open Definition and the European Interoperability Framework, and used by public administrations to assess formats for procurement. Four conditions matter most.

The specification must be published in full and freely available. Nobody should need a licence, a fee or a patent settlement to implement it. The format must be usable by anyone for any purpose, without discrimination between users, applications or business models. And it must be governed by a body independent of any single vendor, so that future versions are decided in public rather than in a company’s product roadmap.

These conditions exist for a practical reason. They are what guarantees that a document written today can still be opened in thirty years by software nobody has yet written.

ODF meets these conditions

The Open Document Format was developed in the open under OASIS, the international standards consortium, and became an OASIS standard in 2005. It cleared its Draft International Standard ballot at ISO/IEC JTC 1/SC 34 in May 2006 with unanimous approval and was published as ISO/IEC 26300 that November. The specification is public, royalty-free, versioned, and maintained by a technical committee whose work is a matter of record. Version 1.4 was approved by OASIS in December 2025.

ODF is not the LibreOffice format. It is implemented by a range of applications from different suppliers, and any developer may implement it without asking anyone. LibreOffice uses it natively, which is a consequence of the format’s openness rather than a claim of ownership over it.

OOXML does not

OOXML, the format underlying DOCX, XLSX and PPTX files, carries an ISO number. It was granted one in 2008 through a fast-track procedure whose conduct is now part of the documented history of standards governance.

The number has not produced the effects a standard is meant to produce. The specification runs to several thousand pages, which discourages implementation. It exists in two conformance classes: a Strict variant, which other developers could reasonably support, and a Transitional variant, which preserves legacy behaviours and is what Microsoft Office writes by default. The variant in daily use by hundreds of millions of people is therefore the one that only its originator implements completely. The cleaner variant that competitors could support is largely unused, and has even disappeared from some versions.

A specification that a single implementation alone can satisfy is, in functional terms, a proprietary format with a standardisation certificate attached. This is not an accusation of bad faith. It is a description of what the format does regardless of anyone’s intentions, and it is the reason the distinction is structural rather than moral.

Why this decision comes first

An organisation that adopts a European cloud provider, negotiates strong contractual protections and hosts everything within its own jurisdiction has achieved nothing for sovereignty if its documents remain in a format only one foreign supplier can read correctly. Server location, hosting jurisdiction and procurement clauses are all downstream of the format decision. An organisation that cannot open its own archives without a supplier’s permission is not sovereign over them, wherever those archives happen to be stored.

The exposure grows with time. An individual with a distorted layout has an inconvenience. A ministry holding two decades of legislative drafts, land registries and court records in a format it cannot independently interpret has delegated custody of the public record to a private company, and cannot withdraw that delegation without converting everything it owns.

Who has already acted

Germany’s Deutschland-Stack, the federal framework for sovereign public digital infrastructure, names ODF and PDF/UA as the mandated document formats, to the exclusion of proprietary alternatives. The IT Planning Council, the body through which the federal government and the Länder coordinate public administration information technology, has committed to ODF. NATO and the European Commission have mandated it.

The decision is not a European one. Taiwan adopted ODF as a national standard in 2009 and has required it as the government’s document format since January 2015, a policy its Ministry of Digital Affairs describes in terms of software equality, digital sovereignty and sustainable development. Brazil has required federal executive bodies to follow the e-PING interoperability framework, built on open standards, since 2005. Public administrations on almost every continent have taken comparable decisions over the past two decades.

What has changed recently is the reasoning. The case for moving away from proprietary office software was once made primarily as a cost saving. It is now made as the preservation of independence, meaning the ability of a public body to act without asking permission from a foreign supplier. Several of the migrations announced in the past year were presented in exactly those terms, with the cost argument set aside. At least one European defence organisation has stated that its decision was not about money at all.

The alternative to lock-in already exists, is mature, is an international standard, and is a legal requirement in several European jurisdictions.

Further reading

Start here

• What is Digital Sovereignty
• There is no digital sovereignty without ODF
• The characteristics of a truly open document standard format

Format comparison and lock-in

• ODF is the future, OOXML is the past
• Why ODF and not OOXML
• How proprietary formats have become Microsoft’s main tool for lock-in
• Document formats: a mystery to many
• The non-technical dependency layers: the Calendar and the Invoice

Policy and adoption

• Twenty years on, ODF is still the only open standard for office documents, and the only one governments can trust
• Germany’s sovereign digital stack mandates ODF
• Policy and digital sovereignty – TDF Annual Report 2025
• Euro-Office: sovereign in name only, or in reality too?

Technical reference

• What is the Open Document Format (ODF)?
• A technical dive into ODF
• Understanding ODF file types: .odt, .ods, .odp and beyond
• What’s new in ODF 1.3 and 1.4
• ODF v1.4 approved as an OASIS standard

Berlin, 26 August 2026 – The Document Foundation today announced the availability of LibreOffice 26.8, the new major release of the free and open source office suite, for Windows, macOS and Linux. Development began in December 2025, and the release consolidates the work of 206 contributors, of whom 155 are volunteers.

LibreOffice 26.8 concentrates on three areas: the typographic quality of what the suite produces, the range of writing systems it handles correctly, and the fidelity with which documents survive exchange with other office suites.

Writing systems

The largest single body of work in this release addresses bidirectional and complex text. Writer now detects paragraph direction automatically when documents or plain text are opened or pasted. Line wrapping places end-of-line spaces according to the direction of the paragraph rather than that of the adjacent characters. Object resize handles behave correctly in right-to-left and vertical CJK documents. Bidirectional control characters are now visible alongside other formatting marks. In Calc, typing right-to-left text into an empty cell sets the direction of that cell automatically.

Alignment semantics have been revised accordingly: new documents default to start alignment rather than left, and changing paragraph direction no longer mirrors explicitly left- or right-aligned paragraphs.

Math has gained named functions and operators for the N’Ko and Adlam scripts, used for the Manding languages of West Africa and for Fulani, together with left-pointing vectors and harpoons for right-to-left formulas. The CJK text grid option has been renamed to reflect what it actually does, namely enable the genkō yōshi manuscript grid. Font names recorded in languages other than the interface language are now resolved, so documents authored elsewhere display in the typefaces their authors chose.

None of this work has a commercial market. It was done anyway, because a foundation does not have to ask whether a language pays for itself before deciding to support it.

Typography

Writer introduces the Paragraph Composer, a text layout algorithm that balances word spacing across consecutive lines instead of optimising each line in isolation. The single-line, greedy approach used by word processors has been standard since the technology existed, and produces justified text that alternates between crowded and sparse lines wherever long words fall near a break.

OpenType font variations are now natively supported, allowing variable fonts to be used as designed, including axes that adjust letterform contrast and proportion to the size at which text is set.

Baseline grid alignment now works correctly for text inside frames, and the grid itself can be displayed while editing, with a configurable colour.

Document exchange

LibreOffice Chart provides basic round-trip support for the newer chart types that Microsoft Office writes into OOXML files: box-and-whisker, funnel, Pareto, sunburst, treemap and waterfall. These charts cannot yet be rendered or edited. LibreOffice displays a message identifying the unsupported type and preserves the underlying definition, so that a file opened and saved in LibreOffice returns to its originating application intact. Region map charts carry extensive geographic data that is not preserved; the chart type survives the round trip but little of its content does.

The distinction matters. A specification extended unilaterally by a single implementer is a moving target for every other implementer. Preserving what cannot yet be rendered is the discipline that keeps a document usable beyond the lifetime of the application that created it.

Calc improves the handling of line breaks in referenced cells in XLSX files, and form control elements in XLSX documents now appear in the Navigator.

Spreadsheets

Calc adds Calculated Fields to pivot tables. Data validity can now silently reject invalid entries, restoring behaviour available before version 24.2. Cell styles support relative font sizes. A Shuffle command randomises the order of cells in a range. The border toolbar button remembers and reapplies the most recently used style.

Presentations and drawings

Impress and Draw support multiple page sizes within a single document. Impress adds presentation sections for organising slides into named groups, displays custom slide names beside slide numbers in the panel, and can convert numbered lists to bulleted ones. Several embedded templates are now supplied in both 16:9 and 4:3 ratios, so that background artwork is no longer stretched when the ratio changes. In Draw, the functions of the mouse wheel can be swapped, making zoom the default action.

User interface

The Notebookbar now carries a distinct background colour for each application, so that Writer, Calc, Impress and Draw can be told apart at a glance. Its tabs have category labels and can be scrolled with the mouse wheel or touchpad. Changes to application theme colours no longer require a restart, and theme colours are reachable from the Notebookbar in Impress.

The list of styles is now consistent across the Notebookbar, the Formatting toolbar and the sidebar, and each entry is shown as a preview of the style itself. Style dialogues allow individual properties to be reset to those of the parent style. Paper sizes from A0 to B3 have been added to page settings. Custom dictionaries have gained a search filter, the Hyperlink dialogue can strip query strings from addresses, and resizable dialogues on Windows now have a maximise button. On macOS, the Emoji & Symbols, Dictation and AutoFill menu items are available.

Accessibility

Writer tables now report row and column index information as specified in ARIA, improving how screen readers convey table structure. The special character selector is fully navigable by keyboard.

Databases and automation

Base preserves SQL comments when a query is switched to Design View, and supports filtering on date, time and timestamp columns with the embedded Firebird database.

Python scripts can be created and edited directly from the Macro manager without installing an extension, and can instantiate UNO services through constructors rather than string identifiers. The ScriptForge libraries add a typed input dialogue, functional map, filter and reduce operations on Basic arrays, and a default named pipe that allows the same script to run unchanged inside LibreOffice or against it as a client.

Elsewhere in the suite

• Keyboard shortcuts can be assigned to an individual document, so a shortcut can invoke a style that exists only in one template.
• Writer opens very large documents containing images significantly faster.
• A Draft view hides headers, footers and margins for distraction-free work.
• The Quick Find sidebar searches through comments.
• Table styles in Writer and Calc can be edited, and their internal representation has been converted from a binary format to XML.
• Application theme colour changes no longer require a restart.
• Additional paper sizes from A0 to B3 are available in page settings.
• The style list is now consistent across the Notebookbar, the Formatting toolbar and the sidebar.
• Automated testing now uses VeraPDF to validate PDF output.

No artificial intelligence

LibreOffice 26.8 contains no generative AI features. Documents are not transmitted to remote services for processing, and no component of the suite requires network access to function. This is a deliberate position. Any organisation handling confidential, legally privileged or personal data needs to know where that data goes, and the only assurance that survives an audit is that it does not leave the machine.

How LibreOffice is funded

LibreOffice 26.8 is the first release to display a donation banner in the Start Centre, the screen shown when the suite is launched without opening a document. The banner is shown periodically rather than at every launch, for instance at monthly intervals or after a successful update. It links to the donation page and appears nowhere else in the software.

LibreOffice carries no advertising, no telemetry, no subscription, no account requirement, and no feature withheld behind payment. It is released under the Mozilla Public License v2 and can be deployed without restriction by individuals, companies, schools and public administrations. Development is funded by donations to The Document Foundation and by the companies of the LibreOffice ecosystem. The banner exists because software used by tens of millions of people is not free to maintain, and because every alternative route to sustainability would cost users something they currently have.

Changes users should know about

The Gentium Basic and Gentium Book Basic fonts are no longer bundled. Documents that specify them will fall back to another typeface unless the fonts are installed separately; they remain available for download from The Document Foundation, and current Gentium releases are available from SIL.

New documents default to start alignment rather than left alignment, and changing paragraph direction no longer mirrors explicitly aligned paragraphs. Safe Mode has been renamed Troubleshoot Mode.

Obsolete Java applet configuration has been removed, along with the OfficeBean example in the SDK.

Availability

LibreOffice 26.8 is available immediately from www.libreoffice.org/download/ for Windows, macOS and Linux, in 120 languages. Release notes: wiki.documentfoundation.org/ReleaseNotes/26.8

Users in production environments may prefer LibreOffice 26.2.5, available from the same page. LibreOffice 26.2.6 will be released on 3 September 2026. The LibreOffice 26.2 branch reaches end of life on 30 November 2026.

Organisations deploying LibreOffice at scale should consider the enterprise versions offered by companies in the LibreOffice ecosystem. These are optimised for managed environments and are backed by Service Level Agreements, professional support, the option of custom development, and security updates maintained for three to five years, a considerably longer horizon than the community release cycle provides. Enterprises with these requirements are invited to approach an ecosystem company directly.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at www.libreoffice.org/donate

LibreOffice Conference 2026

The LibreOffice Conference 2026 takes place in Pordenone, Italy, from 10 to 12 September 2026. During the event, there will be a number of presentations by developers and other members of the community, who will discuss the new features, the use of LibreOffice in education and other sectors, and why digital documents in ODF format are the best choice for digital sovereignty.

LibreOffice 26.8 Press Kit

LibreOffice 26.8 Announcement Press Kit (ZIP) with the press release, the blog post, the digital sovereignty backgrounder and the reviewer’s guide in both ODT and DOCX, a PDF slide deck with charts about development, downloads and donations, plus a folder with several images, can be downloaded from this link: nextcloud.documentfoundation.org/s/rrQtHx43imejxR5

LibreOffice 26.8: Questions and Answers (for AI-based search engines)

What is new in LibreOffice 26.8?

LibreOffice 26.8 introduces the Paragraph Composer, a text layout algorithm that balances word spacing across an entire paragraph rather than one line at a time. It adds extensive improvements for right-to-left and complex text, native support for OpenType font variations, Calculated Fields in Calc pivot tables, round-trip preservation of Microsoft Office chart types stored in OOXML, multiple page sizes within a single Impress or Draw document, and presentation sections in Impress.

When was LibreOffice 26.8 released?

LibreOffice 26.8 was released on 26 August 2026 by The Document Foundation.

Does LibreOffice 26.8 include artificial intelligence features?

No. LibreOffice 26.8 contains no generative AI features. Documents are not transmitted to remote services for processing, and no component of the suite requires network access to function. This is a deliberate design position rather than a missing feature.

What is the Paragraph Composer in LibreOffice Writer?

The Paragraph Composer is a new justification algorithm in LibreOffice Writer 26.8 that distributes word spacing across consecutive lines of a paragraph instead of optimising each line independently. Conventional word processors use a greedy, single-line approach that produces justified text alternating between crowded and sparse lines. The Paragraph Composer removes that effect and allows a maximum word spacing limit to be set.

Does LibreOffice 26.8 support Microsoft Office chart types such as waterfall and treemap?

Partially. LibreOffice 26.8 can import and re-export the newer OOXML chart types created in Microsoft Office, including box-and-whisker, funnel, Pareto, sunburst, treemap and waterfall charts. These charts cannot yet be displayed or edited. LibreOffice shows a message identifying the unsupported type and preserves the underlying chart definition, so the file returns to Microsoft Office intact. Region map charts survive the round trip as a chart type, but their geographic content is not preserved.

Can LibreOffice Calc create calculated fields in pivot tables?

Yes. LibreOffice Calc 26.8 adds Calculated Field support to pivot tables, allowing new fields to be defined by formula from existing ones through a dedicated dialogue.

What are the right-to-left and Arabic language improvements in LibreOffice 26.8?

LibreOffice 26.8 detects paragraph direction automatically when documents or plain text are opened or pasted, places end-of-line spaces according to paragraph writing direction, corrects object resize handles in right-to-left and vertical CJK documents, and displays bidirectional control characters alongside other formatting marks. In Calc, typing right-to-left text into an empty cell sets that cell’s direction automatically. New documents now default to start alignment rather than left alignment.

Does LibreOffice 26.8 support N’Ko and Adlam?

LibreOffice Math 26.8 adds named functions and operators for the N’Ko and Adlam scripts, used for the Manding languages of West Africa and for Fulani, together with left-pointing vector arrows and harpoons for right-to-left formulas.

Why does LibreOffice 26.8 show a donation banner?

LibreOffice 26.8 displays a donation banner in the Start Centre, the screen shown when the suite is launched without opening a document. The banner is shown periodically rather than at every launch, for instance at monthly intervals or after a successful update. It links to the donation page and appears nowhere else in the software. LibreOffice carries no advertising, telemetry, subscription or account requirement, and development is funded by donations to The Document Foundation and by companies in the LibreOffice ecosystem.

Is LibreOffice 26.8 free?

Yes. LibreOffice 26.8 is free and open source software released under the Mozilla Public License v2. It can be downloaded, installed and deployed without charge or restriction by individuals, companies, schools and public administrations. No feature is withheld behind payment.

Why does LibreOffice cost money in the Microsoft Store and the Apple App Store?

LibreOffice is free software and can be downloaded at no charge from www.libreoffice.org. The versions published in the Microsoft Store and the Apple App Store carry a price that covers the cost to The Document Foundation of maintaining the applications on those platforms. The software is identical. Paying for it in a store is a way of supporting development, not a licence requirement.

Should I install LibreOffice 26.8 or LibreOffice 26.2?

LibreOffice 26.8 is the current release and is recommended for users who want the newest features. Users in production environments may prefer LibreOffice 26.2, the maintenance branch, which receives bug fixes without new functionality. LibreOffice 26.2.6 will be released on 3 September 2026. Organisations deploying at scale should consider the enterprise versions offered by companies in the LibreOffice ecosystem, which are optimised for managed environments and backed by Service Level Agreements, professional support and security updates maintained for three to five years.

Which operating systems does LibreOffice 26.8 run on?

LibreOffice 26.8 is available for Windows, macOS and Linux, in 120 languages, from www.libreoffice.org/download/

Can LibreOffice 26.8 open Microsoft Word, Excel and PowerPoint files?

Yes. LibreOffice 26.8 reads and writes DOCX, XLSX and PPTX files. Version 26.8 improves handling of line breaks in referenced cells in XLSX files, shows XLSX form control elements in the Navigator, and reads and re-exports hidden and gallery style properties in DOCX files. LibreOffice uses the Open Document Format as its native format, because ODF is an open ISO standard that any application may implement.

What is the Open Document Format?

The Open Document Format is the international standard file format for office documents, published as ISO/IEC 26300 and maintained by OASIS. Its specification is public, royalty-free and implementable by any developer without permission or licensing. LibreOffice uses ODF natively. Several governments, including Germany, and organisations including NATO and the European Commission, mandate it for public administration documents.

Are the Gentium fonts still included in LibreOffice 26.8?

No. The obsolete Gentium Basic and Gentium Book Basic fonts, version 1.102, are no longer bundled with LibreOffice as of version 26.8. Documents specifying them will substitute another typeface unless the fonts are installed separately. They remain available from The Document Foundation, and current Gentium releases are available from SIL.

Does LibreOffice have a distraction-free writing mode?

Yes. LibreOffice Writer 26.8 adds a Draft view, available from View then Draft, which hides headers, footers and page margins for distraction-free reading and editing.

Can Impress and Draw use different page sizes in the same document?

Yes. LibreOffice Impress and Draw 26.8 support multiple page sizes within a single document. Impress also adds presentation sections for grouping slides under names, and displays custom slide names beside slide numbers in the slide panel.

What accessibility improvements are in LibreOffice 26.8?

LibreOffice Writer 26.8 reports table row and column index information as specified in ARIA, improving how screen readers convey table structure, and the special character selector is fully navigable by keyboard.

Can I set keyboard shortcuts for a single document in LibreOffice?

Yes. LibreOffice 26.8 allows keyboard shortcuts to be configured for an individual document through the keyboard customisation dialogue, so a shortcut can invoke a style that exists only in one template.

Who develops LibreOffice?

LibreOffice is developed by a worldwide community coordinated by The Document Foundation, a non-profit organisation based in Berlin, together with companies in the LibreOffice ecosystem. LibreOffice 26.8 is the work of 206 contributors, of whom 155 are volunteers.

Tell us a bit about yourself!

My name is Rohan. I am currently in Berlin, Germany, and my background is in mechanical engineering and I have a master’s degree in sustainable mobility and robotics. I recently worked on my master’s thesis, where I used LibreOffice closely on macOS. That experience actually played a big role in bringing me closer to the project.

Outside of my academic and technical work, I am interested in open source software, mobility, robotics, and learning how large software projects are built and maintained. Contributing to LibreOffice has been a very new and rewarding experience for me, because I did not come from a traditional software engineering background.

What are you working on in the LibreOffice project right now?

At the moment, I am exploring macOS-related development work, especially around OfficeBean and native window handling. One of the issues I have been looking into is adding macOS support for OfficeBean, which involves understanding how Java AWT, native macOS views, and LibreOffice’s VCL layer interact.

So far, my merged contributions have mostly been in the LibreOffice core repository, around C++ cleanup, refactoring, and modernisation. These include:

• tdf#168771 basctl: Convert traditional enums to enum class
• tdf#43157 canvas & chart2: Replace OSL_ASSERT with SAL_WARN_IF
• tdf#143148: Replace include guards with #pragma once

Some of my other patches have not been merged, but they still helped me learn a lot about the codebase, Gerrit, code review, and how to communicate with reviewers.

I also contributed to the developer documentation by adding macOS-related LCOV information to the Development/LCOV wiki page. I wanted to document what I learned so that other macOS contributors could have a clearer path when using coverage tools.

Why did you choose to become a TDF member?

I chose to become a TDF member because LibreOffice has personally helped me a lot, especially during my master’s thesis. While using it closely, I noticed bugs and small rough edges, and that made me curious about how such issues are reported and fixed.

After attending the LibreOffice Conference in Budapest, I became much more interested in the community behind the project. I saw how welcoming and serious the community is about open standards, user freedom, and long-term software sustainability.

For me, becoming a TDF member is a way to give back to a project that supported my own academic work. It is also a way to stay connected with the community and keep learning from people who have much more experience in open-source development.

Anything else you plan to do in the future? What does LibreOffice really need?

In the future, I would like to continue improving my understanding of LibreOffice’s core codebase, especially in areas related to C++, macOS, VCL, and developer tooling. I am still learning, so I want to take on tasks step by step and contribute in a way that is useful and maintainable.

I think LibreOffice really benefits from better onboarding paths for new contributors, especially people who are not coming from a pure computer science background. The codebase is large and can feel intimidating at first, so documentation, mentoring, and small well-described tasks are very important.

LibreOffice also needs continued attention on platform-specific issues, including macOS, because many users depend on it every day across different environments. Even small improvements can make a big difference for users.

For me, contributing to LibreOffice has been both a technical learning journey and a way to give back. I really appreciate the patience and support of the community, because it has helped me ask better questions, understand code review better, and gradually become more confident as a contributor.

It has become a commonplace to describe the Microsoft 365 Ribbon as the finest office interface available — the most polished to look at and the most ergonomic to use. The claim is repeated so often that it tends to pass unexamined. It deserves examining, because hidden inside it is an assumption that quietly does most of the work: the idea that there exists a single best interface at all.

A competent design — for one kind of user

Let us begin by granting what is true. The Ribbon is a capable piece of design. It was built to help an occasional or intermediate user discover features by browsing rather than by memorising, and for that user it does its job well. Saying so is not a concession wrung out reluctantly; it is simply accurate, and any honest discussion should start there.

But “well-designed for a particular user” is not the same thing as “best interface,” and treating the two as equivalent is where the reasoning slips. An interface optimised for one persona is, by construction, less suited to the others: the power user who works from the keyboard and resents losing vertical screen space, the migrating user carrying twenty years of muscle memory, the user who depends on assistive technology, the user on a small or low-resolution display. A single fixed layout cannot be best for all of them at once. It can only be best for some, at the expense of the rest.

Ergonomics is a trade-off, not a verdict

The same applies to the ergonomic claim, only more sharply, because ergonomics is something one measures rather than asserts. The research on interface efficiency is consistent on one point: how well an interface performs depends on the task, its frequency, and the expertise of the person doing it. Discoverability and raw throughput pull in opposite directions. An interface that makes features easy to find for a newcomer is rarely the one that lets an expert move fastest, and the reverse is equally true.

So the Ribbon makes a trade. It spends vertical screen space and a measure of expert speed to buy browsability for the less frequent user. That is a perfectly reasonable bargain — for the people it was struck on behalf of. Calling it “the best ergonomics,” though, simply declines to name what was given up to get there. There is no free lunch in interface design; there is only a choice about who pays.

The real question: who decides?

This brings us to the point that actually matters. When a product ships a single interface, it has made the ergonomic decision on the user’s behalf and removed it from their hands. The trade-off still exists — it has merely been settled by someone else, once, for everyone.

LibreOffice takes the opposite path. It offers the traditional menu-and-toolbar layout, the Tabbed interface, Tabbed Compact, the Groupedbar, a Sidebar, and a Single Toolbar mode, and it lets each user choose the one that fits their work, their hardware, and their habits. This is not a substitute for a “real” Ribbon, nor an apology for the lack of one. It is the more mature answer to the ergonomic question, for a simple reason: the only person who can properly weigh these trade-offs is the one actually performing the task. Choice is not the consolation prize. Choice is the point.

What 26.8 changes, and what it does not

LibreOffice 26.8 will bring an improved Tabbed interface — the layout closest in spirit to the Ribbon. It is worth being precise about what this means, because it is easy to misread. The improvement widens the range of good options; it does not narrow it. It is emphatically not an admission that the menu-based interface was lacking, nor a signal that it is on its way out.

The traditional menu-and-toolbar interface remains a fully supported, first-class choice, and it will not be deprecated. An ecosystem that adds options without taking any away is the exact opposite of one that imposes a single layout and asks everyone to adapt. Adding a better Tabbed interface while keeping the classic one intact is not a contradiction. It is the whole philosophy, working as intended.

The same principle, one layer down

This approach to the interface is not an isolated quirk. It is the same principle that governs how LibreOffice treats document formats, and the parallel is worth drawing out, because it reveals a consistent way of thinking about who software is meant to serve.

LibreOffice adopts the open standard, the OpenDocument Format, as its native format — the one it reads and writes by default, without compromise. At the same time it continues, release after release, to improve its support for the proprietary formats, so that users who must exchange files with others are served as well as the technology allows. The standard comes first; support for the proprietary follows, and keeps getting better, because that is what users need.

Set this beside the other approach and the contrast is stark. There, support for the open standard is present but kept deliberately limited — limited by choice, not by capability — while the proprietary format remains the privileged default. One model treats the open standard as the foundation and works continuously to serve the user across every format they encounter. The other treats the standard as a box to be ticked and the user as someone to be kept in place.

It is the same pattern in both cases. On one side, a tool that fits itself to the user — in its interface and in its formats alike. On the other, a user asked to fit themselves to the tool. There is no best interface, only the one that fits; and the software that offers the most well-made ways to fit, rather than a single default decided in advance, is the one that takes the user most seriously.

LibreOffice is a worldwide project made up of hundreds of people: volunteers, developers at ecosystem companies, and the 18-person team at The Document Foundation (the non-profit entity that coordinates the project and community). So, what has the team been working on recently? Here’s a quick summary:

Release Engineering

• Tagged, built, and distributed LibreOffice 26.8.0 Release Candidate 2
• Enabled MAR updates for cross-updates from 25.8.7 and 26.2.4 to 26.2.5
• Reviewed patches
• Tested new Windows build bots in production
• Investigated and fixed incorrect permissions in daily Debian packages

Scripting

• Investigated an extension developer’s issue exporting BASIC macros as an extension
• Identified a debug-build assertion that does not appear to affect release builds
• Added a UI test to help prevent future regressions in macro export

Code and Accessibility

• Discussed proposed accessibility improvements on the LibreOffice accessibility mailing list
• Analyzed and fixed tdf#172831: customized NotebookBar tab names were not localised after upgrading
• Released LibreOffice Viewer for Android 26.2.5 on Google Play, F-Droid, and the Meta Horizon Store
• Discussed tdf#172885, a LibreOffice-specific Qt theme/style. Explored an upstream Qt stylesheet-environment-variable approach, then implemented LibreOffice command-line support for setting the stylesheet
• Posted and reworked the macOS-specific parts of the Qt VCL work
  • Reworked the changes in response to comments, then merged them
• Worked on generalising macOS scaling patch
• Made the Reset button dialog action ID well-known across the codebase

QA

• Announced LibreOffice 26.8 RC1 availability for testing
• Upgraded external libraries:
  • NSS to 3.126
  • libffi to 3.7.1
• Improved automated tests:
  • Factored common code from CppunitTest_sc_swarmsolvertest
  • Added ARRAYTOTEXT function tests as FunctionsTest
• Fixed crashes and warnings:
  • Fixed a null-pointer dereference warning in Writer
  • Fixed a crash in ThemeExport::write
  • Fixed a crash in OutMarkdown_SwTableNode
• Tested and commented on Qt6 style and theming work for tdf#172885
• Completed hiring tasks and code reviews
• Investigated regressions involving CJK font names and the CJK bullets gallery
• Fixed two build/SDK issues:
  • Fixed a build issue with Visual Studio 2026 18.7.0
  • Fixed missing cross-platform .NET binding files in the SDK (tdf#165585)
• Continued work toward resolving headless Windows/fontconfig build issues required for Qt6 on Windows

Mentoring

• Reviewed six substantial patch submissions
• Completed GSoC mentor tasks

Design

• Triaged Bugzilla tickets
• Participated in the weekly UX and ESC meetings
• Published extensions and managed comments
• Supported community growth through the @libodesign social media account
• Completed several design reviews
• Prepared the Base survey
• Contributed patches:
  • tdf#115805: corrected increments in numbering dialogs
  • tdf#172739: harmonized NotebookBar tab order

Documentation

• Updated online Help with fixes for Master, 26.2, and 25.8
• Updated Help pages through bug triage, contributor patch reviews, fixes, and housekeeping
• Contributed Help improvements, including:
  • Adjusted left margins for paragraphs in tables
  • Refactored the AutoCorrect Options page
  • Updated documentation for “To page” anchoring
  • Added “Page Break” to Find & Replace attributes
  • Reverted removal of “Page Style” from Find & Replace attributes
  • Muted localisation processing in selected Python and BASIC code lines
• Supported ongoing community updates to the Guides
• Helped newcomers
• Worked on the Bookshelf project, including sanitising the Impress Guide

Marketing

• Announced and promoted new TDF members and the new marketing position
• Maintained social media activity, updates, and responses
• Coordinated conference logistics and prepared the first conference-program draft
• Drafted sections of the TDF Annual Report 2025
• Updated journalists’ mailing lists and database
• Published blog posts about ODF and maintained the blog
• Monitored donations, downloads, media clippings, and download-support requests
• Managed budget-related activities
• Worked on preparations for LibreOffice 26.8 release

So that’s what the team is working on – and this is all thanks to your donations, which help to pay the team members. But as mentioned, this is just a small part of the LibreOffice project activity – the biggest work is being done by hundreds of other people around the world. Thanks to all of you

When governments and organisations talk about “digital sovereignty,” they usually mean one thing in practice: the ability to choose, control, and if necessary replace the software they depend on — without asking permission from a vendor.

It sounds simple. It rarely is.

Document software sits at the centre of almost every organisation’s operations. Contracts, reports, budgets, policy documents, public communications: they all live in files. And for decades, the format of those files — and therefore the tools required to open, edit, and share them — has been controlled by a single commercial entity. That is not sovereignty. That is dependency with a friendly interface.

LibreOffice Technology exists to make genuine sovereignty possible. Not as a promise, and not as a political statement — but as a technical architecture that removes the dependency by design.

This post explains what LibreOffice Technology actually is, why it is categorically different from a “free alternative to Microsoft Office,” and why it is the only open platform capable of supporting software that is fully compatible with the demands of digital sovereignty. It also reviews what several months of deployments, policy decisions, and one very public debate over what “sovereign” actually means have confirmed about that architecture since we first started making this argument.

Beyond the Application: LibreOffice Technology as a Platform

Most people who encounter LibreOffice encounter it as an application — a word processor, a spreadsheet editor, a presentation tool. That is a reasonable introduction, but it misses what makes LibreOffice Technology significant.

LibreOffice Technology is the underlying platform on which LibreOffice — and a growing number of other products — is built. It is a modular, open-source software framework for creating document applications. It includes rendering engines, import/export filters for dozens of file formats, scripting infrastructure, accessibility layers, and interfaces for integration with operating systems, cloud environments, and enterprise software stacks.

Think of it the way you might think of a general-purpose operating system kernel: the kernel itself is not what users interact with directly, but it is what makes everything else possible — and it is what determines whether the system is genuinely open or merely open-looking.

LibreOffice Technology is governed by The Document Foundation (TDF), a non-profit foundation incorporated under German law. Its source code is publicly available, its governance is transparent, and its development is carried out by a global community of contributors from dozens of countries and organisations — including Collabora, allotropia, Red Hat, and many others.

No single company controls it. No acquisition can change its licence. No pricing decision by a distant board can determine whether your organisation can keep using it next year.

That is what a platform for digital sovereignty looks like.

Open Standards Are Not Optional: The Role of ODF

Sovereignty over software is meaningless if the data is not equally free.

A document format is not just a technical specification. It is a commitment about who can read your files in ten years, which tools can process them today, and whether you are locked into a particular vendor’s upgrade cycle to maintain access to your own information.

LibreOffice Technology is built around the Open Document Format (ODF), an ISO/IEC international standard (ISO/IEC 26300) developed through an open, multi-stakeholder process. ODF defines how text, spreadsheets, presentations, and other document types are stored — in a way that any conforming application can read and write, regardless of who made it or on what platform it runs.

This matters in ways that are easy to underestimate. When a public administration stores its records in ODF, it is not dependent on any vendor to access those records in the future. When a hospital uses ODF for patient documents, it can switch tools without migrating data. When a ministry publishes a policy document in ODF, any citizen with any compliant application — on any operating system — can open it.

Contrast this with proprietary formats that, despite occasional published specifications, remain under the effective control of the companies that defined them. “Open enough” is not the same as open. Earlier this month, we set out a first version of what separates the two: a thirteen-criterion definition of what a genuinely open document format requires, from public specification and royalty-free implementation through to independent governance. That short version is only the opening statement — we originated this framework, and a fuller, more rigorous edition is in development, applying all thirteen criteria in detail to ODF, OOXML Strict, and OOXML Transitional in turn.

LibreOffice Technology’s commitment to ODF is not a preference. It is an architectural principle. The platform is designed around the assumption that the data belongs to the user, not to the software.

The Platform Others Build On

One of the clearest indicators that LibreOffice Technology is a genuine platform — not just a standalone application dressed up in platform language — is the ecosystem of products built on top of it.

Collabora Online, a cloud-native document editing solution deployed by enterprises, governments, and cloud providers across Europe and beyond, is built on LibreOffice Technology. Collabora’s 2025 merger with allotropia — whose engineering team brought deep WebAssembly and vertical-application expertise into the same organisation — is itself an example of how the ecosystem consolidates and grows without ever touching the underlying platform’s governance. Other commercial and community products remain in active development by organisations that have chosen LibreOffice Technology precisely because it provides a stable, open foundation they can build on without acquiring permission from or paying royalties to a gatekeeper.

This ecosystem diversity is itself a form of sovereignty insurance. If one vendor stops supporting a product built on LibreOffice Technology, the platform continues. If a government or organisation builds custom tooling on top of LibreOffice Technology, it owns that investment. If the community of contributors shifts, the codebase remains — licensed under the Mozilla Public License 2.0, which ensures it can never be made proprietary.

A sovereign digital infrastructure is not one built on a single vendor’s promises. It is one built on a platform that multiple independent actors develop, maintain, and depend on. LibreOffice Technology is that platform.

The Euro-Office Test Case: Why Compatibility Is Not Sovereignty

No event tested this argument more directly than the emergence of Euro-Office, the European coalition initiative that surfaced this spring under the digital sovereignty banner.

Our first reaction, when the initiative made its opening announcement, was blunt about the architecture: a European suite built around full compatibility with Microsoft’s OOXML formats does not escape dependency, it relocates it. The hosting moves to Europe. The format — and the vendor who controls its evolution — does not.

Euro-Office’s formal pre-announcement in June moved the conversation forward. It leaned much further into a commitment to open standards, and we welcomed that shift while correcting one detail then circulating in the press: LibreOffice, developed under this Foundation for a decade and a half by a global — and substantially European — community, was never absent from the field Euro-Office proposes to enter. We also set out, plainly, the one destination consistent with the sovereignty the coalition invokes: ODF as its native document format, not merely a supported one.

The distinction is not a technicality. As we laid out in A Standard in Name Only, the version of OOXML every proprietary vendor ships by default is the Transitional conformance class — built to preserve decades of undocumented legacy behaviour from Microsoft Office versions of the 1990s, not the cleaner Strict variant an independent implementer could actually build to. An office suite that treats OOXML Transitional as its working format, however European its servers, is building on a specification only one vendor has ever fully implemented. What Euro-Office does next will show whether the coalition takes the final step from sovereign hosting to sovereign format.

Where Sovereignty Is Not an Abstraction: Real Deployments

Digital sovereignty is sometimes discussed as though it were a future aspiration. For a growing number of organisations, it is a present operational reality — and this year produced the clearest evidence of that yet.

In March, Germany’s Federal Ministry for Digital and State Modernisation folded ODF, alongside PDF/UA, into the Deutschland-Stack, the technical framework that will govern digital infrastructure across every level of German public administration. OOXML did not make the list. “This is not a recommendation or a preference, it is a mandate,” said Florian Effenberger, TDF’s Executive Director, at the time — and as we argued in the days that followed, it is a decision the rest of Europe, and every digital policy advisor reading it, should be studying closely.

Germany is not alone. The Italian Ministry of Defence has spent several years migrating well over 100,000 workstations to LibreOffice under its LibreDifesa programme, reducing dependency on proprietary desktop software and building direct control over its document infrastructure. The French Gendarmerie nationale has pursued the same goal at comparable scale over two decades, moving the substantial majority of its computing estate to open-source software as part of a deliberate strategy to reduce vendor lock-in. And in August, in a two–part interview with the Austrian Bundesheer, we heard directly from the team that has moved 16,000 workstations off Microsoft Office: the decision traced back to a 2020 review of what guarantees existed for running office software without a cloud connection at all. The City of Munich’s long-running open-source initiative — despite its complex political history — remains the clearest illustration that sovereign document infrastructure is both technically achievable and organisationally demanding, at scale, inside a large public administration.

These are not proofs-of-concept. They are operational deployments in organisations for which the ability to control their own software stack is not an ideological preference but a security and continuity requirement.

They also illustrate something important: the question is no longer whether LibreOffice Technology can support enterprise-scale sovereign deployments, or whether governments will choose ODF when the choice is put to them plainly. Germany has already answered both. The question now is how quickly the rest of Europe follows.

Why “No Single Vendor Can Pull the Plug” Matters More Than Ever

In 2011, Oracle donated the OpenOffice.org codebase to the Apache Software Foundation and largely stepped back from development. The product that had been the leading open-source office suite effectively stalled. Development slowed, releases became infrequent, and the community migrated — mostly to LibreOffice, which had been founded in 2010 precisely to create a more independent governance structure.

This episode is instructive. A product can be open-source and still be effectively controlled by a single corporate actor. When that actor’s priorities change, the product suffers.

Much of what we have published this year has been an attempt to make that risk structural rather than anecdotal. The invisible architecture of lock-in traces how dependency on a document’s format cascades into dependency on the rendering engine that displays it and, beneath that, the fonts that give it its final shape — three technical layers, each one obscuring the one beneath it. The Calendar and the Invoice extends the same argument to two layers that are not technical at all: the migration deadline a vendor sets, and the subscription price it charges. Five layers, and what unites all of them is a single absence — the user has no exit.

The Document Foundation was designed with this risk explicitly in mind. TDF’s statutes prevent any single company or individual from controlling the foundation. Its governance model distributes decision-making across an elected board, a membership body, and an engineering steering committee. The LibreOffice Technology codebase cannot be re-licensed, sold, or restricted by any single party.

This is not an accident of history. It is an architectural decision about governance — as important to digital sovereignty as any technical specification.

What Sovereignty Requires of a Platform

Digital sovereignty is not a binary condition, and it is not the same thing as self-sufficiency. As we argued in July, it is not about owning everything — no institution, and certainly no continent, is going to reimplement the entire computing stack from silicon upward. It is about ensuring that nothing essential can be taken away. Different organisations will weigh that differently, but a platform that genuinely enables it must satisfy several non-negotiable criteria:

Open source with a robust licence. The code must be inspectable, modifiable, and redistributable. Not just available — auditable and forkable by any qualified party.

Open standards at the data layer. File formats must be governed by independent standards bodies, not by the platform vendor.

Independent governance. No single commercial entity should be able to make decisions — about licensing, pricing, feature development, or platform direction — that override the interests of the broader community of users and contributors.

An active, diverse contributor base. Sovereignty requires resilience. A platform maintained by a single company is a single point of failure.

Ecosystem depth. Sovereignty at the document layer requires that the platform be capable of supporting the full range of an organisation’s document needs — not just basic editing, but integration with enterprise systems, accessibility compliance, multi-language support, and cloud deployment.

LibreOffice Technology satisfies all of these criteria. We are not aware of another document software platform that does.

Sovereignty Starts Here: The Story So Far

When we first sketched out this argument, we framed it as the opening of a campaign. Several months on — with the Euro-Office debate still very much alive, Germany’s Deutschland-Stack mandate now a matter of public record, and the US CISA’s own guidance on open-source verifiability landing squarely in the same argument — it makes more sense to call it what it has become: an ongoing, evidence-led case, not a one-off pitch.

If you want the fuller version, the pieces above trace most of the argument in detail: what digital sovereignty actually means and doesn’t mean; the layered architecture of lock-in and its non-technical extensions; what separates a genuinely open format from one that merely claims the label; the Euro-Office exchange in both its instalments; and, most concretely, the Austrian Bundesheer’s own account of why and how it moved 16,000 desktops off Microsoft Office. Together with the Deutschland-Stack decision, they are the evidence behind everything argued in this piece.

We are not finished. There are interoperability failures we haven’t yet written about, further national deployments to document as they happen, and — with LibreOffice 26.8 due for release on 26 August — a platform that keeps giving us more to report on. Watch this space for what comes next.

If you are a journalist or analyst covering digital sovereignty, open source, or public-sector technology, we would like to talk. If you are an organisation considering or using LibreOffice Technology and would like to share your experience, we would welcome the conversation. Reach out to our communications team at media@documentfoundation.org.

Digital sovereignty requires infrastructure that is genuinely open. That infrastructure exists. It is called LibreOffice Technology, and — as the months since we first wrote that line have gone on to show — this really is where the story starts.

The Document Foundation is the non-profit organisation behind LibreOffice. It is independent, non-commercial, and governed by its membership community. LibreOffice Technology is the open platform on which LibreOffice and a growing ecosystem of document applications are built.

Tags: digital sovereignty, LibreOffice Technology, open document format, ODF, open source, The Document Foundation, public sector IT, vendor lock-in, document software, Euro-Office, Deutschland-Stack

Further Reading on This Blog

The posts behind the argument above, in the order they were published:

• Dear Europe: Germany has shown the way forward — March 2026
• Euro-Office: sovereign in name only, or in reality too? — April 2026
• A Standard in Name Only: What OOXML Transitional Tells Us About Format Sovereignty — June 2026
• Euro-Office, open standards, and native ODF — June 2026
• The Invisible Architecture of Lock-In: the Layering of Dependencies — June 2026
• The Non-Technical Dependency Layers: the Calendar and the Invoice — July 2026
• What Is Digital Sovereignty — July 2026
• CISA Publishes Open Source Security Guidance: Verifiability Is the Difference — August 2026
• The Characteristics of a Truly Open Document Standard Format — August 2026
• Why and How the Austrian Military Moved to LibreOffice (Part 1) — August 2026
• Why and How the Austrian Military Moved to LibreOffice (Part 2) — August 2026

External Resources

• ISO/IEC 26300:2006 — Open Document Format for Office Applications, the official ISO standard page for ODF.
• Public Money? Public Code!, the Free Software Foundation Europe’s campaign for public code as the default for publicly funded software.
• European Interoperability Framework, the European Commission’s guidance on interoperable digital public services.
• Deutschland-Stack, the German federal government’s official site for its sovereign digital infrastructure programme.

Tell us a bit about yourself!

I’m Aleksi, and I live in Oulu, northern Finland. I graduated this spring with a bachelor’s degree in business information technology, and before that I did a vocational degree in software development. Work-wise, my background is in software engineering: I worked on a secure Android smartphone, mostly fixing operating system bugs.

Outside of that, I’m into retro computing: old machines, old phones, and the software that ran on them. There is a lot to learn from software written back when it could only be shipped on physical media. Every time I sit down with a piece of old software, I notice a detail I want to try building myself: an interesting design decision that makes the UI stand out, or a feature that makes me wonder how on earth it was done.

I also like to hang out at my local hacklab and volunteer at gaming festivals. And of course, I like to work on LibreOffice too. What makes LibreOffice interesting to me is that its codebase has a long history. Reading the code and going through the commits allows me to look back in time and see how the software has evolved over the years.

What are you working on in the LibreOffice project right now?

I’m currently working on smaller code fixes. I pick up bugs from Bugzilla, try to reproduce them, and ultimately submit a patch that fixes the issue. In a codebase the size of LibreOffice one can’t just aimlessly duct tape a solution and hope it works. One has to understand the root cause to be able to look in the right place and understand the effect that the change has on the bigger picture.

Coming from a background of debugging Android, I quite enjoy that part of the work. Also, everyone in the community is genuinely great to work with. Code reviews in particular taught me a lot, when a more experienced developer pointed out something that I’d never have spotted myself.

Why did you choose to become a member of The Document Foundation?

Becoming a member felt like a way of saying that I’m in this for the long term rather than just passing through. Before I started contributing, I was a bit scared of putting code out under my own name. I felt like my code wouldn’t be good enough, and that I could only contribute to open source after decades of development experience.

Boy, was I wrong. Going through the issues thoroughly (the community likes to leave hints in Bugzilla comments), understanding the problem, and submitting the best patch I could manage turned out to be enough. Having a mentor and the community’s support on IRC, where I could ask questions whenever I needed to, helped a lot too.

Anything else you plan to do in the future?

I’m planning to move from smaller fixes towards more interesting bugs (our Bugzilla doesn’t contain any hard issues, only interesting ones). I’m also looking forward to working with other teams. I’ve been interested in quality assurance and documentation lately, so picking up small tasks in those areas to build up knowledge for larger work sounds like fun to me.

What does LibreOffice really need?

This is a tough question. At least in Finland, LibreOffice needs to be offered as a real option in schools. That also means we need more people who know it well enough to teach it.

On a lighter note, we recently watched the Excel World Championships at the hacklab. I’m not sure it’s what LibreOffice actually needs, but it would be great to see people who are seriously proficient with Calc solving problems and competing. In its simplest form, it could be a community competition to see who solves the most brain teasers.

For the past few months, we’ve been developing all kinds of features for the future GIMP 3.4 release. We noticed recently that our changelog was getting quite long - a good problem to have!

While there’s been a lot going on internally, it’s been a while since we made a public progress report. So we want to share details on some of the new features and UX improvements that’ll be available in the first development release, GIMP 3.3.2. This won’t be an exhaustive list (we have to save at least some news for the release itself!) but hopefully it will give you some insight into the current direction and progress of GIMP’s development.

New Project File Format⁠

The big focus for maintainer Jehan recently has been developing a new project file format for GIMP.

XCF has been GIMP’s primary project format since 1997, and it has served many users well. Over time however, we’ve observed more and more limitations of the binary XCF format. Among other issues, it does not easily support very large or complex projects, such as the multi-page and animation features currently planned for GIMP 3.6.

The new project file format will follow a more common “zipped XML” structure. While the technical details are still being designed and implemented, this change will allow for faster saving since we’ll only need to update parts of the file instead of the whole thing each time. It will also set the stage for much desired features such as auto-saving, which will now be much more feasible.

That said, XCF is not going away! Backwards compatibility is important to us, and we will continue to support loading XCFs in all future versions of GIMP. (For instance, we’re quite proud that a XCF file made by a small company for their logo in 1998 still renders the same way in the latest version of GIMP)

However, going forward we will only add support for saving/loading new features in the new project file format once it is finalized.

MyPaint Brush: Spectral Blending⁠

During GIMP 3.2’s development, we upgraded to a newer version of the MyPaint brush engine. While this brought new brushes and canvas interactions to the MyPaint Brush Tool, one feature that was left out was Spectral Blending.

Spectral Blending simulates the effects of blending physical pigments in digital art. For example, blending yellow and blue will produce a green color instead of darker yellow, and blending red and yellow will create an orange mix.

Fortunately, new contributor Cassidie Grogan picked up the slack and implemented this feature. There is now a Spectral Blending checkbox in the MyPaint Brush Tool Options. If checked, the new blending method is used. You can control the strength of the blending with the Pigment slider.

In addition, maintainer Michael Natterer improved the MyPaint Brush preview code to display at their full size instead of 48x48 pixels. This fixes an issue where the previews appeared blurry on larger screens.

Non-Destructive Editing⁠

Alx Sa has continued making updates to our non-destructive filter code. To list a few:

You can now apply filters non-destructively to Layer masks! To go along with this, the filter popover has been redesigned by Reju to show the active filters for both the layer and its mask, so you can interact with both on the same screen.

The Gradient Tool can now be used non-destructively! If you check Editable Gradient in the Tool Options, the gradient you create will be added to the filter stack like any other effect. You can toggle its visibility, rearrange its position in the filter stack and delete it. You can also edit the gradient, which will switch back to the Gradient Tool to let you make further changes.

Filters without dialogs (such as Invert) can now be applied non-destructively on non-raster layers such as layer groups and link, text, and vector layers.

PSD Support Improvements⁠

Normally we list all file format updates in a combined section, but there has been so much work done on PSD support (and by so many people) that we wanted to highlight it in more detail.

First, new contributor Frank Teklote has been busy improving our compatibility with PSDs. His big project for this release was creating a PSD metadata export procedure for TIFFs and JPEGs. This complements our existing PSD metadata import procedure, meaning that if you import a JPEG with paths or a TIFF with layers (or create one in GIMP), that information can now be retained in the exported image.

Another great thing about Frank’s work is that as we continue to improve our PSD compatibility, the TIFF and JPEG export features will automatically get those updates too!

Related to that, Jacob Boerema has implemented PSD Descriptor import support. Most of our current PSD support has been based on the public Adobe specification. This document was last updated in 2019 however, and modern PSDs use a relatively undocumented text format called Descriptors to store many features.

Now that GIMP can read descriptors, we’ve begun drastically improving our PSD import support. To list just a few updates: text layers are now editable, a number of adjustment layers and modern layer styles appear as their GEGL equivalents, and solid color shapes are imported as vector layers. This is an active area of development, including by two of our GSoC students Akascape and Waris Maqbool. We hope this work will make it easier for GIMP users to interact with existing PSD projects!

Native File Chooser Dialogs⁠

We have always used the file chooser dialog provided by the GTK GUI library for people to find, load, and save files in GIMP. While the file chooser does the job, it often works differently than the “native” file chooser on non-GNOME platforms like Windows, macOS, and KDE. Additionally there have been some changes to the UI of this dialog in GTK3, which has inspired some strong feedback in our issue tracker!

Therefore, Alx Sa has begun porting GIMP’s file choosers to the “native” option provided in GTK3. This means that when you open or save a file, you will see your platform’s standard file chooser dialog instead of the GTK dialog (unless your platform uses that already, in which case there will be no change!)

Many of the simple dialogs have already been converted. Those with more complex additional features will require some workflow redesigns, which we’re still developing.

User Experience and Interface Updates⁠

A lot of new and existing contributors have submitted improvements to GIMP’s user interface and its user experience. We wanted to highlight their efforts, and encourage you all to continue sharing your feedback on our design issue tracker.

Designer Denis Rangelov has been hard at work updating GIMP’s UI icons. He recreated our layer lock icons to create a more consistent look.

He also took on the monumental task of converting all 78 of our cursor icons to SVG, which will allow us to scale them for higher resolution displays without losing quality!

Original Raster Cursor	Denis’s Vector Cursor

There have been reported performance issues when drawing or zooming into the canvas when the canvas view was rotated. New contributor woot000 diagnosed the problem and created a fix. Now the “checkerboard” transparency pattern no longer rotates when the canvas does, which significantly boosts performance when painting or editing. They also fixed a related issue where the checkerboard pattern would disappear when zooming into the canvas past a certain point.

Gabriele Barbero implemented a redesign of the Search Action UI which was designed by Denis Rangelov. The new layout makes the associated shortcut key more visible, and is more consistent with the menu layouts.

Bruno Lopes has been working to fix issues with pop-up dialog displays on macOS. Since traditionally we have fewer macOS developers compared to other platforms, we’re really happy to see improvements for these users!

New contributor Andreas Vukman improved our Pattern dock display. Now smaller patterns tile to fill the available space, creating a consistent preview for all patterns instead of having some patterns display with odd amounts of padding. We think it makes the dock look much nicer!

Richard Gitschlag has updated the on-canvas text editor to allow selections when you Shift+Click in the text. It should now work similar to what you can do in a word processor like LibreOffice.

In previous versions of GIMP, you imported or exported metadata from the Metadata Editor by selecting an option in a dropdown. Ahmed E. Yassin has made this process more intuitive (and more consistent with the rest of GIMP’s UI) by replacing the dropdown with two buttons instead.

Ondřej Míchal reviewed several portions of GIMP’s UI and replaced many instances of the Spin Entry widget with Spin Scale. The Spin Entry widget is difficult to use when the width is shrunk, so this change improves usability in many areas of the UI.

Assorted Changes and Fixes⁠

Our four GSoC interns have been continuing their work since the midpoint update. Recently, Waris Maqbool‘s Sharpen filter was merged into GEGL, so it’ll be available in the next GEGL release.

New contributor Dimitriy Ryazantcev has submitted several patches for improving our Windows ICO/CUR/ANI support. They’ve already fixed the rendering for certain 32bit ICO formats and made our loading and preview algorithms better match the Windows specification.

Estecka has fixed a rendering issue when applying NDE filters on passthrough layer groups, which made the image look different depending on whether the group had child layers or not.

New contributor Petr Vorel fixed a bug where pressing Alt+0 did not open the tenth most recent image in your history.

Lloyd Konneker, our main Script-fu contributor, fixed a regression in third party scripts where the number range for certain parameters wasn’t shown in the GUI.

Jacob Boerema and Alx Sa have responded to and patched a number of security reports about potential flaws in some of our image plug-ins.

What’s Next⁠

There’s more in-progress work that we look forward to sharing with you all soon!

There is not an official 3.3.2 development release yet, as several roadmap items are still in-progress. If you’re feeling really adventurous and just can’t wait, you can try our “nightly” builds. Instructions are under the Automatic Development Builds header.

In the meantime, we are planning to release GIMP 3.2.6 in the coming weeks. It is a stable release so it won’t include many of the new features described here. However, it will have a number of important bug fixes and small improvements. We’ll discuss these more in the 3.2.6 release news post!

The LibreOffice Conference 2026 will take place in Pordenone, Italy, from September 10 – 12. And now the schedule is online, with:

• 8 conference tracks
• 64 sessions
• 49 speakers

Click here to view the schedule

This is the second part of our interview with the Bundesheer (see here for the first).

At the LibreOffice Conference 2025, you showcased the new LibreOffice features sponsored by the Austrian Armed Forces. How did that come about?

From the very beginning, we clearly recognised the need to further develop LibreOffice. Before finalising our plans, we also examined how we could continue to develop the product. Ultimately, we issued a Europe-wide, open call for proposals to secure both support and development capacity for LibreOffice. The way we selected the product enhancements stemmed in part from this preliminary study, because we had identified specific import capabilities and compatibility requirements.

That’s one major aspect: improving interoperability in line with our needs. The other focus was on improving LibreOffice based on ongoing user feedback and feedback regarding collaboration with external organizations. One example of this was the “Notes” bar in Impress. In the past, users had to edit notes in a separate notes view.

We were told very early on that users wanted to be able to do this directly within the slide editing view. This is a very well-known enhancement that we sponsored, which – I think – works very well. In addition, there are many other details, such as scrolling through presentations with the mouse wheel. Previously, you had to keep switching back and forth to the slide overview view to scroll. Now all of this is possible right from within the slide, which simply makes it easier to use and also increases acceptance because users expect it.

I could list many more extensions. We’re not the only ones contributing a great deal to LibreOffice – we see ourselves as part of the community, and we’re happy when the community uses our contributions and when others contribute their own, which we’re of course very happy to use as well. That’s what makes the project so attractive and successful.

Features and improvements in LibreOffice, sponsored by the Austrian Military (this is a slide from a presentation at the LibreOffice Conference 2025)

Have you also developed external extensions?

We’ve developed extensions for internal use, but there are also several publicly available extensions. One of them integrates our own help page, since we provide targeted help within our internal systems.

On a much larger scale, there’s an extension hosted on GitHub that covers military-tactical symbols. It’s available as open source software, so anyone can use it. This is actually an extension that, although it’s still in “release candidate” status, already works well. The extension is, of course, also suitable for collaboration with other armies. Its functionality is unique. To my knowledge, it’s not available anywhere else.

Do you also use the Open Document Format internally?

Yes – one of the advantages of LibreOffice is that the format is ISO-standardised and truly open. You get the best functionality in LibreOffice when you use ODF. We use ODF throughout. It’s clear that our external partners don’t do this to the same extent. This is where LibreOffice benefits from its ability to handle (read and edit) Office Open XML (OOXML) documents as well.

LibreOffice doesn’t have a built-in email client. How did you handle this issue during the migration?

The Austrian Armed Forces protect the Austrian population; to make this possible, we need, for example, systems that function independently of external parties. We have a large number of systems based on open source solutions and many solutions that are platform-independent. This includes the email system.

Therefore, we didn’t have to replace Outlook or Microsoft Exchange.

At the LibreOffice Conference, you emphasised that the migration was never about saving on licensing costs. The migration was driven by other reasons, correct?

The switch to LibreOffice in the Austrian Armed Forces stems from the necessity that we must be able to function even when nothing else is working. In other words, we cannot rely on public infrastructure. We cannot rely on our data being processed in another data center.

Therefore, the top priority in this transition – unlike 20 years ago, when people very often considered switching to a free office suite or Linux in the workplace for cost reasons – was digital sovereignty.

As for the costs: It was clear to us from the start that we would have to invest in the product in order to gain the additional functionality we needed and to improve interoperability.

Would you like to say a few words about the foundation – that is, The Document Foundation?

Why did we choose LibreOffice in the first place – after all, there are alternative products? LibreOffice isn’t the only solution. First, LibreOffice uses ODF, the open and standardised file format. That’s very important. Second, LibreOffice is truly fully open source software – it’s not a product that just has an open source “core.” There’s no risk of having to pay for variable enterprise features.

And the fact that this is the case is very closely tied to the foundation of LibreOffice, namely The Document Foundation. The way this open source project is implemented and anchored through the foundation – that’s an important guarantee and a key factor in its reliability for us.

Another point is that there is an ecosystem. There are several companies that offer the services we need. Using open source doesn’t just mean using free software – for us, it means we need maintenance, support, the ability to further develop the software, addressing security vulnerabilities, and secure software deployment. All of this comes with a very mature software product that is constantly being developed. That was a key factor in our decision.

What advice would you give to others who are also planning to switch to LibreOffice and open source?

First: There’s a vast amount of information available within the community. It’s important to familiarise yourself with the product. How does LibreOffice work? How does Bugzilla work? Where can I find issues that might not be working but are of interest to me? Where can I find roadmaps for new features, release notes, and so on?

Second: It’s absolutely crucial to properly prepare and fund the resources for a project like this. IT managers have gotten used to rolling out new Office versions without much effort.

However, switching from one office suite to another is actually a massive migration project. This should not be underestimated. It’s not just a matter of installing the software; it requires change management, people to provide support, test the software, and work on new features. It requires the support of service providers. All of this must be prepared in advance. And that’s what sets it apart from previous new office suite releases. You’ll need a project team for this – migration isn’t something you can just do on the side. So, you’ll need proper project organisation and agile change management. How can I provide my users with the necessary knowledge based on their needs? What communication channels do I have to keep my users informed and stay in touch with them?

We – the Austrian Armed Forces – have already received many inquiries about the transition, and we have shared our experiences with numerous organisations. We would be delighted to help build a LibreOffice community for government and enterprise organisations in order to accelerate the collaborative development of LibreOffice.

To that end, I invite you to contact us at libreoffice@bmlv.gv.at.

Hi everyone,

Before we begin, let me thank all our donors and sponsors. Many thanks to all of you for the help you’re providing us!

We’ve got new HWE ISOs this month and some really exciting news. As always, please be aware that the features and improvements mentioned in this blog are a work in progress and that this is a preview of what’s to come and what’s planned for the next release of Linux Mint.

HWE ISOs

A new set of HWE ISOs is available for Linux Mint 22.3 with kernel 7.0.

For more information on HWE, or to download these ISOs: https://www.linuxmint.com/hwe.php

Environment Variables

The System Administration tool received a new page dedicated to environment variables.

Variables defined on this page are set system-wide for all user sessions (graphical and/or console).

Kernel Management

Kernel management was removed from the Update Manager and re-implemented within the System Administration tool.

This new implementation supports both Linux Mint and LMDE. It focuses on kernel series rather than individual kernels.

Kernel management is very simple: You decide which series you want to track and how many older kernels you want to keep. You then receive kernel updates for your tracked series in the Update Manager, and older kernels are automatically removed by the system on a weekly basis.

If you need to free up space immediately, cleanups can be triggered manually.

You can also click on the History button to see which kernels were removed and when.

If you install a kernel from an unknown or custom series, the tool will list its series and give you the ability to mark it as tracked.

In the screenshot below, we installed an OEM and a Real Time kernel.

When you track a known series, the tool installs its meta-packages and ensures you receive updates for that series. In the case of a custom series, the tool doesn’t know how to do that and warns you that it is your responsibility to do so.

If a series is not tracked, all of its installed kernels get automatically removed during the next cleanup. Unless… you protect them.

You can click the “View all kernels” button to install, remove, or protect individual kernels.

When a kernel is marked as “protected”, it becomes immune to kernel cleanups and never gets deleted.

Keyboard Layouts and IM

Cinnamon received support for Fcitx5 with full Wayland/X11 parity.

With Fcitx5 selected in the Input Methods settings, Cinnamon no longer launches ibus-daemon, but uses a different internal handler instead. It lets you define a single layout and delegates everything else to Fcitx.

Cinnamon also features a new keyboard layout viewer.

This viewer replaces the gnome-kbd viewer, which was discontinued.

Other improvements

Interacting with the panel when working with fullscreen windows feels much more natural than before. You can click other components of the panel, close the menu, open other applets, etc.

Sponsorships:

Linux Mint is proudly sponsored by:

Gold Sponsors: Silver Sponsors:

Bronze Sponsors:

Donations in June:

A total of $14,761 were raised thanks to the generous contributions of 419 donors:

$580 (7th donation), Natalya S.
$464 (2nd donation), Michael S.
$300 (35th donation), John Mc aka “Land Research Project“
$300 (9th donation), André Inácio
$290, DJ
$250 (5th donation), Benjamin M.
$232, Dr. S. T.
$232, Götz K.
$145, Libre à Quimperlé
$128, Martin B.
$120 (8th donation), Michael P.
$116 (21st donation), Jiří B.
$116 (14th donation), Hans-Georg Thien
$116 (9th donation), Walter K.
$116, Jan K.
$116, Jan S.
$116, Martin D.
$116, OuestWare
$116, Richard L.
$116, Silvia S.
$116, Thomas E.
$116, Wolfgang H.
$100 (8th donation), William C.
$100 (3rd donation), abrames
$100 (3rd donation), Dale K.
$100 (3rd donation), Gilbert B.
$100 (3rd donation), Mark S.
$100, Adam S.
$100, Dan B.
$100, Edward R. K.
$100, Isaac K.
$100, Michael S.
$100, Services Multiples R.
$87 (2nd donation), Florian S.
$81, Benjamin S.
$75, Javier S.
$70 (6th donation), Vincent F.
$70 (3rd donation), ZS
$70, Simon H.
$58 (18th donation), Roland H.
$58 (17th donation), Jyrki A.
$58 (12th donation), Karl H.
$58 (7th donation), Gerald H.
$58 (5th donation), Karl-heinz P.
$58, Alexander H.
$58, Anton R.
$58, Bernd C.
$58, Daniel B.
$58, gilles Delaguette aka “gillou”
$58, Günter A.
$58, John P.
$58, Kai N.
$58, Levente D.
$58, Martin K.
$58, Michael T. B.
$58, Michel O.
$58, Nick V.
$58, Ralf E.
$58, Ralf S.
$58, Rene W.
$58, Rolando
$58, Rupert W.
$58, Ruth S.
$58, Sanny S.
$58, Stefan I.
$58, Thomas B.
$58, William A.
$58, William F.
$58, Yeun H. T.
$52, Jeffery M.
$51, John A.
$50 (21st donation), Mothy
$50 (17th donation), Anthony C. aka “Ciak”
$50 (11th donation), Peter L. aka “Pedro“
$50 (8th donation), Gerard S.
$50 (7th donation), Tim A.
$50 (6th donation), Leonhard R.
$50 (5th donation), Robert L.
$50 (3rd donation), Soeren
$50 (2nd donation), James M.
$50 (2nd donation), Jason E.
$50 (2nd donation), Johnny R. D.
$50 (2nd donation), peter T.
$50 (2nd donation), Timothy J I.
$50, Algie M.
$50, ANDREW M.
$50, Austin R.
$50, Caleb S.
$50, Dustin P.
$50, edward K. aka “edthefair”
$50, Gohér L.
$50, Joshua E.
$50, Lionel L.
$50, Maciej S.
$50, Marco M.
$50, Mark W.
$50, MOHD A. A. H.
$50, Richard A.
$50, Rolando G.
$50, Ruiping L.
$50, Samuel G.
$50, Shay C.
$50, vitalii V.
$50, Vitalox.co.uk
$50, Wayne L.
$50, WILSON N. S.
$50, Øyvind L.
$46, José R. B. U.
$46, Maik S.
$45, James R.
$41, M.J. D.
$40 (10th donation), Orlando O.
$40 (2nd donation), Jonathan L.
$40, Grant L. S.
$40, Joseph D.
$37, siobhan M.
$36, Shawn D.
$35 (3rd donation), Renee M.
$35, achim M.
$35, David B.
$35, Donald B.
$35, Fazekas F.
$35, GARRY J. W.
$35, Helmut E.
$35, P J. C.
$35, Russell R.
$35, Simon H.
$35, Teo S.
$35, Tobias K.
$35, vincent R.
$31 (6th donation), David B.
$31, Johannes W.
$30 (8th donation), Doug S.
$30, David S.
$30, Jan V. D.
$30, MR G. S.
$30, Terence R.
$29 (2nd donation), Askeldaja
$29 (2nd donation), Kerry H.
$29, Andrea P.
$29, Andrew G.
$29, Michael Koch
$29, Mr T. A.
$29, Warren B.
$28 (4th donation), Toon V.
$27, Benjamin B.
$25 (64th donation), Linux Mint Sverige
$25 (19th donation), Donna B.
$25 (17th donation), John N.
$25 (6th donation), Oleksandr N.
$25 (2nd donation), Roger M.
$25, John H.
$25, Ong L. Z.
$25, ROBERT A. B.
$23 (119th donation), Johann J.
$23 (78th donation), Bryan F.
$23 (72nd donation), Peter E.
$23 (39th donation), Stefan W.
$23 (34th donation), Benjamin W. aka “UncleBens”
$23 (32nd donation), Marek S.
$23 (14th donation), Frank W.
$23 (8th donation), Tapani H.
$23 (6th donation), Robert J.
$23 (4th donation), Guillaume P.
$23 (4th donation), Jeff H.
$23 (4th donation), Pedro A.
$23 (3rd donation), Adam B. aka “Neomodus”
$23 (3rd donation), Benjamin L.
$23 (3rd donation), Gehova L.
$23 (3rd donation), Systemutvikler R. S.
$23 (3rd donation), Thomas H.
$23 (2nd donation), Henrik M.
$23 (2nd donation), Ian K.
$23 (2nd donation), Michel S.
$23 (2nd donation), Norbert E.
$23 (2nd donation), Pascal T.
$23 (2nd donation), Peter V. R.
$23 (2nd donation), Z A. Z. A.
$23, aka “Dealer Dahl”
$23, Andreas S.
$23, Anonymous
$23, Dan M.
$23, Frédéric B.
$23, Heinz-Jürgen F.
$23, Helmut M.
$23, Henning G.
$23, Henrik H.
$23, J.P. G.
$23, Jochen H.
$23, johan B. aka “Woody”
$23, Johannes A.
$23, John M. S.
$23, Klaus P.
$23, Marcus B.
$23, Martin E.
$23, martine P.
$23, Michael N.
$23, michael P.
$23, Mr L. W.
$23, Nurbol K.
$23, Paolo R.
$23, Randy Lahey
$23, Riccardo B.
$23, Ronald H.
$23, Sebastian B.
$23, Sonja S.
$23, staffan O.
$23, Thomas B.
$23, Tobias E.
$23, WILFRIED H.
$23, Wolfgang M. S.
$21 (6th donation), James H.
$20 (53rd donation), John D.
$20 (31st donation), Denis D.
$20 (16th donation), Michel S.
$20 (12th donation), Randall W.
$20 (9th donation), Leela A.
$20 (9th donation), Ricardo M.
$20 (7th donation), Michael G.
$20 (5th donation), Gary S.
$20 (5th donation), Nathan B. aka “Diginate “
$20 (3rd donation), Theodore K.
$20 (2nd donation), Dmytro Z.
$20 (2nd donation), Jerome P.
$20 (2nd donation), Richard L. S.
$20 (2nd donation), Stephen B.
$20 (2nd donation), Terrence C.
$20, Aaron A.
$20, any N.
$20, Brian P.
$20, Bryan J.
$20, David S.
$20, Elijah W.
$20, Elizabeth H.
$20, Gervase G.
$20, GLEATON’S
$20, HYUNGU H.
$20, James M.
$20, Jay G.
$20, Jim B.
$20, Martin J.
$20, Michael B.
$20, Paul B.
$20, Randi J. R.
$20, Revd. Barry Keal aka “G4HDU“
$20, Richard J.
$20, RICHMOND D.
$20, Robert H.
$20, Ron H.
$20, Samuel K.
$20, Steve T.
$20, The Best Buy
$20, Thomas F. aka “Tom”
$17 (93rd donation), Andreas S.
$17 (8th donation), Tristan V.
$17 (5th donation), Tomasz S.
$17, Álvaro V.
$17, Michal L.
$15 (9th donation), mitch K.
$15 (4th donation), Snorre L.
$15 (2nd donation), Justin C.
$15, Josephine
$13 (19th donation), Alessandro S.
$12 (56th donation), Francois-R L.
$12 (51st donation), Thomas Rehm
$12 (50th donation), Tugaleres.com
$12 (30th donation), Adian K.
$12 (24th donation), Slobodan Vrkacevic
$12 (22nd donation), Eskild T
$12 (18th donation), Abe Z.
$12 (17th donation), Artem Ignatyev aka “ZaZooBred”
$12 (17th donation), Tomi P.
$12 (12th donation), Intralogistiker
$12 (8th donation), Rainer B.
$12 (7th donation), J M. H. C.
$12 (6th donation), Claudio A.
$12 (6th donation), Stefan B.
$12 (5th donation), Lyuben R.
$12 (5th donation), Olivier R.
$12 (5th donation), ronald H.
$12 (4th donation), Bartomiej T.
$12 (4th donation), Matthias K.
$12 (4th donation), Renaud A.
$12 (3rd donation), Arne A
$12 (3rd donation), Donald B.
$12 (3rd donation), FrankFRL
$12 (3rd donation), Raul Z.
$12 (2nd donation), Brian C.
$12 (2nd donation), Frank F.
$12 (2nd donation), Marc L.
$12 (2nd donation), MorpurgoMedia.nl aka “Morpurgo Media“
$12 (2nd donation), Nektarios T.
$12 (2nd donation), Ricardo O.
$12 (2nd donation), Sebastian M.
$12, –
$12, Antonio A. M.
$12, Antonio S.
$12, Bernhard R.
$12, Bettina B.
$12, Bogdan D.
$12, Christian B.
$12, Christoph A.
$12, Claes C.
$12, David P. B.
$12, Esteve L. G.
$12, Eugen W.
$12, Fidel V.
$12, FLORIAN K.
$12, Giobatta L.
$12, Helmut S.
$12, Henning S.
$12, Igor C.
$12, Jan O.
$12, Jesse D. A. R. D. S. J.
$12, Joe S.
$12, John D.
$12, Kalin S.
$12, Karel J.
$12, Klaus D. N.
$12, Koski M. K. aka “Wintageman“
$12, Lauris S.
$12, Mark C.
$12, Markus B.
$12, martin G.
$12, Michael D.
$12, Neil G.
$12, Noel A.
$12, Ralph A. W.
$12, Renzo M.
$12, Ruben O. K.
$12, Steffen H.
$12, Sven S.
$12, Tamás R. V.
$12, Thomas L.
$12, tj J.
$12, Wolfram S.
$11, Jozef T.
$10 (123rd donation), Thomas C.
$10 (65th donation), Philip Woodward
$10 (43rd donation), Sami Mannila
$10 (19th donation), Thevirtua
$10 (14th donation), Mariusz B.
$10 (9th donation), Korora Solutions
$10 (9th donation), Steven L.
$10 (6th donation), S Russo
$10 (6th donation), Selwyn A.
$10 (5th donation), makeup
$10 (4th donation), Earl R.
$10 (4th donation), notariat
$10 (3rd donation), narghilea
$10 (3rd donation), Richard W.
$10 (2nd donation), Daniel R.
$10 (2nd donation), Jacek B.
$10 (2nd donation), Metehan K.
$10 (2nd donation), Timothy C.
$10 (2nd donation), VPRECA
$10 (2nd donation), William P.
$10, B P.
$10, Brody McDonald
$10, Cesar R. B.
$10, Craig D.
$10, Dean D.
$10, Hector G. G.
$10, Michael S.
$10, NEWT L. H.
$10, Roger L.
$10, Seth A.
$10, Szilvia D.
$10, Timoth O.
$10, Vasilis A.
$10, Victor M. aka “Bull”
$10, William R.
$177 from 45 smaller donations

If you want to help Linux Mint with a donation, please visit https://www.linuxmint.com/donors.php

Patrons:

Linux Mint is proudly supported by 2,353 patrons, for a sum of $5,318 per month.

To become a Linux Mint patron, please visit https://www.patreon.com/linux_mint

Many government departments around the world are moving away from vendor lock-in by tech giants, and switching to free and open source software like LibreOffice. This helps with privacy, security, and digital sovereignty. One such example is the Austrian Military (Bundesheer), which has moved 16,000 PCs from Microsoft Office to LibreOffice. We talked to them, to find out why and how they did it…

When did all of this start? When were the first decisions made?

It began in 2020, with the trend toward running software increasingly in the cloud and less on-premises on devices within companies. At that time, we examined what guarantees existed for running software – specifically Microsoft Office – directly in the workplace without any cloud connection. So the review and preparation began in 2020.

In late 2022 and early 2023, the decision was made to switch to LibreOffice. The goals were to ensure that data never leaves the company and that the office applications can be used without external dependencies.

Who made the decision?

The decision was structured in such a way that our “corporate leadership” – that is, the Federal Ministry of Defence – could decide, based on the information compiled regarding future software development and cloud dependencies, that we would switch to LibreOffice.

It was actually decided by the Federal Minister’s cabinet and the relevant departments – so at the very top.

Did you create a “timeline” at the beginning – something like “Y should happen by X” and so on?

After we received the assignment, we carried out the planning to determine how the transition could take place and what needed to happen. The plan included, from an early stage, that we would guide our users to LibreOffice in a timely manner, partly by installing LibreOffice at the user’s request. That is, we made it available, and the users who wanted it could have it installed.

We saw very high adoption rates – not 100%, but about half.

Half of 16,000?

Yes. And the next step we planned was to make its use mandatory, because it’s crucial not only to announce that something new is coming but also to require its use so that people have to start working with the tool early on. Of course, switching from an Office suite that’s been used in the company for over 30 years to a completely new product – even if it looks similar but behaves differently – requires practice.

That’s why we specifically made the use of LibreOffice mandatory in selected services. And we did this as early as 2023, so that users could get familiar with it well in advance. This gave users time to tailor the transition to their own needs and prepare for it, and we didn’t just flip the switch all at once with a “big bang.” The change was announced over the course of several years.

Finally, in December 2024, the use of LibreOffice became mandatory for internal collaboration. This meant we actually provided several years of preparation time to make this transition as smooth as possible.

(Photo credits: Bundesheer Fotos, CC BY-NC-SA 2.0)

So many people switched to LibreOffice voluntarily from the start, without being forced to. Was there a lot of resistance? Did you customise the user interface?

The 8,000 users mentioned installed the product to see what was coming. That doesn’t mean that all 8,000 of them immediately started using LibreOffice. But it was a good indicator for us to gauge the mood. If 200 people install it, that’s different from when there are so many.

Early on, before we mandated its use, we provided extensive e-learning modules and videos – including what we call “fast tracks” for the individual modules. With these, it was possible to learn the most important changes for Writer, Calc, Impress, and Base within 15 minutes, so users wouldn’t fall into the typical pitfalls. Anyone who invests those 15 minutes will find it much easier to use the software.

We gave users the opportunity to prepare and view these courses and videos on their own at a time of their choosing.

Another important point: We’ve learned that we need to quickly address individual users’ questions – such as those regarding unfamiliar workarounds or missing features – for the benefit of the broader community.

That’s why we specifically looked for suitable communication channels, and we then agreed to publish a so-called “Tip of the Week” about once a week on a very specific, clearly defined topic. And this “Tip of the Week” appears every Monday on the intranet with a current topic. That means anyone who opens their browser on Monday will see the “Tip of the Week.”

It explains topics we covered the previous week. When we release a new version, there’s a “Tip of the Week” featuring the latest features. When we roll out new functions and enhancements – some of which are sponsored by the Austrian Armed Forces – we highlight them in the “Tip of the Week.”

But we also cover usability topics – for example, how to enable the menu bar even when the tabbed interface is selected. How to use presentations across multiple screens, and so on and so forth. We’ve been doing these “Tips of the Week” for two years now, and they’ve been very well received. It’s a great communication tool for us.

Click here for part 2 of the interview

A truly open document format requires free public availability, royalty-free standards, and no usage restrictions.

Organizations like the Open Knowledge Foundation and the European Union use several core rules to guarantee long-term data access, system independence, and freedom from single-vendor control.

Core Openness Criteria

• Public Specification: The complete format rules are published and easy for anyone to access.
• Royalty-Free: Patents or licensing fees cannot block developers from building compatible software.
• No Discrimination: Anyone can use the format for any purpose without needing special permission.
• Independent Control: A transparent, non-profit standards body manages future updates.

Recognized Frameworks

• The Open Definition: Specifies exact legal and technical terms for open works.
• European Interoperability Framework (EIF): Requires governments to use truly open formats for public documents.

Comparison of ODF and OOXML

When evaluated against the strict criteria for open formats, Open Document Format (ODF) and Office Open XML (OOXML) take fundamentally different approaches.

While both are recognized as official ISO standards, ODF fully satisfies the open standard criteria by design, whereas OOXML features structural and legal complexities that often limit true open implementation.

Comparison Table

Key Openness Differences

Public Specification & Transparency

• ODF: Conceived from the beginning to be a modern, clean XML specification. “ODF is the only openly available standard, published fully in a document that is freely available and easy to comprehend”, as noted by GranneBlog: https://blog.granneman.com/2009/02/06/odf-compared-constrasted-with-ooxml/
• OOXML: Designed primarily to map Microsoft Office’s old binary data into XML. It is split into Strict and Transitional variants. “Transitional is everything else: a vast catalogue of compatibility features, deprecated elements, platform-specific behaviours, and references to undocumented quirks of Microsoft Office versions from the 1990s.”, as noted by the TDF Blog: https://blog.documentfoundation.org/blog/2026/06/02/a-standard-in-name-only/

Legal & Intellectual Property Rules

• ODF: Utilizes a standard open-source framework. Anyone can implement ODF in a project without fearing intellectual property or patent litigation.
• OOXML: Relies on the Microsoft Open Specification Promise (OSP): https://en.wikipedia.org/wiki/Microsoft_Open_Specification_Promise. The OSP is a unilateral covenant not to sue, but it only covers developers to the extent that they precisely mirror the specification. Any implementation-defined deviations or edge cases may leave developers legally unprotected.

Technical Discrimination & System Control

• ODF: Avoids hardware-specific dependencies, ensuring that independent applications (like LibreOffice or Apache OpenOffice) can render the data uniformly.
• OOXML: Contains platform-specific elements tied closely to the Windows OS ecosystem. Because Microsoft Office has traditionally produced Transitional OOXML by default, third-party platforms encounter massive conversion obstacles when interpreting legacy binary elements or proprietary formatting definitions embedded within the file structure.

INTERESTING REFERENCE: the Italian definition

The document Linee guida su acquisizione e riuso di software per le pubbliche amministrazioni (Guidelines on the procurement and reuse of software for public administrations), published by AgID in 2021, define an open format in the glossary as follows (translated from Italian):

Open (data) format. This is a public, versioned data format that is comprehensively documented and has no implementation constraints. An open format is one recognised by a standardisation body and maintained collaboratively by several organisations that provide competing implementations, through a transparent process. The format must remain consistent with the declared version.

The guidelines are not an interpretive gloss issued alongside the statute. They are adopted in implementation of articles 68 and 69 of the Codice dell’Amministrazione Digitale, under express delegations contained in the statute itself. They also supersede the earlier AgID circular 63/2013 on the same comparative assessment.

The definition of formato aperto (open format) is therefore not a recommendation that happens to be well drafted. It is the operative legal definition for Italian public administration, and it acquires that force through the statute rather than in spite of it.

Here’s our summary of updates, events and activities in the LibreOffice project in the last four weeks – click the links to learn more…

• We had one update in July: LibreOffice 26.2.5, the fifth maintenance update to the LibreOffice 26.2 branch.

• We also said a big welcome to our new TDF members! Members – more formally known as the “Board of Trustees” – are a crucial part of The Document Foundation, the non-profit entity behind LibreOffice. They are people from across the globe who contribute time, effort and skills, whether on a voluntary or paid basis.

• Then there was another section from the TDF Annual Report 2025, Policy and Digital Sovereignty. This section looks at Germany’s IT Planning Council committing to ODF, the approval of ODF 1.4, and public migrations to LibreOffice.

• On a similar topic, we posted how proprietary formats have become Microsoft’s main tool for lock-in.

• Back to the software itself: we posted the LibreOffice State of the Project (July 2025 – June 2026), based on data from July 1, 2025, to June 30, 2026, extracted from the LibreOffice dashboard and the Matomo repository. This is full of statistics describing the health of the project and the community.

• An additional section from TDF’s Annual Report 2025 was the foundation’s financials and budget.

• Meanwhile, the small team at TDF is expanding, with a job offer for a new Marketing and Communication Professional. Applications are open until the end of August.

• Finally, we wrapped up the month discussing Microsoft’s end-of-life of Office 2021, and how LibreOffice stays yours for a lifetime. And on a similar topic, we looked at why OOXML-based suites handle ODF badly.

Like what we do? Support LibreOffice with a donation – or join our community and help to make LibreOffice even better! Also keep in touch – follow us on Mastodon, Bluesky, Reddit and Facebook.

🚀 Features

• Added button for renaming tags (#1173) by @EmaYYellow in #1173
• Added audio player for media attachments (#1172) by @deprov447 in #1172

🐛 Bug Fixes & Minor Changes

• Format dates with device preferred 12/24-hour clock (#1183) by @arpitagarwal1301 in #1183
• Honored custom tab preference in notifications (#1182) by @arpitagarwal1301 in #1182
• Fixed crash introduced by audio player feature by @spacecowboy in commit

🌐 Translations

• Updated translations from Hosted Weblate (#1174) by @weblate in #1174
• Updated German translation using Weblate in commit
• Updated Serbian translation using Weblate by @eevan78 in commit
• Updated Ukrainian translation using Weblate by @andm18 in #1186

❤️ New Contributors

• @deprov447 made their first contribution in #1172
• @EmaYYellow made their first contribution in #1173
• @arpitagarwal1301 made their first contribution in #1182

On 30 July 2026, the United States Cybersecurity and Infrastructure Security Agency published Open Source Software: Security Principles and Practices, a 31-page guidance document for federal civilian agencies. It is available at no cost and marked TLP:CLEAR, meaning it may be shared without restriction.

The document is addressed to US federal agencies, and it fulfils obligations under two executive orders on federal cybersecurity. It covers four areas: using open source solutions, contributing to open source projects, producing open source software, and evaluating open source artificial intelligence models. The observations below concern the first three.

Its analytical content is not jurisdiction-specific, and public administrations elsewhere — including in Europe — will find that it articulates, in the vocabulary of risk management, several positions that the open source community has been arguing for two decades.

What the guidance actually says

The central claim is more precise than the headlines suggest. CISA does not assert that open source software is more secure than proprietary software. It states that OSS is “no more or less risky than other software,” and locates the difference elsewhere: with open source, an organisation can assess code quality and security directly, rather than relying solely on vendor assurances.

This is a claim about verifiability, not about defect rates. It is also the more defensible claim, and the more consequential one for procurement. An agency evaluating proprietary software is evaluating a vendor’s statement about its own product. An agency evaluating open source software is evaluating the product.

The guidance draws the corollary explicitly. Among the benefits it lists for federal agencies is reduced vendor lock-in: open standards and modifiable code, CISA writes, protect agencies from “proprietary dependency traps.” A national cybersecurity authority has placed lock-in inside a security document rather than a competition-policy one. That is a meaningful shift in where this argument is permitted to live.

The C4 Framework

The most practically useful part of the guidance is Appendix A, which sets out the C4 Framework for assessing whether an open source project is trustworthy. Its premise is that, because contributors may be pseudonymous and are bound by no delivery obligation, trustworthiness cannot be assessed from who produced the software. It must be assessed from how the software was produced — which open source development makes visible in a way that closed development does not.

C4 groups the evidence into four categories:

• Codebase — commit recency, known vulnerabilities, dependency currency.
• Community — number of maintainers, institutional structure, whether the project sits within a foundation.
• Conduct — whether there is a vulnerability disclosure policy, whether code review is required, whether maintainers merge their own commits, the licence, the code of conduct.
• Configuration — whether defaults are secure, and what hardening the software supports.

The framework is applied in five steps: identify measurable criteria, determine risk tolerance and weight the criteria, collect observations (with automated tooling where available), evaluate against each criterion, and compare the result to the tolerance.

We would encourage public administrations to apply this framework to LibreOffice. Every category can be answered from public evidence: a continuous commit history since 2010, a published security policy and disclosure process, mandatory peer review, an OSI-approved licence, a documented code of conduct, and a governance structure — The Document Foundation, a German Stiftung with an elected Board of Directors — that is a matter of public record rather than of assertion.

We would encourage administrations to apply the same framework to every candidate solution, including proprietary ones, and to note which questions can be answered and which cannot.

Contributing, and the support question

The guidance also addresses a question that public administrations regularly raise about open source adoption: who is responsible for fixes. CISA’s answer is that no single entity is obliged to provide them, and that agencies should therefore plan accordingly — assigning internal staff, contracting third parties, or both — while following two principles in dealing with upstream projects: collaborate rather than demand, and push fixes upstream.

This is a fair description of how the LibreOffice ecosystem works. Support, long-term maintenance, and custom development are provided by certified developers and certified migration professionals, whose contributions return to the shared codebase and benefit every other deployment. The guidance is right that this requires organisations to plan for it. It is also right that the resulting improvements are shared rather than captured.

CISA further notes that where a project becomes unmaintained, an organisation may as a last resort take over a fork. This option has no equivalent in proprietary software, where end of support arrives on the supplier’s schedule and offers no remedy at all.

A note on scope

The document does not name any product. CISA states explicitly that it does not endorse commercial entities, products, or services, and nothing in the guidance should be read as an assessment of any particular software. What it provides is a set of criteria. The observation that LibreOffice satisfies them is ours, and rests on evidence that anyone may check.

Open Source Software: Security Principles and Practices is available from CISA: https://www.cisa.gov/resources-tools/resources/open-source-software-security-principles-and-practices

CISA’s announcement: https://www.cisa.gov/news-events/news/cisa-guide-helps-federal-agencies-securely-and-effectively-use-open-source-software

LibreOffice extensions are optional, third-party addons for the suite, that add extra functionality. Bora Yarkın has been working on a new extension for LibreOffice Impress, so let’s hear from him about it…

Tell us about it!

The extension lets you control a LibreOffice Impress presentation from your phone or any other device with a modern web browser.

When you start the remote, LibreOffice displays a QR code. Scan it with your phone and the presentation starts from the first slide. The phone interface then shows the current slide, presenter notes, elapsed time and navigation controls.

I tried to make the process as simple as possible: no separate mobile application and no manual pairing codes.

The remote can be opened from the Slide Show menu in LibreOffice’s top application menu bar—the menu alongside File, Edit, View and the other main menus.

This should not be confused with the Slide Show tab inside LibreOffice’s Tabbed user interface. LibreOffice’s UNO extension API does not currently let me add commands to that built-in tab. When using the Tabbed interface, the remote commands are therefore available under the Extensions tab instead.

The extension currently provides several connection modes:

• Local network: The phone connects directly to the computer running LibreOffice through its local IPv4 address. This is the main mode and the one I have tested most thoroughly.
• Direct IPv6: Works similarly, but uses an IPv6 connection. It is still marked experimental because my home internet connection is currently the only IPv6 network I can properly test with.
• Relay server: A small Python service that can be hosted on Linux or Windows. It is useful when the phone and computer are on different networks or when direct connections are blocked by carrier-grade NAT, firewalls or other network restrictions. It also supports multiple connections, so an organisation can host one relay server on its own infrastructure.
• LocalTunnel: An experimental fallback that creates an outbound connection through the LocalTunnel service. I consider this a last-resort option when the other connection methods are unavailable.

The compatible relay-server package is bundled with the extension. It can be downloaded or extracted directly from the Remote Settings window by selecting “Get Relay Server”. The package includes the required documentation and setup instructions.

To install the extension, download the .oxt file from the LibreOffice Extensions website or GitHub and open it with LibreOffice. It can also be installed manually through Tools > Extensions. After installation, restart LibreOffice if requested.

The extension includes translations for more than 100 languages and automatically follows LibreOffice’s interface language. English and Turkish are the two languages I have personally checked. Many of the other translations were created with ChatGPT, so I cannot guarantee their quality and would be very grateful for corrections from native speakers.

Why did you create it, and what was the process like?

The original inspiration came from Apple Keynote.

When Keynote is installed on both a Mac and an iPhone, the phone can be used to control the presentation while also displaying presenter notes. That feature completely changed the way I give presentations.

Over time, my slides became more professional and less text-heavy. Instead of putting everything on the slide, I started using the presenter notes almost like a teleprompter, with the text I actually planned to say. This helped move the audience’s attention away from reading the screen and back towards me.

That workflow worked perfectly for a long time, but I never really liked Keynote itself. I could not get used to its interface, and Apple’s decision to introduce paid features was the final reason for me to start looking for an alternative.

There were already several possible solutions, but none of them really worked for me.

LibreOffice previously had its own Impress Remote mobile application, but it has not been maintained for a long time and is no longer practical on many current devices and systems.

Browser-based presentation platforms can offer remote-control features, but I did not want my main presentation workflow to depend on an online service. They also do not offer the same flexibility as a full desktop office suite.

Microsoft Office was another possible option, but I am not a fan of Microsoft’s current direction, particularly the increasing integration of Copilot throughout its products.

OnlyOffice Desktop Editors is a good alternative and I used it for a while, but I encountered several bugs and eventually needed features it did not provide.

That brought me to LibreOffice, which I now find more useful and capable than the other office suites I tried. The only thing missing was the remote-presenter experience I had become dependent on with Keynote.

So I decided to build it myself.

I work mainly in IT and I am familiar with programming, but I would not describe myself as an advanced software developer. Before starting this project, I knew almost nothing about LibreOffice’s UNO API.

I began with ChatGPT. I defined the architecture, features, user interface and constraints myself—including requirements such as localisation being mandatory—and used AI to help me understand UNO and implement the code. The result turned out much better than I expected.

The extension was originally only a personal project. The first version was very basic; the web interface did not even have a back button. I had no intention of publishing it. Once it started working reliably, however, I realised that other LibreOffice users might want the same experience. I decided to take the project more seriously and turn it into a complete extension rather than something that only worked on my own computer.

That meant adding a more polished phone interface, connection settings, QR-code generation, IPv6 support, the relay server, LocalTunnel support, localisation, documentation, error handling and packaging.

Publishing it on the LibreOffice Extensions website was much easier than I expected. I created an account, created the project page, entered the information, uploaded the package and submitted it. After roughly a day of review, the extension was available publicly.

How can people help with testing and further development?

The source code and issue tracker are available on GitHub. The repository includes templates for bug reports, feature requests and pull requests.

My main development and testing setup is macOS with an iPhone. I have also tested the extension on Windows and Linux, but those tests were performed under less-than-ideal conditions, including virtual machines, Remote Desktop sessions and a headless Windows Server installation.

Because of that, testing on real Windows and Linux desktop systems would be especially useful.

The areas where community help would be most valuable are:

• Testing different LibreOffice versions
• Testing Windows, Linux and different macOS versions
• Testing Android devices and different mobile browsers
• Testing IPv6 connections between genuinely separate networks
• Testing the relay server in real-world and organisational environments
• Testing unusual firewall, VPN, NAT and carrier network configurations
• Reviewing and correcting translations
• Improving the documentation
• Reporting bugs and suggesting features
• Contributing fixes through pull requests

The local IPv4 mode has been tested extensively across different local networks, internet providers and VPN configurations. The IPv6, relay-server and LocalTunnel modes need broader community testing before I would consider them fully proven.

When reporting a connection problem, including the operating system, LibreOffice version, browser, phone type, selected connection mode and basic network configuration would help enormously.

The project started because I wanted this functionality for myself. Now I would like to make it reliable enough that other LibreOffice users and organisations can confidently use it for their own presentations.

Today we’re talking to Karl-Heinz Gruner, who has been supporting the LibreOffice community at events in Germany and recently became a member of The Document Foundation, the non-profit behind the suite:

Tell us a bit about yourself!

I live in Middle Franconia, near Nuremberg. In my spare time, I enjoy riding my motorbike, even though I haven’t been getting out on rides as much as I’d like at the moment. I find hiking in the region a great way to unwind. Being active in the fresh air brings me peace and relaxation, whilst also giving me space to come up with new ideas.

Professionally, I have worked extensively with office applications from various manufacturers – both from a user’s perspective and in the context of supporting other users. A particular focus of my involvement is my work with the local Linux User Group. There, I focus on open-source software solutions, sharing experiences and imparting practical knowledge.

For what are you using LibreOffice right now?

My personal curiosity and interest in practical IT solutions prompted me to carry out a fundamental modernisation of an association’s accounting system.

The starting point was an outdated spreadsheet program that was used to create entries, reports and statements. Initially, the idea was to migrate this solution to LibreOffice Calc, making it clearer and more future-proof.

However, during the analysis, it became clear that simply revising the existing spreadsheets would not be sufficient. Consequently, the decision was made to switch to a more up-to-date system with more comprehensive functions within the existing IT environment. A key outcome of this process is the use of a comprehensive application for administration and communication.

In addition to this, I developed a training programme for the adult education centre to focus on a specific area: the professional design of documents using forms and mail merges.

What do you plan to do in the future?

Looking to the future, I believe it is particularly important to convey information through a variety of channels. Modern software offers a wide range of functions, which many users initially find difficult to get to grips with.

It is therefore crucial to break down reservations and barriers to access. Potential users should be provided with clear information, given practical support and encouraged to try things out for themselves. Software and digital services must remain not only functional but also appealing.

For me, this means continuing to share knowledge through talks and training sessions, explaining practical applications using concrete examples, and convincing users of the benefits of open solutions.

My guiding principle is: inform, provide practical support, and spark interest.

Many thanks to Karl-Heinz for his help! All contributors to LibreOffice are welcome to become members of TDF

With July being the final month for the 1st round of the 2026 Bug Accelerator Program, we focused on a rapidly landing quality of life fixes and clearing the way for the next round of BAP work in the next 3 months. With this round of changes and fixes, Inkscape 1.5 is now in a much stronger position, with over 60% completion of the current milestones.

Mike and Sean worked through a wide range of regressions and usability problems, including both issues new to 1.5, and old issues that have existed in Inkscape for years. Some of the new changes include document tabs scrolling, text and font fixes, grid fixes (a much improved UX), startup screen improvements, various shortcut fixes, improved SVG font handling, extension management fixes, and so much more.

Frankly, with so many changes, it's hard to fully quantify just how much work has been landed this month (and really, this cycle). Many thanks go to the BAP devs and the Inkscape veterans who've been providing guidance, assistance and also fixing issues alongside the BAP devs.

We still have more to go, so testing, feedback, and even suggestions are much appreciated.

Michael Terry

• Total time tracked: 52h 8m

• In progress and open items (9h 11m):

  • #6238 1.5-dev: The preferences dialog's size is not restored when reopened - (20m)
  • #5142 Text tool's font dropdown not loading fonts until mouse hover - (42m)
  • #6253 Congested and unusable font collection labels in the new Font and Text dialog - (1h 1m)
  • #631 1.5-dev: Extension Manager: Cannot install extensions nor view details on "Orphan Extensions" - (1h 10m)
  • #6279 If nothing is selected Esc should escape the selected group (not layer!) - (1h 52m)
  • #6168 Set Inverse Mask cause the masking object to lose its path effects - (3h 14m)
  • #6334 Change image in Object Properties doesn't use native file dialog - (14m)
  • #5765 Recent files list deleted files - (38m)

• Merged 17 merge requests (2h 54m):

  • !8046 Use white for default specular color - (5m)
  • !8074 Transform page border paths for coord system - (15m)
  • !8080 Correctly return when actions do not require parameters - (0m)
  • !8081 Fix grammar of action names - (4m)
  • !8082 Address clangtidy issues - (4m)
  • !8072 Don't warn on encountering non-file URIs - (3m)
  • !8071 Fix template and template category i18n on startup screen - (10m)
  • !8070 Reword paste submenu in Edit and right-click menus - (10m)
  • !8054 Base show grids value on visibility status of grids alone - (35m)
  • !8067 Restore grid alpha on load - (1m)
  • !8063 Don't display actions which require unprovided params in shortcuts list - (16m)
  • !8064 Default to not converting `ScalarUnit` limits - (7m)
  • !8052 Add frame to startup screen close button - (22m)
  • !8051 Remove references to saving window position - (6m)
  • !8017 Remove CanvasItemDrawing from Drawing object completely - (25m)
  • !7925 Add effect runner which accepts Variant dictionary arguments - (9m)
  • !7989 Fix version information when updating a document - (2m)

• Fixed 29 issues (32h 35m):

  • #6330 SVG Font Editor does not correctly layout glyphs where the EM-size is not 1000 - (51m)
  • #5832 Converting a solid color to a gradient leaves the fill-opacity attribute unexposed - (57m)
  • #6108 Layers & Objects dialog: Keyboard navigation can no longer access lock, visibility - (3h 7m)
  • #6115 1.4.3 "Open SVG Image as separate document" doesn't work if the SVG file dropped into Inkscape doesn't have a file extension - (24m)
  • #5203 Crash on attempting to duplicate layer - (1h 38m)
  • #6150 Mouse cannot select a zero-length path with Selector Tool or with Node Tool - (1h 13m)
  • #6240 1.5-dev: Document tabs can't be scrolled and don't overflow - (5h 40m)
  • #6320 rect rx percent value misinterpreted when image is present - (1h 17m)
  • #6291 Deletion triggers unexpected Layer change with XML dialog open - (49m)
  • #6260 Layer name (label) lost when converting to group - (11m)
  • #6309 1.5-dev: HSL values saved without "%", causing colours to be displayed as black in 1.4 and other applications - (1h 36m)
  • #6271 Inkscape master: Unchecking "Hide dialogs from taskbar" doesn't work - (1h 13m)
  • #5608 Inkscape master: Panel and document tabs don't apply theme tab styles - (8m)
  • #5613 INX multiline fields not resizing in Inkscape 1.5-dev - (2m)
  • #6008 Filter Primitives Drag and Drop broken - (53m)
  • #4895 New text dialog - Filtering does not work for custom collections - (36m)
  • #6224 Font size units in the new Font and Text dialog can't be set - (1h 30m)
  • #5658 Bezier Tool: Spiro mode preview broken - (1h 11m)
  • #4906 Ctrl+scroll zoom function conflict with node tool grow selection - (4m)
  • #6102 Text alignment is not persistent for new text objects - (2h 35m)
  • #4668 CLI option --export-margin stopped working - (2h 52m)
  • #6066 Embedded Scripts not shown in Document Properties on load - (24m)
  • #5319 Image elements in inx files are rendered too small in master - (1h 13m)
  • #5580 Inkscape (master): menus fail to scroll when submenus are open - (24m)
  • #6227 "Object Properties - URL" changes on the fly are not commited - (14m)
  • #5603 main window "not responding" while "manage extensions" is open - (10m)
  • #5605 Inkscape master: cannot cycle through tabs after panel tabs improvements MR - (4m)
  • #6018 Layers panel doesn't display iconography - (9m)
  • #628 Extension Manager needs to decouple available extension polling - (1h 10m)

• Other development activity (25m):

  • Additional development work.

• Other project tasks (7h 3m):

  • Triage, testing, project discussions and chats, meetings, coordination, and related meta work.

Seán de Búrca

• Total time tracked: 55h 5m

• In progress and open items (9h 40m):

  • !8083 Allow exiting a group with Ctrl+Escape or Escape-with-no-selection - (15m)
  • !8085 Let font category pill boxes flow across multiple lines - (10m)
  • #6339 Nodes do not snap to page borders with y axis up - (25m)
  • #4321 No hotkey hints in the Node Management Tool - (10m)
  • #6283 Converting contour to path changes visual image - (35m)
  • #6292 PDF form imported has all radio buttons selected (but not in the pdf) - (1h 35m) (Investigation of root cause and poppler APIs)
  • #6200 Undo/Redo gets thrown off when removing Rotate Copies LPE - (20m)
  • #6244 Locked status makes clones uneditable too - (2h 10m)
  • #6145 1.5-dev: About Screen crashes on 6th entry - (4h)

• Merged 24 merge requests (10h 15m):

  • !8084 Fix rendering of svg fonts with non-default em widths - (10m)
  • !8079 Fix opening no-extension SVG files as separate documents - (10m)
  • !8078 When changing to a gradient or similar, drop fill/stroke opacity - (15m)
  • !8075 Fix keyboard focus in the Layer & Objects dialog - (45m)
  • !8073 Fix sorting for parent/child nodes - (15m)
  • !8056 Allow selecting a zero-length path - (15m)
  • !8061 Add dropdown menu and left/right buttons for desktop tabs - (1h 15m)
  • !8066 Fix incorrect selection after deleting object with XML Editor open - (15m)
  • !8059 Make "Dialogs are hidden in taskbar" pref only visible in X11 - (40m)
  • !8055 Fix drag and drop on filter effects dialog - (15m)
  • !8057 When clearing the font collection filter, update the font list - (15m)
  • !8050 Fix scrolling on document tabs not actually switching document - (5m)
  • !8011 Add a combined font size-and-unit widget - (1h 10m)
  • !8019 Avoid some node scroll actions conflicting with Zoom - (35m)
  • !8004 Add gap to some pen and pencil points - (30m)
  • !8002 Allow scrolling document tabs with scroll wheel - (5m)
  • !8031 Support --export-margin CLI arg again - (30m)
  • !8029 Show an error when a File->Open Recent file can't be loaded - (5m)
  • !8023 Stop text alignment from resetting as you create a text element - (25m)
  • !8030 When the document is replaced, update the list of scripts - (20m)
  • !8014 Make document and dialog tabs themable by gtk themes - (20m)
  • !8032 Fix size of <image> elements in extensions - (10m)
  • !6148 Add Group Translucency indicator and display opacity override cleanup - (55m)
  • !7999 Allow cycling through panel tabs with mouse scroll again - (35m)

• Fixed 21 issues (28h 5m):

  • #6285 Snapping to page borders with y axis up is broken - (1h 10m)
  • #6306 Blend mode dropdown in the Fill and Stroke dialog requires scrolling - (25m)
  • #6328 clangtidy CI job consistently fails on forks - (55m)
  • #5018 Tooltips for selector tool grammatically incorrect because of 'dual use' of strings - (20m)
  • #6327 Incorrectly filtering out actions with no required parameter - (10m)
  • #6286 Color selector names are being rendered incorrectly - (20m)
  • #6296 PDF Generation Warns on Hyperlink Creation in Inkscape 1.4 - (1h 5m)
  • #6246 Label for "Edit | Paste…" submenu should not end with an ellipsis (…) - (40m)
  • #5760 Inkscape master: Template names and categories do not have translations applied - (1h 10m)
  • #664 View->Page Grid checkbox unchecked with grid displayed and vice versa - (2h 50m)
  • #3297 Warnings opening Keyboard shortcuts page, and minor text suggestions - (2h 20m)
  • #6162 Ctrl+Drag for constrained translation selects instead of dragging - (3h 55m)
  • #6324 1.5-dev: Grid alpha value is not restored - (15m)
  • #6287 Scale > Width regression with 1.5-dev - (2h 25m)
  • #632 Extensions Manager crashes in Inkscape 1.5-dev - (30m)
  • #5659 LPE offset orange dot became white diamond again - (15m)
  • #6212 [Dialog: Welcome] x button undiscoverable in dark mode - (2h 10m)
  • #6270 1.5-dev: Remove/Disable the option to save window positions from preferences - (35m)
  • #6137 1.5-dev: Specular filter with no explicit color results in invisible object - (4h 35m) (Investigation of underlying cause, incl. bisect)
  • #6174 Undoing spin button changes is tedious - (1h 20m)
  • #5828 Selecting mutlitple layers with SHIFT key doesn't work - (40m)

• Other project tasks (7h 5m):

  • Bug Accelerator and project meetings - 6h 35m

  • Build environment setup and maintenance - 30m

Roland Taylor

• Total time tracked: 65h 2m

• Closed/resolved/invalidated 33 issues (2h 45m):

• Moved/migrated 57 issues (4h 31m):

• Confirmed/tested/reproduced 20 issues (3h 13m):

• Reported/created 12 new issues (1h 22m):

• Identified Feature/UX requests (6 issues) (15m):

• 24 issues marked as "Needs info/needs reproducibility"/recorded for follow-up (1h 24m):

• Linked/closed 9 duplicates (20m):

• Other issue tasks (review, labelling, triage, prioritisation, research, coordination) (13h 33m):

• Non-issue tasks (37h 39m):

  • Meetings & meeting prep - 2h 50m

  • Milestone review & follow-up - 8h 11m

  • MR follow-up/testing/building - 1h 48m

  • Admin duties (spreadsheet management, correspondence, managing assignments, reporting, and other administrative tasks) - 24h 50m

Since the release of GIMP 3.2.4, we’ve been hard at work behind the scenes. We’ve been making fixes that will be included in the upcoming 3.2.6 stable release and adding tons of new features for the first 3.4 development version.

In addition, we’ve been mentoring our four Google Summer of Code (GSoC) students as they’ve been working on their projects. Since we just completed their midpoint evaluation, we wanted to share their progress with you all!

In alphabetical order:

Akascape⁠

Project Description

Akascape started off their early work for GSoC by creating a new Vibrance filter in GEGL. This filter combines the existing Hue-Chroma and Saturation filters to more selectively adjust the less saturated sections of an image without increasing others. It was released in GEGL 0.4.68, so you can use it right now in GIMP!

Their main focus has been on improving the user experience with the Keyboard Shortcuts dialog. They plan to both improve usability while also adding new features.

Akascape’s in-progress work already includes several big improvements such as a category list to quickly jump to relevant shortcuts, the ability to import and export shortcut “profiles”, and efforts to make the dialog more friendly for a future GTK4 port.

In addition, Akascape did some early work on adding more adjustment layers to our PSD import plug-in, building off in-progress work by several contributors. His work would allow for importing Vibrance, Black & White, Photo Filter, and Exposure PSD adjustment layers.

Blezecon⁠

Project Description

Blezecon has taken on the task of building the online infrastructure for a GIMP Extensions platform. Originally planned as part of GIMP 3.0, the Extensions platform would allow users to download third-party themes, brushes, plug-ins, and more via a package manager directly in GIMP. The local infrastructure has been in place for several years - this GSoC project is about developing the online submission process.

Blezecon has been working in the Extension repository and making great progress. His initial work involved cleaning up and correcting issues with the initial YAML script.

He then created a comment-based approval system in the repo. This will allow community moderators to easily inspect and approve new extensions through the same interface they use for responding to issue reports and review merge requests. Blezecon next developed a scheduler script that will monitor pending extensions, and once they have received the required approvals, automatically merge them into the Extensions repository for user access.

While infrastructure work is often not as visible to end users, Blezecon’s GSoC project is an essential effort to getting the Extensions repository up and running for future releases of GIMP!

v4vansh⁠

Project Description

v4vansh did some early bugfixes and improvements in GIMP beforehand. He fixed a problem where the thumbnail wouldn’t update after changing image modes, and he corrected missing information in our manual page generation.

Since the start of GSoC, he has been focused on improving text handling in GIMP. His current big project is grouping fonts by family in the text widgets. In addition to better organization (especially with the infamous Noto fonts which have hundres of variants), this patch significantly reduces lag on systems with large numbers of fonts, as v4vansh’s mentor Liam can attest. This feature is in final testing, and we hope it will be merged into the main codebase soon!

v4vansh has also begun experimenting with adding support for OpenType variable fonts. This would allow for much more sophisticated font and text work in GIMP. The initial work involves exploring both the functionality and the user interface to interact with it, and both will develop further as he continues to work with OpenType fonts.

Waris Maqbool⁠

Project Description

Before GSoC began, Waris contributed some early work to GIMP. He updated our OpenEXR import code to load YUV images in color instead of in grayscale. The main focus of his project though has been with GEGL, our color processing engine.

His first project was implementing a GEGL version of the Sharpen filter. Sharpen is a simpler version of the Unsharpen Mask filter, a popular method of correcting blurry images. It was unfortunately removed from GIMP 3.0 due to it not being maintained and only working on 8 bit images. Waris has created a GEGL filter of Sharpen by doing comparisons with the 2.10 version. The recreated Sharpen filter will be non-destructive and will have an on-canvas preview, both improvements over the original.

You can see the in-progress merge request for comparison. We’re doing some final reviews for optimization, but we expect it to be ready for a future release of GEGL and GIMP.

Waris has also begun working on a new Inner Glow filter for our PSD support improvement project. While GEGL already has an inner glow feature, it was not designed to be compatible with how it looks in Photoshop. As part of his work, he is also creating a generic curve editing widget to use for editing the PSD Inner Glow’s settings.

We unfortunately had more great GSoC applicants than we were awarded available spaces. One student in particular continued contributing, so we’d like to highlight their work as well.

Harsh Verma⁠

Harsh has been focusing on several different areas of GIMP. His initial proposal involved improving our unit testing suite. He is currently working to implement automated UI testing for GIMP. This is a challenging task, as interacting with the UI varies across platforms. He’s already developed several tests that work on Wayland, which you can see at his in-progress merge request.

He’s also improved our contributor infrastructure that integrating CI-Fairy into our pipeline. This feature checks to make sure contributor commits follow the proper format before merging, which makes our commit history easier to read and understand.

Harsh has also been working on more user-visible changes. He recently took on a user request to add more version information to our About dialog. This follows standard practice with other software, and makes it easier for users to find information that helps us troubleshoot problems. In addition, there’s a handy Copy feature to easily grab the information for sharing. The code and UI have gone through several revisions based on developer and designer feedback, and it will likely be merged soon!

We’ve very proud of our student’s contributions so far, both in code and in community! We’re looking forward to you all getting the chance to try out their work in future development releases of GIMP, which we hope to have more information to share soon.

GIMP is Free and Libre Open Source Software, but none of it is possible without the people who create with and contribute to it. Our project maintainer Jehan wanted to interview the volunteers who make GIMP what it is, and share their stories so you can learn more about the awesome people behind GIMP!

Early interviews from co-maintainer Michael Natterer and Michael Schumacher were published shortly after the first Wilber Week. The remaining interviews from this event, about Simon Budig and Øyvind Kolås were published years later as a revival of the series. While these interviews are a bit old and reference outdated versions and features of GIMP, we believe they still have value and show the evolution of our community.

This next interview is the first one recorded at the 2017 Libre Graphics Meeting in Rio de Janeiro, Brazil. The subject is Nara Oliveira, co-founder of Estudio Gunga. She is a Brazilian artist and advocate who uses free software exclusively to develop professional works in many fields, including design, illustration, and animation.

This interview took place over April 21 - 23, 2017. In addition to Jehan and Nara, Simon Budig, and Aryeom Han were also involved and asked questions.

Jehan: Hello Nara. Can you introduce yourself to the people?

Nara: My name is Nara Oliveira. I am a Brazilian designer. I am from Brasília, the capital. The city name is Taguatinga. I study design and today I work with free software. I have my own company with some partners and we work in audio, video, design, and animation.

Jehan: What is the name of your company?

Nara: Gunga. Gunga is an instrument from Capoeira. We have the berimbau with the “calabash”, I think – it’s an instrument from Capoeira.

Jehan: Okay. From what we understood, you mainly use free software

Nara: Yes.

Jehan: Mainly, or only?

Nara: Only.

Jehan: And which ones in particular?

Nara: I use GIMP, Inkscape, MyPaint, sometimes Krita – I’ve tried it – Scribus, FontForge, FontMatrix, and others like everybody uses.

Jehan: Do you use Linux?

Nara: Yes, Arch Linux.

Jehan: So full free software from start to end! Okay, and why do you do this?

Nara: When I heard about free software and Linux, I was working in a cultural space. I was working with theater and with drawing, and we already have that culture of sharing things and sharing knowledge. So when I met these guys in free software, they told me about what GNU and Linux were and the philosophy – and when I heard about it I fell in love with it. Because I already think that way, and so free software is applying what I think is right onto software and onto technology. So for me it just makes sense.

So I started to use this software. In the beginning it was difficult to make the transition, but with some time I got into it.

Jehan: So you made a transition from proprietary software?

Nara: Yes, from proprietary software to Linux.

Farid: When was this?

Nara: When? Ah, let me count…

[group laughter]

I was not finished studying then, so like around 2006 or 2007 I started. I really started to use Linux and everything for working in 2008, for everything.

Jehan: So you studied design in university?

Nara: Yes, in university.

Jehan: With proprietary software?

Nara: Yes, with proprietary software only. But my university was not so focused on software. In five years of studying, we only had one class about software. And as the class went on, everyone already knows how to use it! So it’s like a class that has to be on the curriculum, but it’s not like you have to use – it’s more like conceptual.

Simon: Something I do a lot is that - I’m a software developer mainly, so I do a lot of my own tool development. Like I have a specific problem and I know there is an algorithm in my mind that I know would solve the problem (or might solve the problem), so I start implementing my own tools for very specific, very weird tasks, because I can’t do it with GIMP.

Nara: I would like to do that!

Simon: So this is what I wanted to ask – do you have programming experience? Do you have an idea of what it means to develop software?

Nara: No, but I think I have an idea – but I do not develop programs. I’ve studied a little, but it’s not like I can do something. I can see the code lines and know more or less what’s happening, but I can’t write lines by myself.

Jehan: You’ve told me that sometimes you will see some scripts and guess what it can be, and change the numbers…

Nara: Yeah, but more in insights and not in the programming itself.

Jehan: Since we’re doing this interview for gimp.org, what can you tell us about GIMP? How do you like it? How do you hate it? Tell us everything!

Nara: [Laughing] The first thing is, I like GIMP. I use it a lot. My work and style is more vector, but I use GIMP a lot and I like it.

When I made the transition to free software, until today one thing I didn’t like is that you don’t see the effects. You have do something, turn back, “Oh no!” - I have to change two, three points here, then I have to undo and do it again and come back. For me, it’s one of the things that makes the work not fluid.

I’m so happy to see GEGL on-canvas effects.

[Editor’s note: This feature was already implemented in the development version of GIMP 2.10, officially released about a year after this interview.]

Jehan: So, some other comments on GIMP?

Nara: Yeah, I really like it but, for example, I have some problems with my tablet. When I bought my first tablet, it simply didn’t work on GIMP. And I think it’s because of that, I use MyPaint. Because I have to work, and I have to work right now and the pressure doesn’t work, so what can I do with my tablet – so I found MyPaint, and I started to work with MyPaint, and it’s because of that I use it. Not because I think it’s more powerful than GIMP – it’s just because of that. At the time I liked it, and today I still use it.

[Editor’s note: GIMP 3.0 improved many issues with tablet support that were mentioned here.]

Jehan: So MyPaint is your main software?

Nara: For drawing, yeah. Because I am a designer, but I’m an illustrator too. So for illustration I use MyPaint, just for that. For small drawings, I use vectors in Inkscape, and so on.

I use GIMP more for photos, for editing, composing, correcting photos.

Jehan: Yesterday when we spoke, you had this nice example of a job you did with Scribus. Like your first job with free software, I think?

Nara: No, my first book.

Jehan: Ah, your first book, not your first job with free software. Could you tell it again, now that we’re recording?

Nara: I was called on to make a big book, like three hundred pages. There was little time to do it, like three, two weeks. I am from Brasília, and they said you have to do it here with us to get it quicker. I traveled to Bahia to do it, and when I arrived there, there were two other designers. It was funny because I worked in Scribus, one worked in Corel Draw, and the other one in InDesign. So you had three designers, three different software.

Jehan: And three different operating systems.

Nara: Yeah, and three different operating systems, and we had to do one book, the same book!

So we met each other and said “Okay, let’s do it!”. We separated the book into pages, so I would do the first one to 100, the other designer would do 101 to 200, and so on. And we together figured out how the design of the book would be, and the rules to make each part feel like the same book.

So we started, and just like that, I finished first! I was worried, because I had not used Linux for too long, and if there was something wrong in the software or in the distribution, I would not know how to fix it. One of the designers had Mac and the other had Windows and I was so worried.

But it went well and I finished first – and it was very encouraging for me. It’s just a tool you know? I can do it, he can do it, she can do it – everyone can make it, so I was very happy. Because in the beginning I was worried about everything going wrong, and that there would be problems when I saved the PDF and printed it, but it was all okay.

The book was about experiences with, we call it here “apprentice to Griô”. It’s from the French language, because it came from Africa but a country that speaks French.

It’s like an old master who teaches the people around them, the community, something – knowledge about herbs, which can be medicinal herbs, or teaches about techniques about how to construct instruments, or make music, or dancing – like masters of Brazil, of all Brazil. So it’s because of that it’s a big book!

Years later, in the north of Brazil, when the waters came and filled the houses in the city – a flood. I was seeing that on the TV there was an old lady with her flooded house beside her, everything destroyed. And she had that book in her hand. She was crying because her house was destroyed, but she had the book, and she was happy she still had the book even though she didn’t have her house anymore.

So it was a meaningful project, and it was the beginning of my using Scribus.

Jehan: Are there things sometimes you feel you are not able to do with free software? You already answered this yesterday, so I’m just asking again to hear you saying it.

Nara: When I see art – art is everything, design is everywhere – I can’t see something and think about “I can’t it do with free software”. I can do it – maybe I can’t do it because of my creativity or because I don’t think about it, but technically I can do it, you know. We have the tools to do it. We have other ways, but we have the tools I think – in my area of design.

Simon: What would interest me is, you mention that you use quite a lot of different tools, like GIMP, Inkscape, Blender, Scribus -

Nara: Blender not yet, though I started animating in the timeline. In the movie that we showed, the first one that was in 2D, I animated parts of that.

Simon: But there are a lot of different tools that you and your colleagues use. When you start a project, do you pick one of the tools and stick to it, or is more like you start using one tool then transfer the result to a different tool?

Nara: Yes, it was like each tool was like a room of a house. I live in the house, there’s a lot of rooms, and sometimes I’m in the living room, other times I’m in the bed room, other times I go to the kitchen. It’s like I have a bottle, and I take the bottle here and there.

I don’t choose the software. I plan the project, I think about it, and think “How am I going to make this?” So I will start drawing in MyPaint. But I need it to be a vector, so I save it, open in Inkscape and add a vector. But ah, I need an image in the background. So I open the image in GIMP, I work with the image there, then import into Inkscape, okay. But oh, now I have to print it. So I save what I can save in vector I save in vector, and what I can’t save, I export. And I go to GIMP, transform it and edit it, and I take everything, go to Scribus, put them together, and make a PDF. More or less like this. I’m always going back and forth between the programs.

I think it’s very complicated, but for me it’s very simple. But when I teach things like that it sounds very complicated.

Jehan: Do you have any questions, Aryeom?

Aryeom: I feel like I am in her head. I totally understand – I work the same way. Maybe later if I have any questions I’ll ask.

Nara: I learned everything by myself. So I don’t like tutorials, you know?

Aryeom: You don’t like tutorials?

Nara: Yeah, I don’t have the mind to read or watch them. I learn all by myself. I think my way of working is just my way, because I learn by myself. And sometimes I get in touch with people who use the software too, I like to watch them because people do things very different that I do, and things more easily. And sometimes I teach the software to someone, and in two weeks or three, I go to see what the people are doing. “Oh my God, I’d never think of that way!”. It’s very fun because of this.

I don’t like to do workshops because of that. I think my style of work is very crazy. But we can talk about it!

Jehan: So right now you have a big animation project. So maybe can you speak about it?

Nara: Well, Farid is the director. He writes the script. I am the art director, but I also help him with the script and doing all the storyboards. I do it in MyPaint. I was a little worried because I’ve never done a storyboard before. So I study a little, see other’s storyboards, and make it for the animation. And we are talking with people who want to work with us on the animation – and I was happy because people always say “You have a beautiful storyboard!”. I was worried about that.

I think we are, I don’t know, opening ways. Because we are not a 3D studio but we want to do 3D animation, so we have to contact on a lot of other people in Brazil and Latin America, and even in Europe. It’s been like a dream to make it. And we want to make it very fine, very good, because today if you are seeing bad 3D, then you don’t watch it. Because you have Pixar, you have Disney, you have a lot of others. I don’t think that we’ll be like Pixar, but we have to do something very good and great to be seen, you know? I think this is our goal. We want to make something very nice, very good that everyone wants to see.

We’re telling Brazilian history of Quilombo, when there was slavery. Some slaves ran away and made a tribe, a community of their own and lived there. And these communities survive until today. And some of them have a lot of different cultures. It’s like they’re isolated. And the story is about one of these communities. In Brazil the agriculture is taking the lands of these people, because they have a paper that says “We own these lands”, but actually these peoples have been there for 300, 400 years.

So we are telling the story of a girl who lived in a community like this. And they’re being pressured to go out and leave their lands. The story is a fiction, but it’s based on real facts. This is the history. It’s going to be like 10 minutes, it’s a short one, but it’s a real movie and after it’s finished, we want to continue it. Make like episodes or a long movie – it’s just like a pilot. But we need the pilot to get a bigger step.

Aryeom: I feel so moved, because our ZeMarmot project is also like this.

Nara: Here in Brazil there’s a law, I’m not quite sure, that for free television and private television, 50% of programs have to be Brazilian programs. Because it’s all foreign programs, so the government says that 50% have to be produced here in Brazil. So I have a lot of opportunities in that way for animated series.

Jehan: So you plan to distribute on TV.

Nara: Yeah.

Aryeom: Why did you choose 3D? Why not 2D?

Nara: Because we love it! We really love 3D, we’re really passionate. We started using Blender, even for 2D, but we want to go to 3D you know. We have some experiences, and we like the visuals of the movie – we actually don’t work with 3D, but we want to. A lot of people do that – I think 2D is less expensive and -

Jehan & Aryeom [in unison and laughing]: I don’t think it’s less expensive!

Nara: No? We like 3D. We want to make it – it’s so popular for the kids, for everyone. We want this movie not to go to the festivals and stay there. A lot of good films here are made this way. The very good films go to the festivals, earn their prizes, and no one’s ever seen the movie. “Oh you’ve seen that movie? No!”. It will never go to the cinemas.

We want it to have the chance to become popular, you know, a lot of people really watching it. And 3D has this affection, people really like these.

Jehan: I know you said you also appreciate Creative Common licenses and stuff like that, so is this movie going to be under such a license?

Nara: Yes, it’s going to be an open movie! You can take the characters and make another animation by yourself. If you want to take everything, the characters, the background, everything, and animate another story, you can do this.

Jehan: Which license?

Nara: We haven’t thought about it yet, but the kind of license where you can make anything.

Simon: You said 3D. I sometimes have the impression that 3D in some way is more limited in what you can do artistically compared to 2D.

Nara: Yes, it is.

Simon: So this is not a factor for you?

Nara: No. Because in 3D, it’s like you said. If you’re doing a 2D animation, I don’t know, you can do a lot of types of techniques. Like it can be black & white, it can be color, or so many types – it’s like art in stop motion. 3D is different – you have a character, and you have the scenery, and the scenery is just the scenary. You can make some tricks with lighting and shading and colors, but it stops there. It’s an artistic limitation, I agree with that.

Aryeom: In your team, no one had any experience making 3D animations?

Nara: I animate, but I know how to take the characters and make them move. But I’m not an expert. Farid knows that too and know how to make a 2D animation in Blender. But 3D is a new challenge for us.

Jehan: I think also the question was, you are a designer so you usually work in 2D. So we would expect someone who draws would want this drawing to come to life, than just doing the drawing and give it to someone else to make the actual final thing.

Nara: I have difficulties with this. I get tired of drawing very quickly. I can’t imagine myself drawing the same character more than, I don’t know, 10 times. I think I would die if I did that.

Aryeom: Haha, I’m dying!

Nara: It’s like my style. This book was difficult to me, because I had to draw the characters the same. They have to look the same every time I draw it. I don’t like that. I like to do one drawing and it’s over. They have to repeat and be the same. I like the work, but the process of doing the same thing is difficult for me.

Jehan: So you prefer to just draw something and let someone else repeat it again and again.

Nara: Yes, like the computer!

Aryeom: To make a series, an episodic drama, it’s easier to make in 3D. For long form, it’s good I think.

Jehan: Yes, for long form, but for short movies it takes longer due to preparations.

Nara: So it’s not my kind of thing.

[Nara hands out a book]

Nara: It’s by a friend of mine who wrote the story and he asked me to make the drawings. I don’t do a lot of kid stuff, but I like it. And it invites kids to draw at the end of it. It talks about what city do kids want to live in, and what city we want for ourselves. We have a lot of problems in the cities here, and I like the idea of book, to let kids dream about the city because we want that dream to come true.

Aryeom: What about Gunga’s future?

Nara: Ehh, I expect in the future that we have more people working with us. And we have more companies work with us with free software, you know. I’d like to get larger but not too larger. Because I want my life too!

Aryeom: Wise!

Nara: But I’m happy now because last year two new people joined the studio, and it’s a lot more fun to work with more people. We exchange experiences, and I think I want to grow in that way, to get a little bigger and get more partners. And work with more cinemas! It’s more difficult because it’s expensive to work with cinemas, working with animations. We like to do more for ourselves. We make a lot of productions, videos for other companies, for the government, so we’d like to do more for ourselves – like our stories, less for them, more for us.

Jehan: Okay, maybe the last question unless someone has something. Do you have any requests for GIMP developers? Other than on-canvas preview because we already have it!

Nara: I will see the new version you talked about after this.

No, I’m okay. I think I’ve used it for such a long time that I’m so adjusted to it. In the beginning I had a lot of issues – if you gave me a paper then I would fill it with “I want this, I want that! Why do I have this? I can’t believe it!”

But today it is so natural to me that I had to think about it before coming here, because I’ll be meeting people that I want to talk about it with. And I think well, there are little things I want to change in the software. But I think that I have this because I’ve been using it for so long. People are always comparing it with propriety software, and I don’t compare it anymore because it’s been such a long time since I’ve opened something like Photoshop.

So, I’ll think about it.

Jehan: But in the end it just works!_

Nara: Yeah. I’ve written some*, but not for GIMP, for Inkscape, Scribus…

[Editor’s note: Jehan misheard the word “some” here as “song”]

Jehan: Ah! A song for everyone but us?

Nara: I used an earlier version of Inkscape which had a lot of bugs. They just changed it and so I have just bugs for Inkscape. Bugs are bugs.

Jehan: Ah, it’s bugs, not a song!

Nara: Yes, for Inkscape. For Scribus, I have some issues with development.

Aryeom: So you have bugs for them, but you have requests for us. So it’s good!

Jehan: Ah, okay. I thought you’d wrote a song.

Nara: No no – I know my letters are beautiful but it’s not a song.

And I’m happy to meet you! Very happy. I don’t go to a lot of events like here in Brazil. I don’t have a lot of time to do that. And it’s like an investment to travel here because it’s very expensive and the country is too big, haha. So my involvement with free software is like in my community. On our street where we work, a lot of people use Linux because of us. It’s like a center, you know? Time to time, someone goes there, “Oh, I bought a new notebook, I want to install Linux, let’s do it together”.

I think my part in this is more local than global – in the community. I feel better like this. Real connection, offline. I’m not so close to the development here and the other artists. And most of them, they’re just show artists. They don’t really work with design, they don’t really live from this, you know? I tend to know people who live from free software. Most of them are professionals, who are really good at one software, but they don’t put food on the table with it. It’s a little different. I learn from them, but I want to know people who have real issues.

Because when you don’t work with it, you just experiment, you make your own goals. Like “I’m going to make this girl have make-up on her face”, and then you do that. When you work, another person puts a goal on you. Like, “Make this girl have a guitar”, and you have to find a way to do that. And the process when you make a goal versus when another person makes a goal you have to achieve, it’s very different when you’re working with the software. Because you have to go somewhere you’ve never went before. And it makes you use the software in a different way.

You understand what I’m saying? Because when I see the workshops, people are very good at doing something they always do. I want to see people doing very good things they’ve never done before. These things show the real potential of the software.

Jehan: And the potential of the artist.

Nara: Yes, and the potential of the artist. Because you can show me, Inkscape or GIMP is doing this new thing. But maybe I’m not going to use it just because it’s in the software. I’m only will use it if I need it. So, there are a lot of people who are experts in the tools and what the tools can do – to make it, you have to use all the tools combined. It’s different, it’s another level.

Jehan: Well, I think that’s a good interview. Thank you Nara!

Nara: Thank you!

Estudio Gunga

Hi everyone,

Many thanks to all the people who donate and sponsor our project!

Note: The improvements and features mentioned in this blog post are planned for the next version of Linux Mint, which is scheduled for Christmas this year.

Wayland

We worked really hard on Wayland and we got to the point where it feels solid and the experience is almost on par with X11. Wayland support will no longer be considered “experimental”. In the next version of Cinnamon, both X11 and Wayland will be fully supported.

Here are some of the improvements we implemented:

• Proper mapping (sizing and positioning) for new windows, applet popup menus and context menus
• Proper focus stealing prevention
• Many Wayland crash scenarios fixed in Cinnamon, muffin, cinnamon-session and Xwayland
• Improved support for multiple monitors and KVM switches
• Hardware acceleration throughout the compositor, desktop session, and both Wayland and Xwayland clients (via wl_drm, zwp_linux_dmabuf_v1 feedback v4,  hardware-accelerated GBM over EGL (for NVIDIA))
• Full HiDPI support (crisp icons, fixes in mouse cursors, and bugs specific to Chromium apps such as Slack or VSCode)
• Window Progress (this is what allows, for instance, to see nemo copy progress in the panel app button)
• Root applications (run via pkexec) run as Wayland clients (not Xwayland)
• Session fixes

Cinnamon

Cinnamon also received the following improvements:

• A cinnamon-list-windows command was introduced to make it easy to list all open windows and to quickly see their position, size, HiDPI/app/backend info.
• Muffin now rounds coordinates and dimensions for all Clutter actors. This guarantee crisp and precise rendering and fixes blur issues when applets or desktop components forget to do so themselves.
• Support for systemd’s graphical-session. This boosts Cinnamon’s compatibility with many upstream projects.

System

SSH keyring support was improved system-wide.

Fixes were implemented in the LightDM configuration. 

Support for fingerprint authentication was improved in Slick Greeter. Placing your finger on the fingerprint reader is enough to log in. You no longer need to press Enter afterwards.

Security Updates

Another severe security flaw was found this month. This time, it affects mintupdate: CVE-2026-59159.

I’d like to thank Robbie Loewen-Ross for finding this vulnerability and working with us on it.

Security updates were sent 3 weeks ago, for all affected versions, in both supported and EOL (End-of-Life) Linux Mint and LMDE releases.

Make sure you update your system.

Sponsorships:

Linux Mint is proudly sponsored by:

Gold Sponsors: Silver Sponsors:

Bronze Sponsors:

Donations in May:

A total of $19,612 were raised thanks to the generous contributions of 611 donors:

$531 (3rd donation), Joshua G. aka “Heptaveegesimal“
$500 (10th donation), Matthew P.
$500, skyace65
$405, Adriaan S.
$300, Jon H.
$265, Tommaso G.
$212 (6th donation), Natalya S.
$212, Evan W.
$200 (8th donation), Neil V.
$200 (2nd donation), Donald P.
$200 (2nd donation), Rick L. S.
$200, Michael T.
$180 (9th donation), Wolfgang S.
$174, Giovanni V.
$159 (2nd donation), Friedrich N.
$127, Steffen M.
$120 (2nd donation), Cameron E.
$116 (4th donation), TURBOKAN_TR
$116, Achim P.
$116, Irene A.
$116, Jessica F.
$116, Peter V.
$116, ROCHOY J.
$111, Free
$106 (20th donation), Jiří B.
$106 (5th donation), Johan V. D. K.
$106, Christian K.
$106, Claudius M.
$106, Dietmar G.
$100 (20th donation), James F.
$100 (16th donation), Mountain Computers, Inc aka “MTNCOMP aka GGPCTU“
$100 (6th donation), Stuart C. D.
$100 (5th donation), Philip M.
$100 (4th donation), Don W.
$100 (2nd donation), David W.
$100 (2nd donation), Henry B.
$100 (2nd donation), Michael D.
$100, Dennis L.
$100, Jonas H.
$100, Olga M.
$100, Vignesh I.
$100, William R.
$77, Samuel H.
$75 (3rd donation), Harry M.
$65, Joe K.
$60, Daniel B.
$58 (20th donation), Paul S. E. aka “Paul”
$58 (5th donation), Peter B.
$58 (4th donation), Charl C.
$58 (3rd donation), Mike A. aka “peppermint86”
$58 (2nd donation), Stefan A.
$58, Bogdan P.
$58, Enrico R.
$58, Georg W.
$58, Mattias J.
$58, Peter D.
$58, Peter H.
$58, Ralf G.
$58, Stephan M.
$58, TORD A. L. H.
$58, Urs N.
$57, Ulrich M.
$53 (26th donation), Bernard H.
$53 (19th donation), Christian G. aka “Chrissy”
$53 (11th donation), Intralogistiker
$53 (4th donation), Christian H.
$53 (4th donation), John F.
$53 (3rd donation), Daniel F.
$53 (3rd donation), Herbert Jan K.
$53 (3rd donation), Pierre V.
$53 (2nd donation), Holger S.
$53 (2nd donation), Karen P. aka “Kari”
$53 (2nd donation), Matjaz C. aka “TitoJBroz”
$53 (2nd donation), MICHAEL
$53 (2nd donation), Richard N.
$53 (2nd donation), Rico B.
$53, Alan H.
$53, Andreas H.
$53, ATP
$53, Bach T.
$53, Bas R.
$53, Frederic B.
$53, GIRAULT
$53, Janusch M.
$53, jeanmarie L.
$53, Jens G.
$53, Jonathan C.
$53, Jonathan L.
$53, JORDI F. S.
$53, Juergen K.
$53, Kreutzmann-Kirschner
$53, Lorenzo T.
$53, Lutz P.
$53, nathalie C.
$53, Okt D.
$53, Olav M. K.
$53, Robbie Reboot
$53, Tanku T.
$53, Walter B.
$50 (25th donation), Adam K.
$50 (20th donation), Mothy
$50 (16th donation), Anthony C. aka “Ciak”
$50 (11th donation), stewy
$50 (9th donation), Dean R.
$50 (9th donation), Khalid T. aka “k9750”
$50 (7th donation), aka “GM46”
$50 (5th donation), Leonhard R.
$50 (5th donation), Peter B.
$50 (5th donation), Peter S. aka “Pierre”
$50 (4th donation), Patrick T.
$50 (3rd donation), Terry H.
$50 (3rd donation), Thomas P.
$50 (2nd donation), abrames
$50 (2nd donation), Roy K.
$50 (2nd donation), Thomas O.
$50,
$50, Bernard S.
$50, Bobby B.
$50, Brian G.
$50, Carl Summers
$50, Christian W.
$50, Christophe K.
$50, Dany A.
$50, dave W.
$50, David H.
$50, David I.
$50, GARY A. T.
$50, James M.
$50, Jayden. A
$50, Juan M.
$50, Lowell I.
$50, Michael C. P.
$50, Michael D.
$50, Michael G.
$50, Mikel N.
$50, Nicolas V.
$50, Norman G. W.
$50, PATRICK M.
$50, paul H.
$50, Peter P.
$50, Porter T.
$50, Robert K.
$50, Sean F.
$50, Seth B.
$50, shade tree welder
$50, Simon G.
$50, Sriram B.
$50, Steven C.
$50, Thomas B.
$50, Thuan N.
$50, William B.
$49, sean M.
$44, nicolas V.
$42 (17th donation), Henk van C.
$42 (6th donation), Herve C.
$41 (3rd donation), Nicolas G.
$40 (35th donation), Aimee W.
$40 (2nd donation), Stephen J.
$40 (2nd donation), Theodore K.
$40, Paul S.
$39, swarfendor437 aka “swarf'”
$38, Daniel P.
$36, Kase E.
$35 (3rd donation), Kim F.
$35, MR J. M.
$35, Oliver S.
$35, Patrick S.
$31 (16th donation), Luca D.
$31 (3rd donation), Jeroen O.
$31 (2nd donation), Juan L.
$31 (2nd donation), Patrick U.
$31, Alexander S.
$31, benjamin T.
$31, Michael N.
$30 (12th donation), jowind
$30 (4th donation), Ron N. aka “TechNick”
$30, Eduardo N.
$30, Jeremy N.
$30, Joseph D. S.
$30, Michael U.
$30, William E.
$29, Silvan J.
$26 (9th donation), Jonathan. H
$26 (2nd donation), Jan B.
$26, Christian E. G.
$26, Iain J.
$26, Philipp K.
$25 (118th donation), Johann J.
$25 (63rd donation), Linux Mint Sverige
$25 (33rd donation), Ted S.
$25 (24th donation), Richard N.
$25 (18th donation), Donna B.
$25 (16th donation), John N.
$25, Christopher S.
$25, Mr M. W. W.
$25, Paul W.
$25, RICHARD B. C.
$25, wayne G.
$23 (71st donation), Peter E.
$23 (33rd donation), Benjamin W. aka “UncleBens”
$23 (13th donation), Frank W.
$23 (6th donation), Erich G.
$23 (4th donation), Antonio R.
$23 (4th donation), Reinhard R.
$23 (4th donation), Renaud B.
$23 (3rd donation), Ethan T.
$23 (3rd donation), Werner Palmen
$23 (2nd donation), Alexander S.
$23 (2nd donation), Arild S.
$23 (2nd donation), Hans R.
$23, Alain B.
$23, Diego P.
$23, Manuel H.
$23, Marco V. D. S.
$23, Mr B.
$23, saviour P.
$23, WALTER I.
$22 (6th donation), Peter Z.
$21 (77th donation), Bryan F.
$21 (38th donation), Stefan W.
$21 (32nd donation), Doriano G. M.
$21 (31st donation), Marek S.
$21 (14th donation), Gabriele Bandini aka “GiBi Gab“
$21 (9th donation), Harold H.
$21 (8th donation), Ezequiel O.
$21 (8th donation), Kai D.
$21 (7th donation), Michael B.
$21 (5th donation), Henning P.
$21 (5th donation), Rimas V.
$21 (4th donation), Jose C. aka “Revenarius”
$21 (4th donation), Stuart M. aka “UKStuart”
$21 (4th donation), Vittorio A.
$21 (3rd donation), Bartomiej T.
$21 (3rd donation), Michael K.
$21 (3rd donation), Nuno G.
$21 (2nd donation), Adam B. aka “Neomodus”
$21 (2nd donation), Drew C.
$21 (2nd donation), Frank T.
$21 (2nd donation), Joe S.
$21 (2nd donation), Jürgen N.
$21 (2nd donation), Stefano C.
$21 (2nd donation), Stephen P.
$21, Alessandro P.
$21, Alois P. R.
$21, Andrejs Z.
$21, Anibal L.
$21, Ayse B.
$21, Benedikt V.
$21, Bernd B.
$21, Berthold C.
$21, Christian H.
$21, Dominik U.
$21, Dylan B.
$21, Fiorenzo M.
$21, Frank M.
$21, FRED J. N.
$21, Hans-Peter K.
$21, Hubert S.
$21, Jacques D.
$21, Joachim K.
$21, Julian T.
$21, Lars S.
$21, Lucas B.
$21, Manfred K.
$21, marco B.
$21, Marco M.
$21, Maurizio D. R.
$21, Max K.
$21, Michael B.
$21, Michael R.
$21, O H. V.
$21, Olaf M.
$21, Peter P.
$21, Schütz C.
$21, Suffridus G.
$21, Ulf L.
$21, Walter G.
$21, Werner K.
$21, Z A. Z. A.
$20 (27th donation), Nigel B.
$20 (13th donation), Mark R.
$20 (12th donation), Lamont C.
$20 (11th donation), Randall W.
$20 (11th donation), Ron C.
$20 (10th donation), Anthony S.
$20 (8th donation), Orlando O.
$20 (7th donation), Kevin K.
$20 (7th donation), Mary H.
$20 (7th donation), Rimon K.
$20 (6th donation), Edward F.
$20 (4th donation), Carlos L.
$20 (4th donation), Chadwick C.
$20 (4th donation), Glenn S.
$20 (4th donation), Kurt K.
$20 (4th donation), Terry R.
$20 (3rd donation), Angel C.
$20 (3rd donation), John W.
$20 (3rd donation), Steven P.
$20 (3rd donation), Warner Cascante
$20 (2nd donation), Benjamin K.
$20 (2nd donation), Fred S.
$20 (2nd donation), Frederick B.
$20 (2nd donation), John A.
$20 (2nd donation), Joseph K.
$20 (2nd donation), Paul C.
$20 (2nd donation), PAUL G.
$20 (2nd donation), Robert K. aka “Nismo”
$20 (2nd donation), Sandra B.
$20 (2nd donation), Stephen M.
$20, Axel B.
$20, Carlos H.
$20, CD V.
$20, Charles M.
$20, Charles V.
$20, Daniel T.
$20, David C.
$20, Donald M.
$20, Dylan H. aka “D-Guy“
$20, Eric S.
$20, Glennon T.
$20, Harvey C.
$20, Ian U.
$20, J-Yves D.
$20, James T.
$20, James W.
$20, John H.
$20, john K.
$20, Joseph C.
$20, Joseph H.
$20, Jude C.
$20, JULIO H.
$20, Just Me
$20, Keith G.
$20, Luis R. R. F.
$20, mr J. B.
$20, NIRAV D. R.
$20, Pascal B.
$20, Sean M.
$20, TOMASZ W.
$20, Tommie B.
$20, Yuyong Z.
$17 (2nd donation), Peter W.
$17 (2nd donation), Sabrina F.
$15 (92nd donation), Andreas S.
$15 (12th donation), Joerg B.
$15 (3rd donation), Jorgen Rhode
$15, Amritpal G.
$15, Anthony K.
$15, Fred B.
$15, Michael W.
$15, Niels D.
$13, scott D.
$12 (20th donation), José G. aka “picaso”
$12 (17th donation), Abe Z.
$12 (15th donation), Gabriele I.
$12 (6th donation), Nikolay G.
$12 (5th donation), Ingo H.
$12 (3rd donation), Fabrizio P. aka “redshift72”
$12 (3rd donation), Pedro S.
$12 (2nd donation), aka “Admiral Crow”
$12 (2nd donation), Bojan M.
$12 (2nd donation), Nils W.
$12 (2nd donation), Robert M.
$12, Alexander H.
$12, Alexander S.
$12, Andreas M.
$12, Andrei T.
$12, Bartosz K.
$12, Christian P.
$12, Claus-Peter L.
$12, Gustav H.
$12, Ian K.
$12, Jasper F.
$12, Jean-Marc M.
$12, JIŘÍ B.
$12, Jörg S.
$12, José M. P. I.
$12, lothar G.
$12, Luca P.
$12, Olaf Q.
$12, PATRICK L.
$12, Patrick V.
$12, Przemysaw Z.
$12, Robert L. M.
$12, Tino Z.
$11 (28th donation), Adian K.
$11 (18th donation), Alessandro S.
$10 (122nd donation), Thomas C.
$10 (64th donation), Philip Woodward
$10 (49th donation), Tugaleres.com
$10 (28th donation), Christopher R.
$10 (23rd donation), Slobodan Vrkacevic
$10 (16th donation), Artem Ignatyev aka “ZaZooBred”
$10 (16th donation), Masaomi Y.
$10 (15th donation), Axel R.
$10 (13th donation), Mariusz B.
$10 (12th donation), Andreas G.
$10 (12th donation), Thomas R.
$10 (10th donation), Eric H.
$10 (10th donation), Tomasz K.
$10 (10th donation), Želimir S.
$10 (9th donation), Jeanmichel T.
$10 (9th donation), M.B.
$10 (8th donation), Thomas L. aka “hensys”
$10 (7th donation), Allen S.
$10 (7th donation), Cască de Copiat
$10 (7th donation), Honest Beneve Reviews
$10 (7th donation), Rainer B.
$10 (7th donation), Urszula S.
$10 (5th donation), Balazs S.
$10 (5th donation), Hubert F.
$10 (5th donation), Rainer G.
$10 (5th donation), Selwyn A.
$10 (5th donation), Stefan B.
$10 (4th donation), cască de copiat
$10 (4th donation), Lars A.
$10 (4th donation), Lyuben R.
$10 (4th donation), Piotr R. aka “_PAPCIO_”
$10 (3rd donation), Balázs V.
$10 (3rd donation), Dieter S.
$10 (3rd donation), Ken P.
$10 (3rd donation), Linda P.
$10 (3rd donation), Niklas K.
$10 (3rd donation), Pedro A.
$10 (3rd donation), Rafael B.
$10 (3rd donation), Ralph B.
$10 (3rd donation), Roger L.
$10 (2nd donation), Anders B.
$10 (2nd donation), Annet V. E.
$10 (2nd donation), Arne A
$10 (2nd donation), Claudiu-Stelian D.
$10 (2nd donation), Esa A.
$10 (2nd donation), Florian B.
$10 (2nd donation), James M.
$10 (2nd donation), Joachim K.
$10 (2nd donation), Judian G.
$10 (2nd donation), Robert M.
$10 (2nd donation), Thomas L.
$10 (2nd donation), Wilhelm H.
$10 (2nd donation), Wolfgang R.
$10, aka “Improntus”
$10, Adam S.
$10, Alain G.
$10, Alan Y.
$10, Alfredo G. G. R.
$10, Andreas S.
$10, ANDRES Y. R.
$10, Anonymous
$10, Antero K.
$10, Axel S.
$10, Ben M.
$10, Bernd F.
$10, branko S.
$10, Braz G. D. L.
$10, Carlos S.
$10, Cezary Z.
$10, Christopher H.
$10, Christopher M.
$10, Chuck Monty
$10, Daniel K.
$10, david A.
$10, David L.
$10, Deacon M.
$10, Didier A.
$10, Djordje N.
$10, Eduardo P.
$10, Edward P.
$10, Everteal
$10, Fabrice D.
$10, Filip K.
$10, Gaston N. P.
$10, GERALD F.
$10, H.
$10, Heinrich R.
$10, Herbert H.
$10, HONG J.
$10, hshin
$10, Jair H.
$10, James W.
$10, Jan K.
$10, Jean-Michel G.
$10, Johannes D.
$10, John C.
$10, Jonathan N.
$10, Juan R. T. I.
$10, Kacper B.
$10, Kaj K.
$10, Karl-Heinz L.
$10, Karthik Murali
$10, keith B.
$10, Keith T.
$10, Kelly C.
$10, Kelvin M.
$10, Klemen R.
$10, Liam O aka “locobean”
$10, Lorentz A. L.
$10, Maik G.
$10, Marc C.
$10, Maria C. M. H.
$10, Matthias H.
$10, MI N.
$10, Michael H.
$10, Mingfei G.
$10, Myriel E. R.
$10, Niels C. M. J.
$10, Oscar G. M. E.
$10, Philipp S.
$10, Qifeng S.
$10, Raul O.
$10, Richard P.
$10, Roger L.
$10, Sam G.
$10, SAMUEL K.
$10, Skalli
$10, Stavros S.
$10, Stefan H.
$10, Svenn M. N.
$10, Tatsunori O.
$10, tbnet.pl
$10, Theodore C.
$10, Thomas W.
$10, Tobias A.
$10, Vágó Z.
$10, vanhsana D.
$8 (4th donation), Marcelo A. Maito
$7 (5th donation), Jordan S.
$7, Brodie R.
$7, Dennis C. H.
$7, Lorenzo aka “Kafka”
$7, Tomasz J.
$266 from 77 smaller donations

If you want to help Linux Mint with a donation, please visit https://www.linuxmint.com/donors.php

Patrons:

Linux Mint is proudly supported by 2,326 patrons, for a sum of $5,334 per month.

To become a Linux Mint patron, please visit https://www.patreon.com/linux_mint

🐛 Bug Fixes & Minor Changes

• Exposed missing strings to translations (#1168) by @himu-gupta in #1168

🌐 Translations

• Updated French translation using Weblate by @Matth7878 in commit
• Updated Latvian translation using Weblate by @Coool in commit
• Updated Portuguese (Portugal) translation using Weblate by @AntonioOliveira2 in commit
• Updated Estonian translation using Weblate in commit
• Updated Czech translation using Weblate in commit
• Updated Hungarian translation using Weblate by @summoner001 in commit
• Updated Polish translation using Weblate by @Aga-C in commit
• Updated Chinese (Simplified Han script) translation using Weblate in commit
• Updated German translation using Weblate in commit
• Updated Bosnian translation using Weblate in commit
• Updated Italian translation using Weblate by @Wiccio in commit
• Updated Dutch translation using Weblate in commit
• Updated Serbian translation using Weblate by @eevan78 in #1167

❤️ New Contributors

• @AntonioOliveira2 made their first contribution
• @himu-gupta made their first contribution in #1168

🐛 Bug Fixes & Minor Changes

• Increased max article download size to 3 MB from 1 MB (#1164) by @spacecowboy in #1164
• Restored scroll position indicator in the article reader (#1165) by @mvanhorn in #1165

🌐 Translations

• Updated Tamil translation using Weblate in commit
• Updated Czech translation using Weblate in commit
• Updated Latvian translation using Weblate by @Coool in commit
• Updated Italian translation using Weblate by @Wiccio in #1159

🚀 Features

• Use feed entry id as fallback link. (#1144) by @fictiontoreality in #1144
• Upgraded export format so saved articles can be imported again (#1131) by @edd255 in #1131
• Added on-device local as an option for translation (#1143) by @JaredTweed in #1143

🐛 Bug Fixes & Minor Changes

• Widget stuck in loading (#1137) by @MatthewTighe in #1137
• Corrected three sync read-status bugs (#1141) by @spacecowboy in #1141
• Resolved flaky test caused by identical generated pubDates for undated feed items (#1146) by @spacecowboy in #1146
• Corrected defaults causing AI translation appear enabled on upgrade (#1153) by @spacecowboy in #1153
• Prevented OOM crash when fetching or rendering large articles (#1154) by @spacecowboy in #1154

🚜 Refactoring

• Cleaned up sync read-status layer (#1142) by @spacecowboy in #1142

📚 Documentation

• Added logging conventions to AGENTS.md (#1148) by @spacecowboy in #1148

🌐 Translations

• Updated Chinese (Simplified Han script) translation using Weblate in commit
• Updated French translation using Weblate by @Matth7878 in commit
• Updated Czech translation using Weblate in commit
• Updated Latvian translation using Weblate by @Coool in commit
• Updated Polish translation using Weblate by @Aga-C in commit
• Updated German translation using Weblate in commit
• Updated Hungarian translation using Weblate by @summoner001 in commit
• Updated Estonian translation using Weblate in commit
• Updated Indonesian translation using Weblate by @arifpedia in commit
• Updated Serbian translation using Weblate by @eevan78 in commit
• Updated Spanish translation using Weblate in commit
• Updated Ukrainian translation using Weblate in commit

❤️ New Contributors

• @arifpedia made their first contribution
• @edd255 made their first contribution in #1131
• @fictiontoreality made their first contribution in #1144

GIMP is Free and Libre Open Source Software, but none of it is possible without the people who create with and contribute to it. Our project maintainer Jehan wanted to interview the volunteers who make GIMP what it is, and share their stories so you can learn more about the awesome people behind GIMP!

Early interviews with co-maintainer Michael Natterer and Michael Schumacher were published shortly after the first Wilber Week. Unfortunately, the rest of the interviews from that event have never seen the light of day - until now!

Our previously resurfaced interview was with Simon Budig. The interview in this article is about Øyvind Kolås. He is the maintainer of GEGL and babl, the color engines of GIMP. His work was instrumental in (among many other things) the long-waited non-destructive filters implemented in GIMP 3.0!

This interview took place on February 4th, 2017. In addition to Jehan and Øyvind, Michael Schumacher, Simon Budig, and Debarshi Ray were also involved and asked questions.

Jehan: Okay, hello Pippin! So, first off, how should we call you, Pippin or Øyvind?

Øyvind: If people know how to pronounce ‘Øyvind’, that is perhaps easiest. In some contexts it is a difficult name to pronounce and I have to go by my nickname Pippin.

Jehan: Ah, and where does it come from?

Øyvind: The nickname Pippin originates from Lord of the Rings. The first time I went on IRC, must have been ‘95 or ‘96, I had to come up with a nickname for myself, and I chose the nickname of a hobbit. I used the nickname “Sméagol”.

Jehan: But you’re not very small.

Øyvind: No, but Sméagol is the hobbit in terms of Gollum, and I kind of decided that I didn’t want to have the association that came along with that hobbit. So after just one day of using that nickname I skimmed a little bit through the history of the Lord of the Rings again, and noticed that the “Pippin” hobbit might be more appropriate. He’s a hobbit that’s a little bit too curious – he throws stones in Morannon and stares into Saruman’s palantír and wonders how things work.

Jehan: So, how many times have you read Lord of the Rings?

Øyvind: Two or three times? I’ve seen the movies more than once.

Jehan: How are the movies?

Øyvind: They’re okay. They’re long!

Jehan: So, you’re the GEGL maintainer. Maybe first, let’s explain what GEGL is. For people who read the website, they may know GIMP, maybe not necessarily GEGL.

Øyvind: GEGL is a library or system where you can plug components together. You can create chains of image manipulation filters or operations. So you can first adjust the colors of an image, and then apply some sharpening to it. So you can construct those as a flow chart or similar – “First do this then do that, then do that” – so programmers can create data structures representing such chains or flows of image data, and developers can use such components to use in the chain.

Jehan: And so how did you come into this project?

Øyvind: I had been using GIMP for quite a while, and then at some point I was experimenting with writing my own video editor. And I started implementing various transform tools and operations – I implemented perspective rotation tools and similar. And while I was doing that, I was also taking a look at how GIMP was doing some such transformation tools and operations. And I realized that the perspective transform in GIMP produced not quite the results that I would like it to produce.

It had big problems with moire and aliasing when you did severe perspective transforms, for instance. So with my newly gained knowledge of making something similar myself, I sat down and tried to figure out how to improve what GIMP was doing. So I made a patch fix to add adaptive subdivision super-sampling to the transform tools.

Jehan: So it was not GEGL?

Øyvind: It was for GIMP. That’s how I got involved in the GIMP project, it was my first patch that I did there. But even that was after I had ran into many of the people from the GIMP project at a GNOME conference in Copenhagen in, I believe, 2001.

Jehan: Okay. So, how does GEGL change GIMP? What is GEGL for GIMP?

Øyvind: Well, I’m the wrong person to ask that question. I know how GEGL works. I know many of the needs of GIMP. But the person who has the greatest knowledge and detail of how GEGL makes that work and happen for GIMP is Mitch.

Jehan: We should have asked him yesterday then! Thank you. So, maybe you can still explain some of the cool features in GIMP. Like what everyone has been talking about, such as non-destructive editing, which is enabled by GEGL?

Øyvind: So this graph-based data-flow chains of operations that you can do with GEGL – most parts of GIMP have been transformed to make use of that. The core thing that is currently non-destructive editing in GIMP is the layers dialog. Other software has more capabilities there, but it’s not easy for us to know what interface to provide and present to the user to add such capabilities as drop shadows, or blurs, or color adjustments.

Jehan: It’s easy or not easy?

Øyvind: It’s easy to do it as a hack or as a proof of concept, but it’s more difficult to figure out how to do it in a way we can guarantee will be stable for many years into the future. So where we are currently, as we are close to being able to release GIMP 2.10 is that we’re doing all the layer processing that GIMP 2.8 use to do, but there’s no hacks – we’re using GEGL as the engine instead.

Jehan: So, do you use GIMP a lot?

Øyvind: Sometimes GIMP is the appropriate tool, and sometimes there’s other existing software that I use as a tool. And sometimes the tools I want or need don’t exist, and then I try to make those tools.

Jehan: You also have a background as an artist. Could you maybe speak on this?

Øyvind: From when I was a teenager, I’ve been doing both visual arts such as painting and drawing, and being interested in creating media in various forms such as videos. The only form of creative expression that I haven’t much played with is music. My original education and training was in fine arts. Only after having done that for a few years did I go back to computers and digital media, and go more the academic route in computer science.

Jehan: So you studied computer science before, then you went to art?

Øyvind: No, but I’ve been doing computer graphics since I was 14 or 15 years old. I was inspired by the demoscene community and having access to dial-up bulletin boards systems with people discussing programming techniques and languages. They contained tutorials in C and Pascal and Assembly and also involving Turbo Pascal. Demoscene-style graphics are things I’ve done since before University level age, along with experimenting with painting and traditional physical drawing media.

Jehan: So how do you see the future of GEGL and free software graphics in general? How do you see GEGL in 20 years?

Øyvind: If GIMP still exists in 20 years in some form of UI, then most probably GEGL is part of that story as well. I hope that some of the existing core processing code actually doesn’t survive! But the idea of the graph and maybe some of the operations that are hooked up to each other, I hope that continues to exist. Just like how other applications that use GEGL like video editing software, GIMP, GNOME Photos – the API and how they do that, I hope are very similar. But maybe both the CPU based processing code and the OpenCL one, will have been replaced.

Jehan: There’s something I’ve never really completely understood. If you look at the GitLab of GIMP and GEGL, they started around the same time. So why are they getting merged only recently?

Øyvind: I only know stories of this – I haven’t been around in the project since in the beginning.

Michael Schumacher: You said you’re not the best person to ask how GIMP is using GEGL. So can you tell us how you wish it was being used, or how you think it could be used more? Because I recall you making comments on IRC in that regard.

Øyvind: Well, we are close in 2.10 to a state where I am happy about how things are at the moment. It’s been a while since I was unhappy about how GIMP’s projection was driving the layer compositing code or creating a graph for compositing with GEGL – it’s been a long while since it was fixed. So when it comes to the performance of doing those things, or the performance on-canvas preview of vectors, the current problems are more in GEGL land than GIMP land.

Jehan: In GEGL?

Øyvind: Yes, it’s an architectural puzzle to figure out, before GIMP should change how it does its rendering to make use of the new capabilities in GEGL.

Jehan: So how fast can GEGL go? How fast do you think (compared to now) it can improve?

Øyvind: I think for most filters in common use for photo manipulations as well as working with multiple layers, that even on a CPU that you should have 10 frames per seconds updates on dragging layers around as well as doing color adjustment to the photos or the individual layers. I don’t see why that should be a big problem. That is what solving the mip-mapping problem should provide.

Debarshi Ray: Any plans for what you want to use for GEGL’s API documentation? It used to use kind of like GTKDoc at some point. There’s always the website, but any plans?

Øyvind: It currently displays a GObject introspection repository data directly on the website using Javascript. I kind of hope that the documentation people start working towards more documentation on GObject introspection and perhaps we align with something they do, if they do something like that.

Jehan: Do you want to see GEGL in more software, not only GIMP?

Øyvind: That would be really nice because if people then create more filters and interesting things you can do in that software, it becomes available in GIMP and also in other software.

Jehan: Actually that’s very interesting. Can you explain a little about the architecture of GEGL which makes it so that its filters can be available everywhere? How it will work in other software that integrates GEGL?

Øyvind: Well, you could imagine that for the operations you have in GIMP in terms of filters, there are many that you invoke for an image, that could be something that also you could apply as an effect in a video editor to a clip. You can animate some of the properties over time, like increasing or decreasing the blur on some background that you composite something on top of.

Michael Schumacher: What would you suggest people should do to learn about the capabilities of GEGL and how to use it, either in GIMP development or in their own software?

Øyvind: Mostly, study what already exists, and if there is anything doing something similar to what they want already, then try to tweak that to do something new.

Michael Schumacher: Do you have a suggestion on what someone can use to play around with GEGL? For instance, if someone has fairly decent experience developing software, is there some kind of best approach like “Oh, use Python”?

Øyvind: I haven’t really tried to use any of the language bindings apart from C in a long while. I can see how approaching a library framework with C can be difficult for some users. But no, I don’t know of any of these integrated languages that have a very good integration.

Simon Budig: I think that the first start would be to use the GEGL command line tool and build trees in XML or something like that.

Øyvind: I guess there’s also the data formats, the XML and JSON based data formats, as well as the data format you can fully construct on the command line just chaining operations and properties.

Debarshi Ray: Can you comment on how GEGL compares to GStreamer, since they are both graph based and you can even do some image manipulation with GStreamer like their application does? Would it be easier with GEGL?

Øyvind: GEGL is focused on rendering and creating images. GStreamer is focused on playback and streaming of video. So the things passed around between the components of the graph of GStreamer are always full frames of videos. And it has many considerations for how to deal with playback and pre-feeding data to be able to stay in continuous playback and similar. Whereas GEGL has only a concern about generating pixels for a static graph.

So the concerns involved in piecing together video codecs and the muxing of codecs and doing those things in a data flow, are different from doing just image processing with it – but kind of the core idea, which is visual programming using a graph instead of more like a human language with abstract syntax to create, is shared between GEGL and GStreamer. The data flow based approach and creating a framework for visual components and ordering.

Jehan: I have a similar question. There was an efficiency test – I think the product name was libvips – with various graphics software library, and GEGL was in the list. In the tests they said it was worse.

Øyvind: Maybe that has improved recently, I’m not sure. Both GEGL and babl have had a traditional approach to bench-marking at runtime when things are already up and running and for interactive use. Whereas those benchmarks are based on equating command-line utilities with those that also include all the overhead of start-up. That is something that has improved recently in both, particularly in babl – it keeps measurement and profiling information from previous runs around in a file on disk so it can load, so it doesn’t have to do a lot of computations the first time you do a computation of a particular kind.

But I haven’t really re-run those benchmarks lately. But a lot of the trouble involved for GEGL and babl is that they’re very generic and have many plug-ins and do loads of file system access and those things before it can do any form of processing.

Jehan: Have you tried this libvips library?

Øyvind: Yes.

Jehan: How does it compare – not efficiency wise, but API, architecture? Why would one choose GEGL over libvips?

Øyvind: That I don’t know. Depends on the capabilities of what you need it to do, GEGL is well on the way to have most traditional GIMP filters as operations. I haven’t studied the actual program APIs and how you would rig up pipelines with those APIs. I looked more at the graphical user interface of libvips – it’s an Excel spreadsheet-like approach to it, where you refer to data in a different cell. It’s one way of expressing a graph but I don’t know the actual programmatic APIs.

Jehan: So there’s different ways of expressing graphs?

Øyvind: GEGL’s API for expressing and manipulating the graphs is loosely based on the W3C’s Document Object Model and hierarchical tree structures. I have no idea if or what type of API inspirations that libvips is using.

Debarshi Ray: I have a question. GIMP has a new website, shiny and everything. Will GEGL have a new website as well?

Jehan: It has to be shiny!

Øyvind: Do you have a PNG file called “Shiny” that we can use? Or do you also have some CSS and some pages and content for the GEGL website?

Debarshi Ray: No, I have nothing.

Øyvind: I have tried for the last two or three years to make some existing GIMP and GEGL contributors excited about writing some documentation and content as part of the website. They do rebuild the website every single time they build GEGL and it ends up in the docs folder of the website. But it seems like it’s actually easier to get people to contribute code and new operations and exciting new features in GIMP and things than to get them to improve the website documentation.

And I must admit that I’d rather fix bugs and performance and features than spend too much time on the website.

Jehan: So, unless anyone has another question, we can finish…

Simon Budig: Did we talk about the Patreon?

Jehan: Oh right! So you’re trying to live off free software coding, especially GEGL. Can you try to explain it?

Øyvind: I spent a lot of time over the last ten years doing code for both GEGL and GIMP, but also many other projects. It is strange how the media exploration experiments I do in code seem to not really have much cultural worth in society. So creating software and creating tools is not something that seems to be on the culture budget of any Western European country or something that would be considered part of improving the digital literacy of the population. It’s something that’s left up to private companies to maybe create software tools – but it’s not something that you’ll find on the budget of a country, that they want to let people improve and create tools for, say, image manipulation.

Maybe that’s a horrible way to start out to explain this.

Jehan: You can start over if you want.

Øyvind: I’ve been playing with creative expression in both visual media and in code for a couple of decades. I have made music videos, I’ve made short films, I’ve made paintings and I’ve made software. And sometimes when I make software, I get paid for it because there’s other business interests behind wanting it to exist. But I consider many of the contributions I’ve made to GIMP and GEGL to be valuable contributions, and that it would be good if I could do more of that type of experiments that end up in actual software – but also freely be able to do my own research and find out how it is possible to do a certain thing with videos or images or other ways that you can combine digital media types.

I’ve been fortunate enough to have had a software development job where I made a bit of money and had a safety cushion. So I’ve been living off savings for quite a while, creating software for GIMP and other things while traveling. But lately I’ve seen that my bank account has started screaming and turning red soon. So I was wondering, maybe this Patreon thing that I’ve seen both other software projects and other types of things suggested that I could try to keep bills paid. And I decided that okay, in some sense it’s asking for money and a little bit begging to be like a street music performer and saying “I’m making this thing and if you’re enjoying it, maybe you’d like me to continue doing some of the things I’m already doing”.

And it turns out there are a couple hundred people already who would like me to continue writing code and sharing it publicly and openly. That at least sustains me roughly on the level of unemployment benefits in European countries. And I hope that this will even slightly increase – I will not have a Silicon Valley level software developer salary, but I’ll have enough money to cover my expenses.

Øyvind’s portfolio website

🚀 Features

• Added stripping of tracking parameters before opening URLs (#1097) by @mvanhorn in #1097
• Preserve article scroll position when Android recreates the process (#1115) by @boringrgb in #1115
• Added ability to translate articles with AI service (#1072) by @JaredTweed in #1072
• Add per-feed article metadata thumbnail enrichment (#1130) by @tokenflood in #1130
• Enabled arm memory tagging extension (#1132) by @flexxxxer in #1132

🐛 Bug Fixes & Minor Changes

• Added initial widget state and timeouts for bitmap loading (#1113) (#1114) by @MatthewTighe in #1114

❤️ New Contributors

• @flexxxxer made their first contribution in #1132
• @tokenflood made their first contribution in #1130
• @boringrgb made their first contribution in #1115
• @mvanhorn made their first contribution in #1097

Hi everyone,

We’ve got a lot of exciting news this month! But first of all, let us thank everyone involved in helping our project. Many thanks for your support and your donations!

Note that the improvements and features mentioned in this blog post are planned for the next version of Linux Mint, which is scheduled for Christmas this year.

Navigation Speed in Nemo

We significantly improved the response time and navigation performance in Nemo. In Cinnamon 6.6, a delay of 200ms was used between the moment you clicked on a directory and the moment this directory started to show its content on the screen. Some directories load faster than others, but to guarantee a smooth looking render each took at least 200ms.

200ms might not seem like much, and to be honest it never really bothered us before. But once you notice it, you cannot unsee it. Nemo now uses different rendering modes depending on the situation. It now renders some directories immediately and without delay and looks much more responsive than before.

Interactive Search

Nemo supports something called Interactive Search. Open a directory and start typing to use this feature.

In Cinnamon 6.6, a little entry appeared in the bottom-right corner to show what you typed and the view jumped to the first result which matched your query. You could then use the arrow keys to jump from one result to the next.

This feature is convenient but its implementation didn’t make it obvious or comfortable. Nemo now uses a filtered view instead.

When you start typing the entry is now added to a search bar which looks much more obvious than before and doesn’t disappear when you stop typing or when you click away.

The view gets filtered to only show results so you can see them all at once and no longer need to jump without knowing where you’re going to land.

Cinnamon Screenshots

Cinnamon is getting its own screenshot tool.

The first thing you’ll notice are the new features:

• Window screenshots can be taken with or without shadows
• Screen screenshots can include all monitors or only a single one
• Screenshots can be cropped before getting copied or saved

Under the hood, many changes were made to make screenshots look cleaner and to accommodate the differences between CSD (Client Side Decoration) and SSD (Server Side Decoration) windows.

In a CSD window, the frame and shadow are rendered by the application or its toolkit (GTK). In an SSD window they are rendered by the Cinnamon window manager directly (Muffin).

In Cinnamon 6.6, there was no option to include the shadow. The screenshot interface had an option to remove the frame but that wasn’t useful, it was buggy and it wasn’t used by GNOME Screenshot.

Although window screenshots only captured the window itself, some of the shadow was visible outside of rounded corners.

The new interface allows window screenshots to be made with or without shadow.

If the screenshot tool requests a shadow, this is taken into account when capturing the window. In the case of SSD, the shadow is re-created the same way as in Muffin.

If it doesn’t, the corners are cleaned up to remove any semi-transparent pixels coming from the shadow.

Dialogs

Cinnamon is now able to use draggable Clutter dialogs. They stay on top but don’t lock the screen, and can be moved around. This can be handy if you need to access something or click on an app before responding to the dialog.

GTK3 dialogs don’t look great and this is something we’re looking into.

Here’s a question dialog for instance.

In this dialog:

• The buttons are stuck to each other (this was a style GNOME pushed for a while, and which they abandoned since)
• The title alignment is messy
• Symbolic icons look great within apps, but underwhelming in a dialog that requires the user’s attention
• The titlebar has no title so it looks empty and useless

Here’s the same dialog with these issues fixed:

It catches the attention, puts more emphasis on the message and looks much cleaner.

Theme Improvements

The colors and contrast were improved in the dark version of the Mint-Y theme.

Frames and scrolled areas, which were rectangular, are now slightly rounded, like the buttons and combo boxes.

Treeviews and listviews got rounded as well.

This is a subtle change, but it makes Mint-Y slightly more polished.

The Mint-Y, Mint-L and Mint-X themes now use XSI icons for GTK dialogs. So when you ask a GTK application (like Xed for instance) to open something, the file dialog that pops up now uses the same icons as Nemo.

Network Improvements

Cinnamon received support for WPA3 (Wi-Fi Protected Access 3) and OWE (Opportunistic Wireless Encryption).

Security Updates and Project Impersonations

A severe security flaw was found in Xreader: CVE-2026-46529.

A PDF could provide and run malicious code on your computer. All it took was for you to open it and click a link inside of it.

This is a good opportunity to remind everyone to keep up to date with security updates. This vulnerability was fixed in version 4.6.4 (and for older releases in version 3.6.7).

While we’re talking about security, I’d also like to take the opportunity to mention project impersonations.

https://www.fullstory.com/blog/inside-a-global-campaign-hijacking-open-source-project-identities/

Malicious people are making fake websites which impersonate FOSS applications. Their goal is money, whether that’s just by generating web traffic, selling personal data, or infecting you with viruses and ransomware.

Look at Warpinator.com and hypnotix.org for example. We can’t take these down. If the host cares, they get hosted somewhere else. If we take the domain down, they get a new one.

We’ve had secure and centralized repositories since the 90s, since the very start of the Debian project. I know some of you are new to Linux and coming from Windows. Despite the fact that smartphones have used centralized software stores for decades as well now, I know a lot of people who think the best way to install something is to search for a download link and click whatever comes up. This isn’t the best way to install software. This is the best way to install malware.

NEVER, ever download an application from a website you don’t fully trust. If you do, make sure to check its authenticity with the developers. It doesn’t matter if you know the software, it doesn’t matter if it’s open-source.

Sponsorships:

Linux Mint is proudly sponsored by:

Gold Sponsors: Silver Sponsors:

Bronze Sponsors:

Donations in April:

A total of $18,746 were raised thanks to the generous contributions of 687 donors:

$637 (5th donation), Natalya S.
$265, Marleen V.
$250 (3rd donation), Mark S.
$250, Darrell L.
$212, INDUSTRIAS P. S. P.
$212, Norbert H.
$200, Paul E.
$180, Kevin M.
$106 (19th donation), Jiří B.
$106 (10th donation), Marek Stapff
$106 (8th donation), Rhydwen V.
$106 (7th donation), Bernhard M.
$106 (3rd donation), Henri-ppc
$106 (2nd donation), Daniel C.
$106, Dean C.
$106, Do. Z.
$106, JOSE L. G.
$106, Klaus B.
$106, Lex A. B. B.
$106, Martin B.
$106, Max T.
$106, Michael T.
$106, Olivier M.
$106, Philippe C.
$100 (33rd donation), John Mc aka “Land Research Project“
$100 (19th donation), James F.
$100 (6th donation), Felipe Amaral aka “famaral42“
$100 (2nd donation), Carl J.
$100 (2nd donation), Robert J. G.
$100, anonymous
$100, Ben M.
$100, Derrek B.
$100, Hermann G.
$100, John D.
$100, Michael F.
$100, Reece G.
$100, Rolando F. aka “Roferris”
$100, Thomas A. L.
$100, Thomas C. S.
$79, Siegfried L.
$75, Michael S.
$75, Michel M.
$63, Jan S.
$60, LEACH D. L.
$60, Ryan S.
$58 (2nd donation), thomas K.
$53 (17th donation), Roland H.
$53 (16th donation), Jyrki A.
$53 (6th donation), Hannu H.
$53 (6th donation), Keith H.
$53 (6th donation), Michele M.
$53 (5th donation), Uwe W.
$53 (4th donation), Siegfried S.
$53 (3rd donation), Ronan B.
$53 (2nd donation), Andreas F.
$53 (2nd donation), Jens K.
$53 (2nd donation), Olivier R.
$53 (2nd donation), Patrick K.
$53 (2nd donation), Stefan B.
$53 (2nd donation), Stephan B.
$53 (2nd donation), Thomas P.
$53 (2nd donation), Thomas P.
$53 (2nd donation), Wuming
$53, Anonymous
$53, Antoni P.
$53, Benjamin A.
$53, Bill A.
$53, Bostjan D.
$53, Burkhard P.
$53, Carlos M.
$53, Chris K.
$53, Edward N.
$53, Gunther S.
$53, Hannes B.
$53, Herbert S.
$53, Hubert K.
$53, Johannes H.
$53, Johannes P.
$53, Josh
$53, Juan S. P.
$53, Jürgen H.
$53, Lindsay W.
$53, Ludwig B.
$53, Maik T.
$53, Marion B.
$53, Martin E.
$53, Martti K.
$53, Matejas N.
$53, Mathias F.
$53, Max L.
$53, Maximilian W.
$53, Philipp B.
$53, Robert D. V.
$53, Roberto A. B.
$53, Rodolfo M.
$53, SAMUEL P.
$53, Sergio D.
$53, Slav N
$53, Steffen K.
$53, Steve Bartrick aka “Steve B”
$53, Sven S.
$53, Thomas H.
$53, Thomas P.
$53, Ton K.
$53, Volker G.
$53, Wolfgang A.
$53, Wolfgang S.
$52, Anonymous
$50 (19th donation), Mothy
$50 (17th donation), An L.
$50 (15th donation), Anthony C. aka “Ciak”
$50 (11th donation), Daniel M.
$50 (9th donation), Charles H.
$50 (9th donation), Kenneth R.
$50 (8th donation), Khalid T. aka “k9750”
$50 (7th donation), Alonzo J.
$50 (7th donation), PulpKult
$50 (6th donation), Jaime F. Zarama
$50 (6th donation), Tim A.
$50 (5th donation), Horacio M.
$50 (5th donation), xexus.us
$50 (4th donation), David N. B.
$50 (4th donation), William S.
$50 (3rd donation), Chris J.
$50 (2nd donation), Fahri Taha C.
$50 (2nd donation), George H.
$50 (2nd donation), Robert B.
$50, Amir B.
$50, Andrew D.
$50, Antonio D.
$50, Arthur M.
$50, David K. H.
$50, Don D.
$50, Fridolin.A
$50, Gerald A.
$50, Glen B.
$50, HIDENOBU O.
$50, Hovendra P.
$50, Jerry F.
$50, Jim S.
$50, Juan M. A.
$50, Markus L.
$50, Marlon H.
$50, Martina D.
$50, michael P. M.
$50, PATRICK M.
$50, Philip L.
$50, Robert S.
$50, Scott N.
$50, Sean G.
$50, Stephen J.
$50, Technition
$50, Trevor B.
$50, William I.
$42 (4th donation), Michael R.
$42, Benoit R.
$40 (7th donation), Orlando O.
$40 (3rd donation), maurice A.
$40 (2nd donation), Angel C.
$40, Hector M.
$40, Peter C.
$37 (2nd donation), Karl K.
$37, William C.
$33 (5th donation), Frank B.
$33, Samir I.
$33, Stojan A.
$31 (24th donation), Adam K.
$31 (6th donation), Matthias Versen aka “Matti”
$31 (2nd donation), Klaus R.
$31 (2nd donation), Rossella C.
$31, Christian R.
$31, Horst E.
$31, Ilja P.
$31, Maciej P.
$31, Paul L.
$31, Schule G. -. O. D. L.
$31, Ursula H.
$31, Victor M.
$30 (13th donation), Murray C.
$30 (9th donation), Frank F.
$30 (3rd donation), VICTOR G.
$30 (2nd donation), Donald K.
$30 (2nd donation), Mark B.
$30, GERARDO C.
$30, Joseph B.
$30, marumochi
$27, M. P.
$26 (7th donation), Keith P.
$26 (6th donation), Santiago
$26 (3rd donation), Andreas W.
$26 (3rd donation), Eugene G.
$26 (3rd donation), R. León
$26 (2nd donation), Norbert T.
$26, Georg N.
$26, Neil K.
$26, PourLeBienCommun
$25 (62nd donation), Linux Mint Sverige
$25 (32nd donation), Ted S.
$25 (21st donation), John W.
$25 (15th donation), John N.
$25 (3rd donation), Paul G. A.
$25, Akin B.
$25, Fred N.
$25, Jeffrey D.
$25, Masters of War Productions
$25, Robert B.
$22, I-Ping H.
$21 (70th donation), Peter E.
$21 (37th donation), Stefan W.
$21 (32nd donation), Benjamin W. aka “UncleBens”
$21 (30th donation), Marek S.
$21 (14th donation), Rob B.
$21 (12th donation), Frank W.
$21 (10th donation), Gabriele B.
$21 (6th donation), Curd-Juergen S.
$21 (6th donation), Helgi J.
$21 (5th donation), Thomas B.
$21 (4th donation), Antony L.
$21 (4th donation), Arvis S.
$21 (4th donation), Jean-pierre V.
$21 (4th donation), Monika M.
$21 (3rd donation), Andre V.
$21 (3rd donation), Armin F.
$21 (3rd donation), Ettore G. aka “Hanamigi“
$21 (3rd donation), Livio G.
$21 (3rd donation), Luca O.
$21 (3rd donation), Pawel P.
$21 (3rd donation), Snorre L.
$21 (2nd donation), Ariane R.
$21 (2nd donation), Carlo S.
$21 (2nd donation), Chris F.
$21 (2nd donation), Elias R.
$21 (2nd donation), Heinz S. aka “Heiner“
$21 (2nd donation), Helmut S.
$21 (2nd donation), Joerg P.
$21 (2nd donation), Laureano P. C.
$21 (2nd donation), M M. K. M.
$21 (2nd donation), Manuel L. G.
$21 (2nd donation), Michael H.
$21 (2nd donation), Noel V.
$21 (2nd donation), Oliver K.
$21 (2nd donation), Pe D.
$21 (2nd donation), Peter L.
$21 (2nd donation), Raphael Dieter
$21 (2nd donation), Roland W.
$21 (2nd donation), Steffen L.
$21 (2nd donation), Werner W.
$21, Adrian Y.
$21, Alastair T.
$21, Alexander O.
$21, Alfred T.
$21, Auguste M.
$21, Carlos P.
$21, Christoph G.
$21, Daniele Fornera aka “Dany”
$21, David R.
$21, Dennis T.
$21, Deon K.
$21, Dieter P.
$21, Emilie L.
$21, Fabio B.
$21, Fiorenzo M.
$21, francesco M.
$21, Frobose, S.
$21, Georg L.
$21, Günther F.
$21, Hans J. K.
$21, Hendrik B.
$21, Herbert B.
$21, Ian L. aka “Penfold”
$21, J. Hernandez
$21, James K.
$21, JAMES R.
$21, Johannes K.
$21, Judian G.
$21, Jürgen S.
$21, Karl-Ernst K.
$21, Kees D.
$21, Keith J.
$21, Marcel K.
$21, Martin C.
$21, martin H.
$21, Mervyn A. G.
$21, Michael D.
$21, Michael H.
$21, Michael J.
$21, Mikel N. G.
$21, Mikhael W.
$21, Mr. SA
$21, Paolo D. B.
$21, Páraic Seosamh Canavan
$21, Patrick U.
$21, Paul H.
$21, PEREZ aka “Alain”
$21, Peter J.
$21, Petros C.
$21, Ronald M.
$21, Salvador P.
$21, Sasha P.
$21, Sebastian K.
$21, Viljami L.
$21, Vincent A. B.
$21, Willy S.
$21, Winfried K.
$20 (52nd donation), John D.
$20 (33rd donation), Aimee W.
$20 (12th donation), Antonio C.
$20 (11th donation), Andreas G.
$20 (11th donation), Andrew D. aka ” (Thank you for LMDE7!!!)”
$20 (11th donation), Colin S.
$20 (10th donation), Randall W.
$20 (8th donation), Leela A.
$20 (6th donation), Esteemed Ape
$20 (6th donation), Michael G.
$20 (6th donation), Robert A.
$20 (5th donation), Clarence D.
$20 (5th donation), Steven M.
$20 (5th donation), Walter B. aka “Walter-CH“
$20 (4th donation), Alejandro A.
$20 (4th donation), Leah M.
$20 (4th donation), Matt H.
$20 (4th donation), Raymond T.
$20 (3rd donation), Denis V.
$20 (2nd donation), Arnold L.
$20 (2nd donation), Mohamed T.
$20 (2nd donation), Nelson P.
$20 (2nd donation), William B.
$20, Brian H.
$20, Chris M.
$20, Christopher L. H.
$20, Clifford A.
$20, Collision Detection
$20, Daniel M.
$20, david C.
$20, David R.
$20, Derek S.
$20, Dylan G.
$20, Edward B.
$20, George W.
$20, Hilary P.
$20, James K.
$20, Jason B.
$20, Jeffrey H.
$20, JOHN I. A.
$20, john O.
$20, Jonobie F.
$20, Jorge G.
$20, Joseph K.
$20, Mackenzie I.
$20, Mariusz K.
$20, Mark P.
$20, Martin S.
$20, MARYANN A.
$20, Michael A.
$20, PAUL G.
$20, Pawe S.
$20, Robert C.
$20, Robert W.
$20, SouthMicro
$20, Stephen S.
$20, Timothy D.
$20, WILLIAM A. P.
$20, William B.
$20, William J.
$17, M D.
$16, Robert K.
$16, Sahil
$15 (91st donation), Andreas S.
$15 (26th donation), Adian K.
$15, Dr. C. M.
$15, John W.
$15, Marco M.
$15, Rene M.
$12 (42nd donation), Sami Mannila
$12, Dennis Van de Poel
$12, Dominik S.
$11 (117th donation), Johann J.
$11 (17th donation), Alessandro S.
$10 (121st donation), Thomas C.
$10 (63rd donation), Philip Woodward
$10 (50th donation), Thomas Rehm
$10 (48th donation), Tugaleres.com
$10 (45th donation), Denys G. aka “GD Next“
$10 (30th donation), Bruce M.
$10 (20th donation), Adis H.
$10 (18th donation), Ronald S.
$10 (16th donation), Abe Z.
$10 (15th donation), Artem Ignatyev aka “ZaZooBred”
$10 (14th donation), RexAlan
$10 (12th donation), Mariusz B.
$10 (9th donation), Wojciech S.
$10 (8th donation), Augusto B.
$10 (8th donation), Korora Solutions
$10 (8th donation), Lars K. aka “laku3008”
$10 (8th donation), Sergei Petrov
$10 (8th donation), Steven L.
$10 (7th donation), Gary R.
$10 (7th donation), Gunnar A.
$10 (7th donation), Ian B.
$10 (6th donation), Carlos P.
$10 (6th donation), Cor D.
$10 (6th donation), Honest Beneve Reviews
$10 (6th donation), Urszula S.
$10 (6th donation), Van G. H. aka “HarryT140E”
$10 (5th donation), Marc S.
$10 (5th donation), Oleksandr N.
$10 (5th donation), S Russo
$10 (5th donation), Serge S.
$10 (5th donation), Ted H.
$10 (4th donation), Alexander B.
$10 (4th donation), Jordan S.
$10 (4th donation), Lukasz M.
$10 (4th donation), makeup
$10 (4th donation), Peter B.
$10 (4th donation), ronald H.
$10 (4th donation), Selwyn A.
$10 (4th donation), Stefan B.
$10 (3rd donation), Alexej S.
$10 (3rd donation), Andrea C.
$10 (3rd donation), Claudio B.
$10 (3rd donation), Ian S.
$10 (3rd donation), Jim R. aka “Images in Colour Inc.”
$10 (3rd donation), Juan Z.
$10 (3rd donation), Julio Casanova aka “JC67”
$10 (3rd donation), Lyuben R.
$10 (3rd donation), notar public
$10 (3rd donation), Paweł
$10 (3rd donation), Piotr R. aka “_PAPCIO_”
$10 (3rd donation), Ricardo O.
$10 (3rd donation), Thank you Linux Mint
$10 (2nd donation), Bartomiej T.
$10 (2nd donation), Brian K.
$10 (2nd donation), Dominik S.
$10 (2nd donation), Garcia J.
$10 (2nd donation), Georgi P.
$10 (2nd donation), Henry G.
$10 (2nd donation), Jacob R.
$10 (2nd donation), Joao D.
$10 (2nd donation), John M.
$10 (2nd donation), Jordi del Valle
$10 (2nd donation), Kevin L.
$10 (2nd donation), Marco E. E.
$10 (2nd donation), MAXI G. B.
$10 (2nd donation), Myne aka “Myne”
$10 (2nd donation), Niklas K.
$10 (2nd donation), Oliver W.
$10 (2nd donation), Patrick F.
$10 (2nd donation), Patty G.
$10 (2nd donation), Raul Z.
$10 (2nd donation), Richard W.
$10 (2nd donation), Steffen G. S. R.
$10 (2nd donation), Stelios Gidaris
$10,
$10, Aad T.
$10, Adam B. aka “Neomodus”
$10, Akshay B. P.
$10, Andrew C.
$10, Ann S.
$10, Anthony D.
$10, Antonio Jose Rabasco Serrano
$10, Arne A
$10, Augustin Winther
$10, Bart Meijer
$10, BM
$10, Bobby H.
$10, Brantley E.
$10, Bryan M.
$10, Cedrik P.
$10, Charlie M.
$10, Claudio D. C.
$10, Clément P.
$10, Compucall
$10, con G.
$10, cz
$10, Daniel R.
$10, Daniel W.
$10, David A. E. G.
$10, David R.
$10, Deniz H.
$10, dominik P.
$10, Elia Bedendo aka “@eliabedendo_“
$10, Felix W.
$10, Fidel G. M.
$10, Florin M.
$10, francesco P.
$10, Frank V.
$10, Friedrich G.
$10, Fuchsiano
$10, Gary B.
$10, GEJM V. W.
$10, Gregory S.
$10, Guinle C.
$10, Harry T.
$10, Henning B.
$10, Hichem E.
$10, Ihar K.
$10, Irmgard J.
$10, J.F. V.
$10, J.P.W
$10, Jack J.
$10, Jacques T.
$10, Jan V.
$10, Jean D.
$10, Joep6161 aka “Oldgit”
$10, Johannes R.
$10, Jose D. S. L.
$10, Joseph S.
$10, KARAM S.
$10, KERMAN Z.
$10, Kjetil A. E.
$10, Kris D. V.
$10, Krzysztof O.
$10, László D.
$10, Laurent E.
$10, Linas M.
$10, Luca L.
$10, Lucas J.
$10, Maciej S.
$10, Mario D. P.
$10, Martin Kasper le Grand
$10, Mathieu J.
$10, Matthew G.
$10, Maurice K.
$10, Michael D.
$10, Mubarik A.
$10, Murányi és Társa Bt.
$10, Nenad Đ.
$10, Nils B.
$10, Nils W.
$10, Noureddine M.
$10, OpaManni
$10, P.H aka “Lost”
$10, PALAO B.
$10, Patrik T.
$10, Pavel P.
$10, peter H.
$10, Peter S.
$10, Quentin H.
$10, Raffaele G.
$10, Randy S.
$10, Rasmus
$10, Ricardo O.
$10, Richard G.
$10, Richard T.
$10, Robert B.
$10, Robert E.
$10, Robert M.
$10, Rocklyn H.
$10, Rodrigo I. C.
$10, Ronal P.
$10, Ronald T. M.
$10, Russ J.
$10, Ryan M.
$10, samuel T.
$10, Scott P.
$10, Simon P.
$10, Szymon A.
$10, T. U. I.
$10, Thomas H.
$10, Thomas R. P.
$10, Thomas W.
$10, Tim S.
$10, tino R.
$10, Tobias H.
$10, Tony M.
$10, Ülo P.
$10, Viktor D.
$10, Volker B. aka “schnoog”
$10, Volker J.
$10, Werner J.
$10, Wesley da Guia
$10, Xerofable X.
$10, Yevhenii Bondarenko
$9 (2nd donation), Roger S.
$9, AM.
$8, STEVEN N.
$7, Dale
$7, Jeff D. B.
$6 (3rd donation), Alexandre M. aka “Maz”
$272 from 104 smaller donations

If you want to help Linux Mint with a donation, please visit https://www.linuxmint.com/donors.php

Patrons:

Linux Mint is proudly supported by 2,274 patrons, for a sum of $5,297 per month.

To become a Linux Mint patron, please visit https://www.patreon.com/linux_mint

• Milestone

This is bug-fix release for 1.29.0.

Feature highlights✨:

• Accept .txt import of feed URLs in additional to e.g. OPML
• New CLI for automatic periodic SQLite export with retention
• More feed info: last received date, publication date

Bug fixes highlights 🐛:

• Fix cookies with some browsers
• Fix search in shared user queries with empty results

UI highlights 🖼:

• Improve Web browsers compatibility

This release has been made by @Alkarex, @Frenzie, @IEEE-754, @Inverle, @McFev, @ciro-mota, @cweiske, @polybjorn and newcomer @mzl2233

Full changelog:

• Features
  • Accept .txt import of feed URLs in additional to e.g. OPML #8818, #8837
  • New CLI for automatic periodic SQLite export with retention #8819
  • More feed info: last received date, publication date #8799
• Bug fixing
  • Fix cookies with some browsers #8867
  • Fix search in shared user queries with empty results #8863
  • Fix XML errors with loading invalid OPML in lib_opml library #8652, #8853,
    lib_opml#48, lib_opml#51
  • Fix ensure maximum number of feeds also with Dynamic OPML #8832
  • Fix click mark as read #8817
• UI
  • Improve browser compatibility to keep mobile navigation at the bottom #8833
  • Improve support of older/simpler Web browsers/engines such as SeaMonkey #8810,
    #8811, #8813,
  • Improve Swage theme #8842
  • Rename Nord theme to Nord #8805
  • Replace GIF spinner by CSS spinner #8804, #8812
  • Various UI and style improvements: #8800, #8816,
• I18n
  • Improve Brazilian Portuguese #8846
  • Improve Dutch #8868
  • Improve German #8840
  • Improve Polish #8854
  • Improve Russian #8861
  • Improve Traditional Chinese #8849
• Misc.
  • Update dev dependencies #8858, #8864

We received some informal reports in the Microsoft Store reviews telling us that GIMP updates were deleting user data! In particular, plug-ins, themes, brushes, user settings and other add-ons were not being kept during an update from the store.

To resolve this, the updated version of GIMP from the Microsoft Store will require Windows 11 or at least Windows Server 2022 (Windows NT Build 10.0.20348.0).

Windows 10 is still supported, but only when GIMP is installed from our .exe installer.

Note that we are no longer able to support versions of Windows older than Windows 10, and can no longer support 32-bit systems running Windows.

Installing the update will prevent future data loss during upgrades.

Technical details⁠

This was being caused by the way MSIX (the format of apps distributed on Microsoft Store, GIMP included) is designed, which prefers sandboxed user data (like Flatpak and Snap). We have been trying to work with this requirement when running from MSIX, but were not successful.

So, to fix this packaging limitation, we were given the special “restricted capability” unvirtualizedResources (specifically virtualization:ExcludedDirectory), to preserve user data on %AppData%\GIMP, just as the .exe installer does. This is similar to what we do on other sandbox distributions such as Flatpak and Snap.

After the update, GIMP user data will be copied on upgrades.

The update does not affect images or other resources stored outside your GIMP folder.

How to migrate the previous user data⁠

This restricted capability is only available on Windows NT Build 10.0.20348.0 and later. So, users with older Windows versions will need to use the .exe installer.

Note: the binaries inside the .exe installer and the .msix are exactly the same.

For users who were using the MS Store version until now and are switching to the .exe installer, here are instructions in order not to lose your configuration data from the MS Store version:

1. Manually locate your config dir at %LOCALAPPDATA%\Packages\ (you may just copy-paste this string into the Windows Explorer).
2. Search a folder starting with GIMP (with random numbers and letters after that) at this location.
3. From there, navigating down to LocalCache\Roaming\ where you will find a folder named GIMP.
4. Copy this GIMP folder into %APPDATA% (again, just copy-paste %APPDATA% into the Windows Explorer to find the correct location).
   Note that maybe the folder %APPDATA%\GIMP\ already exists, in particular if you also used the .exe installer at some point. If so, it is up to you to decide whether you want to override the data already present with the ones from the MS Store GIMP.

This procedure is a one-time thing as a workaround to this exceptional issue. You won’t have to do it again in the future!

We have been trying to encourage contributors to be more present on various events, international or local. Here is where you will find someone from the GIMP team in the coming weeks:

Linux App Summit 2026⁠

The Linux App Summit (LAS) brings the global Linux community together to learn, collaborate, and help grow the Linux application ecosystem.

It happens this week-end, from May 16 to 17 in Berlin, Germany, and we will have one person attending, Michael Schumacher, one of our long term contributor, as well as member of our Committee.

Unfortunately our project did not submit a talk, but we are still interested to meet more of the desktop software ecosystem contributors and see what’s happening around us! So if you attend too and spot Michael, do not hesitate to go and speak with him. He will likely have Wilber stickers to distribute too! 😍

10th Congrès ADULLACT⁠

The Congrès ADULLACT is a conference gathering elected representatives of French local authorities, to discuss Free Software usage in the public sector.

Jehan, GIMP Maintainer, will be present there to showcase GIMP as a Community, Free Software. Obviously GIMP is already quite massively present in France, but as many Free Software, administrators and users alike may not realize how it is being developed, by whom, why and how. Nor do they know that it is being developed by a major part in Europe and more particularly in France. Since one of the two main topics this year is the digital sovereignty, this is quite a major stake in this context.

The event happens from June 4 to 5, 2026, in Montpellier, France. As one can imagine, it is a close event for elected representatives and civil servants only, so if this is your case, we hope you will show up and Jehan will be happy to discuss with you!

Jehan’s talk will be on Friday, June 5, 2026, at 14:20 (French time) and he will introduce GIMP as a “Free Software and Community”.

We hope you’ll be many to attend! (oh and Jehan as well will have Wilber stickers, even though it may less a selling point in such a conference 😋)

• Milestone

This is a major release.

Feature highlights✨:

• New sort order preferences at global, category, and feed levels
• Use feed-provided icon
• New option to hide sidebar by default
• Show time since when a feed has problems
• New functions to handle plural in internationalisation
• New cli/purge.php to apply purge policy from command line

Bug fixes highlights 🐛:

• Improve support of PHP 8.5+
• Several fixes related to searches

Security highlights 🛡:

• Limit cURL to protocols HTTP, HTTPS

UI highlights 🖼:

• Improve mobile view with multiple lines when thumbnails and summaries are shown
• Several themes improved

Extensions highlights 🧩:

• New Webhook extension for automated RSS notifications
• New LLM Classification extension to automatically tag incoming articles based on a prompt sent to an LLM

This release has been made by @Alkarex, @Inverle, @Kiblyn11, @math-GH, @rupakbajgain, @xtmd and newcomers @polybjorn, @olivluca, @tomasodehnal, @PeterVavercak, @mrtnrdl, @ale-rt, @cweiske, @rid3r45, @gabbihive, @drosell271, @Kachelkaiser, @zanivann, @nanos, @bowencool, @pe1uca, @matheusroberson, @DenuxPlays, @rlrs, @chanse-syres, @IEEE-754, @umaidshahid, @michi-onl

Full changelog:

• Features
  • New sort order preferences at global, category, and feed levels #8234
  • New filtering by date of Server modification date #8131, #8576
    • Corresponding search operator, e.g. mdate:P1D for finding articles modified by the author / server during the past day.
    • Especially useful for optimising the API synchronisation.
  • Use feed-provided icon #8633
  • New option to automatically mark new articles as read if an identical GUID already exists in the same category #8673
  • Automatic feed visibility/priority during search #8609
  • Add feed visibility filter to statistics view unread dates #8489
  • Add option to enable/disable notifications, also for PWA #8458
  • Add a form to create new user queries on the User Queries page #8623
  • Allow WebSub hub push from same private network #8450
  • Support category field in JSON feed import #8786
• Bug fixing
  • Fix wrong search toString in case of regex-looking string #8479
  • Fix article last seen date in case of feed errors #8646
  • Fix search expansion with backslash #8497
  • Fix user query parsing #8543
  • Fix search in shared user queries #8789
  • Fix redirect to wrong view after mark as read in reader and global views #8552
  • Fix SQLite paging when sorting by article length #8594
  • Fix change sorting during paging #8688
  • Fix SQL keyset pagination when sorting by category name #8597
  • Fix SQL duplicates in the user labels when sorting randomly #8626
  • Fix wrong error redirect in subscription management #8625
  • Fix do not include hidden feeds when counting total number of unread articles #8715
  • Update user modify date when changing extensions UserJS / UserCSS #8607
  • Non-strict OPML export #eedefb
• Security
  • Limit cURL to protocols HTTP, HTTPS #8713
  • Better sanitise favicon URLs #8714
  • New setting for <iframe> referrer allow list #8672
  • Fix email validation and allow error page for unverified email users #8582
  • Add allowfullscreen to <iframe> #8467
  • Rewrite Set-Cookie using native PHP support of SameSite #8447, #8778
    • Sanitize lifetime of session cookies from session.cookie-lifetime in php.ini
  • Update to <meta name="referrer" content="no-referrer" /> from deprecated never #8725
  • Preventive measure against search ingestion #8777
• UI
  • New option to hide sidebar by default #8528
  • Improve mobile view with multiple lines when thumbnails and summaries are shown #8631
  • New option to disable unread counter in tab title and favicon #8728
  • Show time since when a feed has problems #8670
  • Improve add feed UI #8683
  • Improve slider behaviour when using navigate back button #8496, #8524
  • Improve consistency of slider behaviour after submitting form #8612
  • Create dynamic favicons from SVG instead of PNG canvas #8577, #8588
  • Only display scrollbar everywhere if there's an overflow (especially for Chromium) #8542
  • Fix CSS padding of .content pre code #8620
  • Fix wrong navigation buttons layout on Chromium #8606
  • Fix don’t mark as read if middle click is outside of article link #8553
  • More robust JS #8595
  • Fix sidebar slide animation at narrow viewports #8747
  • Visually dim disabled users in user management table #8768
  • Improve multiple UI themes #8711, #8732,
    #8733, #8734, #8735,
    #8736, #8737, #8738,
    #8739, #8743, #8746,
    #8749, #8761, #8781,
    #8784, #8785
  • Various UI and style improvements: #8537, #8538,
    #8541, #8624, #8731,
    #8774
• Deployment
  • Also push Docker images to GitHub registry #8669
  • Improve support of PHP 8.5+ using Pdo\Mysql #8526
  • Add support for Podman in Makefile #8456
  • Re-add database status in installation check #8510
  • Docker / CLI: Allow chown/chmod to fail with warning #8635
• Extensions
  • New Webhook extension for automated RSS notifications Extensions#456
  • New LLM Classification extension to automatically tag incoming articles based on a prompt sent to an LLM Extensions#458
  • New extension methods to get typed configuration values #8696
  • New hook: Minz_HookType::ActionExecute #8599, #8603
  • New hook to modify the list of feeds to actualize #8655, #8675
  • Allow passing Minz_HookType as hook name in registerHook() #8600
  • Return more info and status from httpGet() #8700
  • Make httpGet() cache nullable #8705
  • Allow extensions’ configuration UI to use select-input-changer JavaScript helper #8721
• SimplePie
  • Bump upstream #8628, simplepie#71
  • New function get_icon_url() for feed favicon simplepie#974
  • Fix Undefined array key in get_thumbnail() #8634, simplepie#970
  • Fix int types for enclosures #8702, simplepie#975
  • Fix HTTPS headers given to SimplePie, e.g. for some HTTP/2 cases #8742
• CLI
  • New cli/purge.php to apply purge policy #8740
• I18n
  • CLI validate language directory names #8767
  • New functions to handle plural, and new timeago() #8670
  • Improve German #8491, #8557, #8689,
    #8704
  • Improve Italian #8517, #8519, #8554,
    #8555, #8556, #8566
  • Improve Latvian #6553
  • Improve Polish #8536
  • Improve Portuguese #8649
  • Improve Simplified Chinese #8474, #8475, #8476
  • Improve Traditional Chinese #8709, #8716, #8723,
    #8730, #8748
  • Improve Spanish #8572
• Misc.
  • Initial conventions for AI agents and humans: AGENTS.md, SKILLS.md, instructions.md #8478
  • Update to CSSXPath 1.5.0 #8642
  • Update to PHPMailer 7.0.2 #8483
  • SQL improve PHP syntax uniformity #8604
  • Trim SQL whitespace before parenthesis #8522
  • Improve PHP code #8627, #8644, #8753,
    #8697
  • Add dev legacy rules PHPCS 3 #8645
  • Update dev dependencies #8469, #8480, #8499,
    #8545, #8546, #8547,
    #8617, #8638, #8660,
    #8661, #8662, #8663,
    #8664, #8665, #8666,
    #8667, #8668, #8685,
    #8752, #8754, #8755,
    #8756, #8757, #8758,
    #8772, #8798