Skip to content

Friday, 16 October 2026

Kdenlive development for the 26.12 release is very active, and we would like to request some feedback regarding two of the upcoming features.

Title Editor

One of the feature is related to the title editor. Our title editor has always been functional but rather limited. A new feature was recently implemented by klg that allows having different font styles in a single text block.

Note that several other great improvements were made by other contributors, like: Undo/redo support, implemented by Jaimukund Bhan, and Copy/paste support, implemented by chocolate image.

Relative paths for projects

The second large change is the switch to relative paths in project files. This means that if your videos or images are in the same folder as the project file (or a subfolder), you can easily move your work to another drive and reopen it without issue. This should really improve the experience for people editing projects on several computers, or switching between different operating systems. And this should also fix issues for teams doing collaborative work with projects on network drives or removable drives.

How you can help

We did some regression testing and have some unit tests for both these new features, of course, but some real-life scenarios may not be covered, which is why having feedback from testers is very valuable to us. Download the binaries from the link below and use this development version (26.11.70) to test the steps as described below, then report your findings in the comments section.

To test the title editor changes

The goal is to ensure existing titles display exactly as before and that there are no changes to the position or attributes of the titles.

  1. Open your project files, ensure your existing titles display and render correctly.
  2. Save your project to a new file, try to reopen and ensure it still displays and renders fine.

To test the relative paths changes

The goal is to ensure that all files in existing projects are correctly found, that you can render, save, open again, and all files are still correctly found.

  1. Open your projects, ensure that all files appear correctly.
  2. Check in the project settings that the project folder is correctly detected (default location, parent folder, or custom folder).
  3. Check that rendering works correctly (no missing images ore videos).
  4. Save the project with a new name (Save As), then repeat steps 1 thru 3.
  5. If you sometimes edit from multiple computers, save the project under a new name and ensure that you can open and save the project file correctly from your different computers.

Download

Linux Appimage can be downloaded from Kdenlive's unstable download folder. Make it executable from your file manager before running it.

Windows installer can be downloded from Kdenlive's unstable download folder.

Development Flatpak can be installed from KDE's cdn server.

Thursday, 15 October 2026

For more than 20 years, I’ve been part of the KDE community, one of the largest and most impactful Free and Open Source software community world-wide. Yesterday, KDE turned 30 and this went accompanied with the premiere of the KDE documentary.
As former release manager, Plasma core developer and KDE e.V. board member, I’ve also been interviewed. A fairly prominent NPC role went out to Skippie, my cat.

Lately, I have been back into Free Software development, working on two apps that are closely related to hobbies of mine. Watch this space for news! Something nice has been cooking!

Tagoross published its first open content package, one day after KDE turned thirty. Two good days in a row Yesterday was a great day for me. KDE turned thirty years old. The KDE documentary, published to celebrate the anniversary, was delightful. Today is no less special for me. The first Tagoross package This morning, Tagoross … Continue reading Tagoross releases its first open content package on AI openness

We are happy to announce the release of Qt Creator 21 Beta2.

Wednesday, 14 October 2026

When I joined KDE in 1999 I already thought of it as a mature project. I used the KDE desktop every day, and I was delighted with what it could do and how it felt. I had no idea that this would be one of the most impactful decisions of my life, or where it would lead me.

Today we are celebrating the 30th anniversary of the original announcement of KDE. The project is still alive and kicking. I still use it every day, just like millions of other people. Not only because it's great software, but because of the values it embodies.

KDE stands for freedom and being able to shape your own destiny. As the KDE vision says: "A world in which everyone has control over their digital life and enjoys freedom and privacy." While I originally joined for the technology, this is what made me stay.

One of my favorite pictures illustrating the spirit of the community is the group picture of Akademy in Dublin in 2006. Brilliant people having fun working towards a shared purpose of digital freedom.

