First maintenance release of the 25.08 series is out continuing the focus on stability and polish with many fixes for crashes and regressions as well as user interface and usability improvements.
Some packaging issues caused a small delay for this release announcement, sorry for the inconvenience. Thanks to all the people who help make Kdenlive more stable by reporting bugs, providing patches or sending constructive feedback.
For the full changelog continue reading on kdenlive.org.
You find a selection of improvements and fixes below. Please have a look at our change log for more detailed information.
Symless is the latest company to officially help fund KDE.
Symless develops Synergy, an open source solution that allows users to share a keyboard, mouse, and clipboard across several computers at the same time, without extra hardware and regardless of whether they are using Linux, Windows, macOS, or a mix of all of the above.
“Becoming a Supporting Member of KDE is a natural step for us", stated the Synergy team representative. "Synergy is heavily rooted in open source, and we want to give back to the community that made it possible. By supporting KDE financially and contributing to upstream projects like Deskflow, we’re helping ensure open source software remains sustainable for both enthusiasts and enterprises”.
“It’s exciting to see organisations in our ecosystem participate alongside KDE and Plasma in creating next-generation workflows for everyone", says Aleix Pol, president of KDE e.V.. "We’re glad to welcome Symless as a KDE Supporting Member and value their continued commitment to Open Source.”
Symless joins the other supporters, KDAB, basysKom, Haute Couture Enioka who help fund free open source software and development through KDE e.V.
Over 24 years ago, our kwrite-devel@kde.org mailing list started with:
From: Scott Manson
To: kwrite-devel@max.tat.physik.uni-tuebingen.de
Date: Wednesday, February 21st, 2001 at 21:47
Subject: [Kwrite-devel] I just wanted to be the first to post here )
Welcome to kwrite-devel
I hope this is an active list and we can attract some more developers Anyone have any ideas on coding style,enhancements problems please feel free to post your questions/comments here.
or, depending which mail arrived faster in your inbox:
From: Waldo Bastian
Date: Wednesday, February 21st, 2001 at 21:50
Subject: [Kwrite-devel] Welcome to this mailinglist.
Hello,
Welcome to the kwrite development mailinglist. *test*test*
Cheers, Waldo
Like the first mail wanted, that list was very active for a long period of time.
The initial posters no longer are active in the project, but some people like me still stick around even after more than two decades.
A lot of important design decisions were discussed on the mailing list and many user questions got answered.
The list traffic slowed down more and more over the last years even as the actual amount of contributions (and presumable the user base) did increase.
Reasons are for sure that for development, we use mostly our KDE GitLab instance for communication. It is just that easier to couple discussions with code there and link development issues to merge requests or commits. I can not remember any serious discussion on larger development topics outside our GitLab in the last years.
For users I assume mailing lists are just too arcane today. Perhaps that is a misconception I have, but at least from most people I know in real life, most of the online support questions went of to either websites or random other channels. Some people survive without any mail account beside the one needed to create some online accounts or install thei mobile phone.
I need to moderate away at least 10 to 100 spam mails for any real mail on the list, that is just a not needed overhead nobody should waste time with.
Therefore in the near future we will close that list, it will not get a 25 years birthday party :-)
I already updated our documentation and web site to point to the current contact points.
In short:
Bug reports: like before - our KDE Bugzilla instance
User questions web site: use the Kate section on the KDE discourse server
User & developer questions chat: join our Kate Matrix channel
Development discussions and code: show up at our KDE GitLab instance
Many Kate developers and users are active on random social media and Co., too. But the above mentioned places are the ones that should be preferred.
A matching thread for this can be found on r/KDE.
Like every year, one of the highlights is Akademy! This time we were in Berlin, making it quite easy to get there from Hamburg:) The weather was surprisingly nice, especially when heading out in the evening to try lots of different restaurants. And of course - since being in Berlin - you gotta try a local Döner there :D.
One talk I was particularly surprised about was Saturday’s keynote “Open by Design: How Governments Can Lead the Shift to Digital Sovereignty” by Alexander Rosenthal.
Besides the information about OpenSource-Software being used on different levels of federal/state/local, the aspects of OpenData.
This made me realize that software is not the only thing one should focus on being open.
Also, the huge amount of memes in the slides made the talk super refreshing and a nice start into Akademy!
Nate’s talk “Minding the Big Picture: Opportunity From Chaos” also fit this topic. OpenSource can provide a stable foundation and reduced dependence on individual companies.
My main development focus and also the most frequent topic of the blog is the Clazy project. Akademy is a good occasion to tell other people about it.
So I took the occasion and held a fast-track talk about Clazy to tell how awesome and useful it is.
It was also quite good to get people talking about it and share their ideas/problems.
I also did a decent amount of coding on Clazy. This included a request from aacid about Clazy not working properly with a Qt variant
that is build into a specific namespace. This was quite the rabbithole, but I managed to get the passing tests from 50% to 90%.
The last few edgecases are not as relevant if most of Clazy works properly.
For the use-arrow-operator-instead-of-data a false-positive is fixed where the check complains if you do a .data() call and then cast the pointer.
This is in most cases needed, if not, clang-tidy should warn about unneeded casts.
Finally, fixits for detaching-temporary and detaching-member are more reliable when multiple calls are chained.
The biggest surprise though came at the Akademy awards. I am very honored to have received one, this left me quite speechless.
Me finally catching some words after getting the Award <3
This also means I am responsible for choosing the person for next year’s award. So you better get busy doing cool stuff 😎👀.
Finally, I want to thank everyone who helped organize Akademy and made it as awesome as it was!
Kaidan 0.13.0 is out now! And it comes with a bunch of shiny new features.
Most of the work has been funded by NLnet via NGI Zero Entrust with public money provided by the European Commission.
Kaidan supports the simultaneous usage of multiple accounts now. Imagine you could use the same chat app at work and with your friends. All your favorite and accustomed features would always be accessible without switching apps. It is possible with XMPP and finally with Kaidan too!
In order to quickly distinguish the account a chat belongs to, there is a small avatar of the corresponding account in the corner of a chat’s avatar. Furthermore, Kaidan makes sure that you do not accidentally add a new contact to the wrong account. That is achieved by selecting the account before you enter the contact’s chat address or scan their QR code. The same applies to the group chat actions.
The account passwords are stored in the device’s password manager. You do not need to keep passwords in your mind. Instead, you can use random ones. They are securely stored in a central place.
If you already read the latest messages from a contact but do not have time now to respond, you can simply mark them. A separate counter is shown for the marked messages. Take your time and come back to those messages later. You will not forget to reply anymore!
You can forward messages from one chat to another. After clicking the corresponding context menu button, you can choose a chat to forward the message to. By default, only the chats of the current account are listed to make it as simple as possible for you. But you are able to list chats of other accounts as well.
Once you selected a chat, the message is added to its input field. You can directly send it or adjust it beforehand.
There are several other improvements. Have a look at the following changelog for more details.
Features:
Bugfixes:
Notes:
Or install Kaidan for your distribution:
This post is to celebrate a few things despite the events that are clouding our feelings. 😠
Another thing to not celebrate is the slaughtering by Sourceforge of my developer web site, which they are calling "sunsetting", by October. I've already migrated it.
On the other, brighter hand, I'm celebrating this week La Mercè, which is the local festivity of Barcelona.
You may download it from GitHub (source code and APK), or you may get it from the IzzyOnDroid repository which is available in the F-Droid app, but also on Neo-Store, Droid-ify, and the unofficial IzzyOnDroid app.
If you already have the F-Droid app, you only need to add the IzzyOnDroid repository in Settings>Repositories and install it today, or you may prefer to use the official F-Droid repo.
I would like to add to the celebration a video live streaming concerto, but I am too lazy and odd playing for that. Better use this wonderful rendering of the Tchaikovsky Violin concerto by TwoSet Violin, with Brett Yang playing the soloist and Eddy Chen the rest of the orchestra. Enjoy!
A week ago I attended the 2025 edition of KDE Akademy in Berlin, Germany.
Akademy is a week of hanging out with old and new friends that also happens to have two days of presentations and multiple days of BoFs attached to it.
It was slightly weird hearing from public administration/public agencies in their talks how important digital sovereignty and public funding for FOSS are, it’s not like we haven’t been telling them for years and it’s them rather than us who are in a position to really change this. Anyway, I’d consider that a sign of success.
You’ll find a couple of reports about Akademy on Planet KDE already, I’ll focus on a few things I was involved in below.
On Saturday I presented our work on free and open infrastructure for receiving emergency and weather alerts. My main goal was to collect input on how this should eventually be integrated client-side.
The plan there is now to have a module in Plasma’s System Settings to manage areas of interest and keep the current stand-alone app prototype as the thing that opens when receiving push notifications. We can then gradually expand that to have more things (such as Itinerary) manage relevant areas.
With more people installing the current prototype and the venue Wi-Fi being a bit flaky at times we also managed to identify an issue in our current push notification infrastructure, namely an unfortunate interaction between KDE’s UnifiedPush server and Qt’s broken HTTP2 implementation in 6.9.1.
Push-based alerts weren’t the only thing though, we also got a chance to test cell broadcast alerts during the week. Since last year the Linux Mobile stack has made big improvements there, receiving cell broadcasts now just works, including wakeup from suspend and Unicode decoding. We now merely miss Plasma Mobile UI for this.
On Thursday we then got a chance to test both of this in action, as Akademy once more coincided with Germany’s nation-wide alert infrastructure test.
This worked flawlessly both for cell broadcasts and push notification, for the latter easily within the one minute latency the system is designed for.
And while my own (non-)travel to Akademy was very boring this year, others did provide ideas, test cases and merge requests:
A challenge when working on the travel document extractor is that this often requires access to actual booking documents for development and testing. Those are donated by people, and full of their personal information. The current historically grown “trust me” approach without documented rules is far from ideal, and makes the people holding those documents single points of failures.
There had been several ideas already on how to improve this, but what I had missed until discussions during Akademy is that e.g. the Poppler and Okular team has exactly the same problem.
So rather than coming up with something for just Itinerary we’ll now look at a more general solution for this. Probably worth its own post eventually.
While we have a cross-platform API for showing notifications we lack a way for application to show the platform-specific notification configuration dialog for themselves. That’s relevant on platforms where the presentation of notifications is controlled by the platform rather than the app itself (such as KDE’s Plasma or Android).
This isn’t particularly hard to implement when running in a Plasma host system, but it’s a bit more challenging for applications inside a Flatpak containment:
toscalix
alex1701c
@vkrause:kde.orgnotifyrc file, either by the Flatpak exporting that
or by Plasma looking into installed Flatpaks for this.kcmshell with the right arguments, inside a Flatpak we’d probably need some kind of URL scheme
for this.I’d finally like to get the moving of PIM libraries back to KDE Frameworks going again. Being under Framework’s API stability guarantees would simplify a few things.
For this we now at least have a basic agreement that this should be done and what API details should be reviewed and possibly cleaned up beforehand. The biggest remaining task however is porting to the new API documentation infrastructure, which we’ll have to do for all other non-Frameworks libraries as well. Help very much welcome.
There were also a couple of discussions around our own distribution of applications. There’s still some historic artifacts like external distributors having a one week lead time for getting access to release tarballs, while our own packaging can only start at the moment of the public announcement (and then takes a couple of days).
Albert kindly showed me how the automatic update monitoring infrastructure for Flatpak works. I could directly apply that for the Itinerary Flatpak (which thus will eventually have all features enabled on Flathub as well). Even more interesting though was discussing how that could be integrated with Craft so we can use that for our packages on all other platforms as well.
And finally I learned how I could log into Flathub to see validation errors for apps I’m responsible for. That’s very useful as so far I only hear about those by chance in random pastebins shared in unrelated chat channels. Well, in theory at least, as that doesn’t seem to actually work for my account unfortunately.
Akademy was just the start into the autumn conference season for me, with the Open Transport Community Conference, the CAP Implementation Workshop 2025 and 39C3 still to come, next to the KDE PIM sprint in Paris and an OSM Hack Weekend or two.
Welcome to a new issue of This Week in Plasma!
This week we finalized the set of features and major changes in Plasma 6.5, and released the first beta. I’d encourage everyone to test it out! One of the best ways these days is via KDE Linux. Many other distros also offer “unstable” KDE repos and the like. Please do test. For the next month, the Plasma team will be focusing on bug-fixing, so let us know what the bugs are!
This week, the last few features landed, and we began The Great Plasma 6.5 Bug-Fix-a-Palooza:
Implemented support for text insertion point tracking in the Zoom effect on Wayland. (Vlad Zahorodnii, link)
You can now set up a VPN with the “Fortigate” vendor. (Roland Tapken, link)
KRunner is now smarter about performing mathematical calculations when given numbers with group separators. (Han Young, link)
Implemented more improvements to make Wayland window activation/raising work better. (Xaver Hugl, link)
You can now right-click the list items of many System Tray widgets to access their extra actions without having to expand them first. (Kai Uwe Broulik, link)
Improved the way Discover communicates the status of Flatpak installations and updates. (Aleix Pol Gonzalez, link)
Improved the way screen readers describe actions and keyboard shortcuts on System Settings’ Shortcuts And Autostart pages. (Christoph Wolk, link 1 and link 2)
The Kicker Application Menu widget now shows a placeholder message when you search for something and get no results. (Christoph Wolk, link)
Removed the combined meta-transaction in Discover’s transactions view, because it wasn’t necessary, and confused people when there was only one transaction happening. (Aleix Pol Gonzalez, link)
The desktop bar at the top of KWin’s Overview effect now fades in and out nicely. (Tony Wasserka, link)
Plasma Vaults now consistently uses the terms “lock” and “unlock” everywhere. (Nate Graham, link)
Fixed an issue that prevented the Breeze GTK style from being activated by default in Plasma, as intended. (Fabian Vogt, link)
Fixed some issues with printer ink levels being shown unnecessarily, or hidden when useful. (Mike Noe, link 1 and link 2)
Fixed an issue that could cause Plasma to get stuck at high CPU usage when you invoked its scripting system in a very specific way. (Albert Astals Cid, link)
Fixed an issue that could cause input methods to stop working with X11 apps on Wayland. (Xuetian Weng, link)
Drag-and-drop now works with a stylus on Wayland. (Vlad Zahorodnii, link)
Fixed two issues that broke the ability to load certificates for 802.1X networks and view VPN server logs. (Ilia Kats, link 1 and link 2)
Fixed some issues in the DrKonqi bug reporting wizard that caused UI elements to overflow at small window sizes or with languages with long words like Russian and German. (Nate Graham, link)
Clicking on a disabled zoom button on the map present on the Night Color page in System Settings (which moves to the Day/Night Cycle page in Plasma 6.5) no longer inappropriately moves the current location marker to be under the button. (Vlad Zahorodnii, link)
Fixed an issue that caused some Flatpak apps to not display the right icons on System Settings’ Flatpak Application Permissions page. (David Redondo, link)
Fixed an issue that could cause blinking graphical artifacts at the edges of screens with floating panels when using certain fractional scale factors. (Xaver Hugl, link)
When connecting to a Plasma system using remote desktop, typing text now always inserts letters from the keys you typed, rather than respecting the keyboard layout on the remote machine, because that would potentially insert different letters from the ones you typed. (Nicolas Fella, link)
When configuring the System Monitor apps and widgets, the spinboxes that let you enter degrees are a lot less janky now. (Arjen Hiemstra, link)
KRunner’s popup no longer overflows beyond the bottom edge of the screen when there are a ton of results — especially when it’s configured to appear in the center of the screen; now it scrolls as needed. (Oliver Geer, link)
Launching apps using Konsole no longer causes their CPU and memory usage in the System Monitor app and widgets to be attributed to Konsole. (Christoph Cullmann, link)
Fixed two somewhat common Plasma crashes caused by improper thread use the SVG rendering pipeline. (David Edmundson, link 1 and link 2)
Created a little command-line kwindowprop tool that works in much the same way that the X11-specific xprop tool did: you run it, click on a window, and then it prints information about that window. (David Redondo, link)
The last-used virtual desktop and the size of portal-based open/save dialogs are now saved in their respective state configs, not their settings configs. (Nicolas Fella, link 1 and link 2)
The command-line kscreen-doctor tool now reports refresh rates correctly, with two digits of precision for decimal values. (Liu Jie, link)
Implemented support for notifications about “graphics resets”, which Plasma and other Qt-based apps (but not KWin, which already supports this) will be able to use to behave more sensibly when graphics cards don’t behave so sensibly. (David Edmundson and Vlad Zahorodnii, link)
KDE has become important in the world, and your time and contributions have helped us get there. As we grow, we need your support to keep KDE sustainable.
You can help KDE by becoming an active community member and getting involved somehow. Each contributor makes a huge difference in KDE — you are not a number or a cog in a machine! You don’t have to be a programmer, either; many other opportunities exist, too.
You can also help us by making a donation! A monetary contribution of any size will help us cover operational costs, salaries, travel expenses for contributors, and in general just keep KDE bringing Free Software to the world.
To get a new Plasma feature or a bugfix mentioned here, feel free to push a commit to the relevant merge request on invent.kde.org.