KDE gets a wonderful present for its birthday. The KDE documentary is premiering today. It tells the story of the founding, the rapid early development, and the license conflicts. How it became a solid product used by many people, and then put it all at risk with KDE 4. How we learned from that and turned it into this extremely resilient and lively community it still is today. I'm happy I could contribute to this story, and that I'm one of the people telling it in the documentary.

For me, KDE shaped my career and my life, and gave me the opportunity to grow and learn. It led to things I would never have expected when I started: my code running on millions of computers, talking to hundreds of developers at conferences, sitting at the negotiation table with Nokia in Helsinki, consulting as an expert in the German parliament. And much more.

Today, KDE is maybe stronger than ever. We reached a lot of new users with the Steam Deck. The Sovereign Tech Fund is investing more than a million euros in KDE. With the strategic goals the community set this year, we are addressing enterprise, documentation, and styling. It shows how much the project has matured, beyond what I could ever have imagined. It also shows in its contributors. While contributors leave over time, new generations come in every year and keep the community growing over the long run, combining stability and rejuvenation.

I'm proud and grateful. Proud of what the KDE community achieved. Grateful that I could be part of this amazing group of people. A team nobody could have hired.

Happy birthday, KDE.

So... a bit of news. 🙂

KDAB have just published a video featuring me talking about design, QML, and something I keep coming back to: what happens when the tools we use to make software become more capable, while the interfaces we build with them seem to get increasingly predictable?

This started with me playing around with QML, trying to see how far I could push some ideas about the look and behaviour of an interface.

Things that are perhaps a little excessive, things that might be annoying in everyday use, things that are difficult to justify in a design review.
The sort of things you might want to try before somebody with more of a brain than you explains why you shouldn't. 🙂

And its something I have been thinking about for some time, the place we leave for this kind of work, particularly in open source.

OSS has a rather unusual relationship with creativity. We can inspect how things work, modify them, share our experiments, and build on each other's work.
There is room for someone to follow an idea simply because it interests them, it does not require a market research, there is no need to demonstrate that it will appeal to the largest possible audience before writing the first line of code or in my case drawing the first squigly line in inkscape.



And yet, sometimes our projects can be surprisingly cautious about appearance.
We globaly spend a great deal of effort making software coherent and predictable, which is understandable and a good thing when you have to maintain it for years and support a wide range of users.
But those concerns can also make it difficult to explore alternatives. The existing conventions gradually become the boundaries of what we consider reasonable.
Trust me I was that guy shooting down what I believed were bad ideas. because of all the work that it would create, or because it was just 2 insane etc....



BUT

Now as a designer, I find that a little frustrating. Especially when the technology itself offers so many possibilities. I don't expect every application to become an animated art installation, and I certainly don't want every interaction to demand my attention (expect the ones I create ;)) . But I'd like to see more people curious about what an interface could be, rather than starting from what an interface is supposed to look like.



Which brings me to OxygenLabs.

We started a new repository under KDE in the playground area, intended as a space for exploring visual ideas and seeing where they lead.

https://invent.kde.org/libraries/oxygen-labs.git



What interests us is the willingness to put care into visual details, to explore a particular character or mood, and to take the appearance of software seriously enough to question the usual answers.

We would like OxygenLabs to give that process somewhere to happen. Not every piece of work needs to arrive as a finished feature, actually the opposite and not every experiment needs to graduate into a product. Sometimes it is useful just to make something, live with it for a while, and find out what you learn from the experience.



For now it just has 2 things I was playing with, one of them a request people have for a long time to be able on only use colourful icons . on the plasma panel via giving the icons KCM area a specific configure option per theme...



Anyway, that's the thinking behind it. The video goes into some of the questions that led me here, and OxygenLabs is a small, practical way of exploring them.


Have a look at both, and let me know what you think. I'm curious to see what comes out of this. 🙂



P.S. we also have a "new" site https://oxygen-design.org/

Tuesday, 13 October 2026

The second maintenance release of the 26.08 series is out with the usual batch of stability fixes and workflow improvements. Highlights include improved project handling and ability to set the frame count to start at 1 in the Dynamic Text filter which is useful for animation workflows. This release also fixes several issues in proxy clips, titles, and audio levels.

Kdenlive needs your support

Our small team has been working for years to build an intuitive open source video editor that does not track you, does not use your data, and respects your privacy. However, to ensure a proper development requires resources, so please consider a donation if you enjoy using Kdenlive - even small amounts can make a big difference.

For the full changelog continue reading on kdenlive.org.

Monday, 12 October 2026

This year’s edition of International Calligraphy Festival Keralam was yet another great experience, consisting of workshops, demonstrations and talks surrounding calligraphy & typography, much like the last time. Eminent calligraphers of about a dozen scripts shared their expertise and experience.

Pictures of a sample collection of the calligraphy works at the exhibition below.

For my talk, I presented the historical evolution of Malayalam script from rock inscriptions to the digital age, and how the vigilant volunteer community reclaimed the script with its rich conjuncts and conjoined reph/matra shapes, and made all the foundational digital technologies openly available for public good.

The video recording of the talk is available.

Many type designers, companies and enthusiasts were also at the 4-day programme, enabling lot of productive hallway talks as well. A recurring question was the usage of Open Font License, which I hope to have helped to clarify.

The most useful feedback after the talk came from a good friend, who pointed that my slides didn’t do enough justice to the body of work we’ve done (particularly as open-source); and helped me walk through some possible improvements. I did make some of those changes, and the slides (created using TeX) are made available.

Sunday, 11 October 2026

Welcome to the latest edition of This Quarter in KDE Digital Sovereignty!

This blog series covers the work done throughout KDE’s software stack that’s funded by the investment KDE received earlier this year from Germany’s Sovereign Tech Agency.

Commissioned work on a variety of projects has been done by KDE contributors working for KDE e.V. itself, as well as the Techpaladin Software, enioka Haute Couture, and MachineSoul companies.

This post will cover the work done in the third quarter (Q3) of 2026. Let’s get into it!

Quality assurance and testing

QA work continued in Q3, this time largely to polish and improve upon the work that was landed in Q2.

On the KDE Linux side, the OpenQA system received a lot of work both to maintain it, and also to reduce ongoing future maintenance needs, as well as adding more tests. Some highlights include:

On the PIM side, the end-to-end tests continue to pay dividends. Lots of effort went into fixing the issues they uncovered. This included issues like:

This allowed us to remove all the expected fail marks which were still present on some of the tests.

With this QA safety net in place, we’ve been working on landing long-needed improvements around DAV support. For instance, it’s been migrated away from KIO to use QNetworkAccessManager leading to a large performance boost. Further performance enhancement is expected from the work to port the DAV Akonadi resource to ObserverV3 allowing batching of some operations.

IMAP4rev2 and WebDAV-Push

The work on QRESYNC support in the IMAP Akonadi resource has been completed, providing a very nice boost to email syncing by making it faster, and drastically reducing the network bandwidth used for a sync. This pretty much concluded the work on the IMAP4rev2 upgrade of our stack.

Focus then shifted to WebDAV-Push support for DAV Akonadi resources. More of the protocol is getting implemented like support of the “Don’t Notify” header to avoid getting notified of our own changes. The DavPush notification subscription code path has also been completed.

This allows us to move to the next step which is integration of the various components involved and the addition of new end-to-end tests to validate the whole chain.

An interesting side effect of this work has been the need to implement support for DAV sync-tokens, which is supported by most servers. This will simplify calendar syncs even if your server doesn’t support WebDAV-Push. We expect it to improve the syncing of calendars in a similar way to the improvements with emails we’ve experienced with QRESYNC.

This work is not completed yet, with a few merge requests still in flight. But expect next year’s release to fly for syncing IMAP and DAV.

Security

Plasma’s security infrastructure received a great deal of work in Q3. Much of it is non-flashy, but rather intended to shore up and modernize the foundations. As part of that work, Plasma’s lock screen gained a more flexible system that supports multiple authentication methods being configured and made available in different combinations:

Plasma lock screen showing multiple authenticators

Work is now ongoing to apply this feature to Plasma Login Manager, and share more security infrastructure between them.

Recoverability

Work began on adding a “safe mode” to Plasma, wherein you’ll be able to log into a dedicated troubleshooting environment that offers tools to help you get back to a working session.

This work is all in progress, with parts expected to start landing in Q4.

Network share handling

KDE’s network share handling improved in two significant ways in Q3. First, network FUSE mounts created by kio-fuse will now be automatically mounted if needed when you open a file that was previously accessed from a kio-fuse mount path. And those paths are now stable across logins, meaning that paths involving kio-fuse mounts also remain accessible across logins.

Work also began to remove blocking file access calls in KDE software, so that network shares accessed via mounts (FUSE or otherwise) are less likely to cause freezes and hangs — starting with Dolphin.

Data integrity

Q3 also saw a significant amount work on the topic of data integrity, from multiple angles.

First, the kio-snapshot service built in Q2 received a large amount of technical and user interface polish to make it a practical and reliable tool for users whose systems take Btrfs snapshots.

That tool was then integrated into KDE Linux, along with the Snapper Btrfs shapshotting system, thereby providing automatic user-level file snapshots by default. You can read a bit more about this in the August 2026 KDE Linux blog post.

The Baloo file indexing system was also made aware of Btrfs snapshots — specifically, how to not index them!

And because the concept of “free space” can be somewhat fuzzy on snapshotted filesystems, work is ongoing to surface information in more comprehensible ways, starting with KDE’s Filelight app.

Finally, the Kup backup system — which was previously released independently — was made a part of Plasma, so it will now see regular releases on the same schedule as Plasma itself. As a prerequisite to this, Kup was fully ported to Qt 6 and its widget received some more polish. Kup was also configured to avoid backing up large Flatpak apps and runtimes installed at the user level by default. And in the process, a longstanding bug afflicting multiple System Tray widgets was fixed.

Configuration management

The topic of strengthening KDE’s configuration management continued in Q3. First, even more apps and parts of Plasma were ported to use KConfigXT, and some had their settings refined to move volatile state data out of their configuration files.

Leveraging this expanded use of KConfigXT, the team created a GUI config editor app that offers system administrators the ability to graphically visualize and change configuration options. This app is still a work in progress, but shows the promise and potential of fully adopting schema-based configuration.

Account Autoconfig

On the PIM side, work to ease setup is moving towards exposing the new facilities to the user. Indeed, the KAccountAutoconfig library is almost feature-complete with one patch still to go through review.

Once it’s merged, we’ll start the process of moving the library to KDE Frameworks, and then begin integrating it into KOnlineAccounts and the individual PIM apps. We already have a prototype port of kmail-account-wizard to use this new library — a good first use of this library to prove it works properly.

Kontact Flatpak

Last but not least, work on the Kontact Flatpak integration with Plasma has started, and we’re currently scoping out requirements. The dependency chain between Plasma and the PIM stack will be completely reworked: it will be D-Bus based, and we’re working on defining the interfaces.

Attending Akademy 2026 definitely helped, as we got interesting input during the PIM BoF on the direction to take. This will lead to options which might benefit more contexts than the desktop, and so hopefully one day help Plasma Mobile as well.

Stay tuned for more details when the implementation work will be underway.


Looking forward

User-facing work has begun! We anticipate that this will continue in Q4 of 2026. And we’re very grateful for the Sovereign Tech Agency’s investment in KDE that made this possible!

Saturday, 10 October 2026

intro

Great news for the community! The integration of QML Quick Editor into Qt Creator is now 100% complete. The plugin is officially available, bringing native workflow integration directly to your development environment. Give it a try, and let us know what you think!

Features:

Designed as an all-in-one QML code editor, this extension allows you to quickly prototype and test QML snippets without the overhead of creating a full project. Simply edit your code and preview the visual output instantly inside Qt Creator—speeding up your UI experimentation and debugging workflow.