Planet KDE | English

Krita 5.3.2.1 Released!

Krita News — Tue, 02 Jun 2026 00:00:00 +0000

Hot on the heels of Krita 5.3.2, we're releasing Krita 5.3.2.1. 5.3.2 had a bug with the layer docker that was very pervasive, and could cause anything from unsynced layers to crashes to groups not behaving as they should. 5.3.2.1 fixes this. Furthermore, we also had some issues where the Windows packages weren't signed. This too should now be fixed.

[!WARNING] We consider Krita 5.3.2.1 suitable for productive work; 6.0.2.1 is, because of the many changes from Qt5 to Qt6 more experimental.

Download 5.3.2.1

Windows

If you're using the portable zip files, just open the zip file in Explorer and drag the folder somewhere convenient, then double-click on the Krita icon in the folder. This will not impact an installed version of Krita, though it will share your settings and custom resources with your regular installed version of Krita. For reporting crashes, also get the debug symbols folder.

[!NOTE] We are no longer making 32-bit Windows builds.

64 bits Windows Installer: krita-x64-5.3.2.1-setup.exe
Portable 64 bits Windows: krita-x64-5.3.2.1.zip
Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

64 bits Linux: krita-5.3.2.1-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

MacOS disk image: krita-5.3.2.1-signed.dmg

Android

Krita on Android is still beta; tablets only.

Source code

Sources are the same as 6.0.2.1

md5sum

For all downloads, visit https://download.kde.org/stable/krita/5.3.2.1/ and click on "Details" to get the hashes.

Key

See the 6.0.2.1 key section.

Download 6.0.2.1

Windows

[!NOTE] We are no longer making 32-bit Windows builds.

64 bits Windows Installer: krita-x64-6.0.2.1-setup.exe
Portable 64 bits Windows: krita-x64-6.0.2.1.zip
Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

64 bits Linux: krita-6.0.2.1-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

MacOS disk image: krita-6.0.2.1-signed.dmg

Android

Krita 6.0.2 is not yet functional on Android, so we are not making APK's available for sideloading.

Source code

md5sum

For all downloads, visit https://download.kde.org/stable/krita/6.0.2.1/ and click on "Details" to get the hashes.

Key

The Linux AppImage and the source tarballs are signed. You can retrieve the public key here. The signatures are here (filenames ending in .sig).

KStars 3.8.3 Released

Jasem Mutlaq — Mon, 01 Jun 2026 10:36:47 +0000

KStars v3.8.3 is released on 2026.06.01 for Windows, Linux, and MacOS.

For Linux users, it's highly recommended to use the official KStars Flatpak hosted at Flathub.

This release brings major improvements to the Mount Modeler with artificial horizon filtering and uniform point distribution, significant connection speed optimizations, better guide streaming integration, and enhanced rotator handling. We've also fixed several scheduler and stability issues reported by the community. Here are the highlights:

Alignment & Mount Modeler

Christian Kemper added Artificial Horizon filtering to the Mount Modeler wizard, allowing generated alignment points below the active horizon to be automatically filtered out. Candidate coordinate points (both generated AltAz coordinates and snapped catalog objects) are now checked and rejected if they fall into active artificial horizon regions.
New Uniform Distribution mode generates points spread evenly across the visible sky using a Halton sequence, sampling in AltAz space to guarantee every point is above the configured minimum altitude. Points whose declination exceeds +/-80 degrees after conversion are rejected. The Any Stars, Named Stars, and Any Object modes now adopt this distribution internally and snap each generated position to the nearest qualifying object.
Auto-sorted wizard output: points added by the wizard are automatically sorted in nearest-neighbour slew order, minimizing total slew distance. Users no longer need to click Sort after running the wizard. Clicking Sort during a run reorders only the remaining unvisited points, leaving completed rows undisturbed.
The wizard now automatically configures the solver for each alignment point. Blind solves are used by default because no pointing model exists yet at the start of a run, so the mount's reported position may be significantly off. The GOTO mode is forced to Sync so the mount is updated after each successful solve. The original settings are saved and restored when the run finishes, is aborted, or is reset.
Refactored point generation logic to eliminate duplicated generation and conversion math in the test suite, improving generator efficiency using a stateful sequence
Toni Schriber fixed activation of the rotator button in the align module
Fixed effective focal length calculation to use radians in the DSLR branch

Guide

Thanks to Andreas Ruthner, guide streaming now correctly handles video stream window interaction. The video window no longer pops up when guide streaming starts, displays frames correctly when opened from the Capture module after a guide session, and now renders 16-bit mono stream frames (previously only 8-bit mono and RGB were handled).
Andreas also fixed frame, binning, gain and exposure sync for streaming mode. When starting guide streaming, the module now applies the same frame settings that captureOneFrame() applies for single-frame captures. Previously, streaming mode skipped this setup entirely, causing stale values from other modules to remain active in the driver.
Frame ROI and binning now sync on stream start, live gain updates apply immediately when the user changes the spinner during active streaming, and binning/exposure changes automatically stop and restart the stream
Added 0.001-0.01s exposure values to the guide exposure spinner for fast streaming and daytime testing

Rotator

Fixed several issues with Reversed rotator state not taken into account in various rotator operations
Rotation now aborts if the Position Angle error keeps increasing due perhaps to reversed rotator behavior

Ekos Profiles & Connection

Significantly cut down time to connect to INDI web manager by skipping DNS resolution if we already have an IP address specified for the remote host
Fixed rare crash due to dangling clientManager pointer with test to verify the fix

Capture & Livestacking

Use OpenCV debayering by default. Enforce even ROI selection to ensure bayer boundaries are respected.
Always sync from INDI to overwrite shadow states in the Camera process
Account for STREAM_FULL_DEPTH when streaming
John Evans added support for Live Stacker Alt/AZ data via Seestar S30 Pro. It should support other telescopes in Alt/AZ mode.
John added a gradient removal option to post processing in Live Stacker.

FITS Viewer & File Handling

Use standard gzip compress instead of Qt own compression algorithm
Support loading .fits.gz and .xisf.gz in the viewer

Scheduler & Observatory Automation

Fixed scheduler freezes when loading ESL referencing many ESQ files (patch by Tomas). BUGS:519294
Autopark should work over multiple nights now
If observatory is not started, skip shutdown procedure
Fixed issue where post-shutdown script run in infinite loop
Fixed scheduler and capture scripts not running inside flatpak

Optical Trains & DBus API

Added DBus call to set and get Pictures directory
Fixed warning of missing devices when we already selected alternative devices in the optical train

Build & Infrastructure

Use KSUtil to consolidate all calls to external executable so they can run correctly within a flatpak as well
Within flatpak, run the external scripts on the host system since it may require libraries that are only available on the host system
Christian Kemper fixed macOS iconutil failure by adding 256px and 512px icon sizes rendered from the existing SVG source, which are required by iconutil on macOS 15 (Sequoia)
Wolfgang Reissenberger updated the Dockerfile to be based on installation scripts for all steps: INDI, StellarSolver, PHD2, GSC, openCV. All scripts are built uniformly such that existing packages or installations are preferred. If the package is missing, first installing the appropriate package is tried. If this fails, the package is built from sources

Stability & Bug Fixes

Fixed crash reported in crash-reports.kde.org regarding invalid base device or message text. The check for message text now occurs earlier in the process to protect against this crash.
Milhan Kim fixed test deadlock by replacing QTest::mouseClick with animateClick(), which posts the click through the event loop and prevents tests from hanging indefinitely on QDialog::exec() loops
Fixed an issue where frequent temperature updates can cause the dark cover check to run indefinitely
Hy Murveit fixed green lines display issue
Fixed solution assignment
Fixed crash and distorted artifacts in video streaming
Replaced all abs and fabs with std::abs for consistency
Modernized signals and slots

Many thanks to Christian Kemper, Andreas Ruthner, Toni Schriber, Hy Murveit, John Evans, Milhan Kim, Wolfgang Reissenberger, Tomas, and all others who contributed fixes and improvements to this release! Your work makes KStars better for everyone.

Download KStars v3.8.3 today and enjoy improved mount modeling, faster connections, and more reliable guiding!

What Even is Ocean???

Andres Betts — Sun, 31 May 2026 21:14:15 +0000

Throughout this new process at KDE, I believe I have failed to clearly state what Ocean is and what it means for the future for Plasma user interface and experience.

In this post, I will try to shed some light into this and hopefully it’s easier for new people interested in this project.

Why the Confusion?

I think a lot of the confusion primarily comes from my part in showing graphics first and interface later.

Graphics tend to attract a lot of attention. So much that it swallows other narratives about what Ocean is. It’s natural for our users to want to know more and accept that the graphics are the whole story.

Spoiler… it’s not just graphics

How Should We Think of Ocean?

Ocean is many things, let me list them out:

Ocean Design System
Ocean Widget Style
Ocean Font
Ocean Icons(Icon Pack)
Ocean Plasma Style
Ocean Color Scheme

I think this is another reason why there is confusion out there. I have given a few talks on this as well, but I also see how it’s confusing.

In simple terms, Ocean is a new graphic design platform for the Plasma Desktop.

This new platform aims, first, to organize the way graphic design for Plasma is achieved. As you may know, designers like me, tend to be pretty creative and unbound. We give free range to creativity and we like to break norms.

This is a problem, because if we want to make graphics for a computer system, such as Plasma, we need to organize our creativity in way that developers can understand.

For this reason, in recent years, a modern way to organize creativity for computers was invented by applications like Sketch, Figma, and Adobe XD.

In these applications SVG is the graphic of choice. SVG is a set of coordinates that tell the system how to draw shapes on the screen. It’s versatile enough that SVG code can be read and tweaked by designers and developers alike. It can be stretched without losing quality, yadah, yadah, yadah… You know the rest.

This new wave of applications work with SVG as collections or repeatable graphics interconnected with each other. They use systems of “Components” and “Variants”. Given that computer UI is generally very repetitive, these components save designers time in building more copies of the same graphic with only slight modifications, let’s say for states such as default, hover, selected, etc.

These design systems help bring the world of UI development into the graphic design applications. Many developers are very used to working with graphical components, but only until recently were designers able to work with them in a flexible graphical way.

KDE Plasma has never had a system like this to organize design around the UI. Because of this, designers haven’t really made a ton of inroads into the system and this limits users in the way that we can deliver design for them. In essence, we designers, were never organized enough to provide a proper, development-ready, graphic design that could be used for Plasma.

This is where Ocean comes in. We took up the idea of creating a design system for Plasma that accounts for most, if not all, of the necessary graphical building blocks that developers could use, that preserve consistency between graphics and code, and deliver a cohesive experience for users.

By doing this, our hope is that graphic designers that are used to working with design systems can join our team and help us go even further.

On the developer side, a design system is a much more clear way of communicating component organization. Developers can more easily understand how buttons are made, what colors are used, what typography levels are on screen, etc. We do this by creating a series of graphic tokens that describe their use in more detail.

CSS is also involved, even though we may not support it, applications like Figma and Penpot have the ability to represent component code in CSS terms that others can read. In addition to these tokens, we create a series of foundational tokens where we declare our colors, typography, shadow levels and composition, blur levels, etc. Everything that users would need to see on the screen.

Ok, But What About the Graphics You Keep Showing?

During the first part of creating a design system, we noticed something pretty meaningful. Breeze and other previous themes, while they work, they don’t have any reflection in a design system. Therefore, designers have a hard time completing the puzzle for a good design system that accounts for Breeze. With any attempt, we would be completing so much of a missing puzzle that we would create something new anyway, just to replicate a style in Penpot, for example.

Because of this, we decided to create a new style called Ocean and any style is composed of many parts, listed above.

Because of this, we created:

Ocean Icons (In progress)
Ocean Plasma Style (Complete in Penpot)
Ocean Font (In progress)
Ocean Style (Complete in Penpot)
Ocean Color Scheme (Complete-ish, needs more testing)

And one little important detail, it doesn’t matter so much how Ocean style looks. Why?

Because through a design system for graphic designers, we have the ability to distribute our system for free to anyone that wants to use it. Graphic designers can tweak the design tokens that Plasma can understand and by doing that, they can more easily build a Plasma Style on their own in a way that is cohesive, thoughtful, complete. We then give those elements to the developer team that would help us execute the design. Hence why I say that Ocean is a design platform.

Still, we created a new style in graphical form and we are working with the developer team to execute this style, using the design system tokens and components, in the same way that the designer intended.

Our current focus is on icons, particularly application icons. This is just one of the many parts that compose Ocean design. A few months ago we completed a round of design that created monochrome Ocean icons. These icons are functional in nature and much easier to put together. However, we knew that app icons take longer because they are colorful and require lots of time and styling.

Icons

My recent posts showcase the progress on these icons. To be more clear about how we are doing this icon design element, here is a process:

Formalize the visual system
1. Define strict rules for perspective, lighting, shadows, gloss, depth, materials, and color usage so all icons feel like one coherent family.
Strengthen semantic readability
1. Ensure each icon immediately communicates the app’s purpose, especially at small sizes. Avoid abstraction that weakens recognition.
Improve visual hierarchy
1. Reduce competing elements and make each icon have one clear focal point with cleaner foreground/background separation.
Tighten color discipline
1. Use fewer competing colors, control saturation more carefully, and keep palettes more consistent across the set.
Be more selective with stylistic quirks
1. Avoid asymmetry, misalignment, or unusual perspectives unless they clearly improve recognition or composition.
Standardize depth and rendering behavior
1. Keep extrusion, internal shadows, dimensionality, and lighting logic consistent across all icons.
Shift from per-icon experimentation to system-level art direction
1. Prioritize cohesion and consistency over making every icon individually novel or visually surprising.

…and we are in step 3 of the process for these icons. We are moving them from rough mockups and sketches into more formalized shapes. At this stage, you should not expect a lot of color or shape cohesion. After this pass comes a time of definition. We restrict our colors even more, simplify shapes for impact, remove or redo icons, etc. It’s a major review. We expect to do this along with the community.

We also decided to not create icons for third parties. This makes the amount of app icons to make much smaller. This also makes it easier to think about what our icons should look like going forward.

All in all, Ocean is a platform composed of many parts. Our current design focus is set on completing the icon pack while the rest of the style is preparing for development.

I hope this makes it easier to understand and I am happy to answer any questions.

No Such Thing as a Free Lunch

Paul Brown — Sun, 31 May 2026 17:35:53 +0000

Joe Bloggs sat himself in front of his brand new laptop, pressed the On button and waited.

This month in KDE Linux: May 2026

Nate Graham — Sun, 31 May 2026 16:16:56 +0000

Welcome to another edition of “This month in KDE Linux” — KDE’s in-progress operating system.

Infrastructure

This month we completed a major infrastructure project. Previously, our build process was generating Arch packages for KDE software and having mkosi install them; Hadi Chokr ported this to use KDE’s kde-builder tool to compile all KDE software directly. This change brings three benefits:

Better alignment with how developers compile KDE software themselves.
Improves distro-agnosticism, so we can more easily get non-KDE software from a different source in the future should the need arise.
Substantially faster by using a more effective caching system.

QA & testing

Another major focus this month was on improving KDE Linux’s automatic QA story. The project already has a basic “does it boot to the desktop?” test for every build, but we can do much better.

To that effect, Bhushan Shah and Thomas Duckworth worked on finishing up the OpenQA-based testing system prototyped by Kangwei Zhu last year. Once fully integrated, this promises to hugely improve our ability to catch bad builds before they’re released, and we can update it over time to catch even more failure conditions.

Harald Sitter also added a test using the existing system to make sure we don’t ship an image with broken file capabilities. We did ship one bad build that includes a regression here, so this new test ensures that it won’t happen again.

Security

After multiple security issues were discovered in the upstream Linux kernel last month, a few of us (Adrian Vovk, Hadi Chokr, and I) did a mini-audit of insecure and unused software included in KDE Linux. This resulted in a variety of positive changes:

Returning to the vanilla kernel; it turned out the Zen kernel no longer offered very much beyond the config tweaks we had already made anyway.
Deleting the insecure and unused alf_alg kernel modules.
Replacing the NTFS and CDemu kernel modules with their userspace FUSE versions.
Removing the out-of-tree OpenRazer and APFS kernel modules. It was nice to have these pre-installed, but we realized they would eventually cause us to fail secure boot review, and we should instead be working towards upstream solutions. APFS support can work in userspace anyway via its FUSE driver. It looks like it might be abandoned, though. So there may be no good option; we’ll see.
Removing a bunch of unused and unnecessary packages: acpi_call, busybox, cryfs, encfs, hplip, v4l2loopback-utils (yes it is indeed unneeded; you can do everything it does in userspace), and vpl-gpu-rt.
Removing fuse2 as it’s unmaintained and known to be insecure. This will unfortunately have the effect of breaking some old AppImage apps. If you encounter any, please report that as a bug to the app’s authors/packagers; multiple other OSs have already removed fuse2, so apps really need to update to fuse3 ASAP.
Removing fenrir, which it turns out was embarrassingly not used at all for various technical reasons. This allowed us to completely remove our usage of the AUR, which had been a source of infrastructure instability in the past.

Pre-installed apps

I implemented a service to install any new pre-installed Flatpak apps on people’s existing systems. It ignores any apps you’ve previously uninstalled manually.

Speaking of new Flatpak apps, I replaced KWalletManager and its configuration page in System Settings with the new KeepSecret app, packaged using Flatpak.

I also updated Ark’s nightly Flatpak packaging to include 7-zip support and generally synchronize it with the Flathub version.

Documentation

I migrated the project’s website and documentation to https://linux.kde.org, where everything lives now. I also added a few more pages.

Grab bag

Hadi Chokr set up /opt/local for being a supported location for installing compiled binaries. This is because the usual /usr/local location is read-only on KDE Linux. This is now documented here.

João Pedro Silva Sousa fixed a bug that could make installation fail if there happened to be two KDE Linux live USB disks plugged in at once.

And that wraps up May! There’s still lots to do, so if you’re a fan of the project, please help out:

User support: help support people on discuss.kde.org using KDE Linux.
Issue reporting: install KDE Linux and report issues.
Documentation: improve docs; submit merge requests here.
Flatpak: fix packaging or code issues in Flatpak-packaged apps.
OS development: help build KDE Linux! There’s plenty to do.
Kapsule development: work on our Incus-based Kapsule system, which is integral to the “expansion by experts” story.

Week 1 : Tabs are in

Yash Bavadiya — Sun, 31 May 2026 13:11:00 +0000

This is my first weekly update as a Google Summer of Code 2026 student working with KDE on Kdenlive.

My project is "Improving Effect Widgets for Kdenlive." The first widget I'm working on is the Curves Widget, specifically adding per-channel tab support to the avfilter.curves effect.

The problem: Kdenlive's current Curves effect uses a dropdown to switch between channels (R, G, B). Switching channels wipes the previous curve there's no memory per channel. So if you tune the red channel and switch to green, your red curve is gone. You'd have to stack multiple instances of the effect to adjust more than one channel.

The fix: replace the dropdown with tabs (All, R, G, B), each storing its own curve independently, all serialized together into avfilter.curves format.

This week I went from zero code to functional tabs in Kdenlive.

What went in:

Added m_channelData (std::map<CurveModes, QString>) to store per-channel curve state and m_tabBar (QTabBar) to CurveParamWidget
Implemented slotTabChanged -> saves the current channel's curve before switching, loads the next channel's curve or resets to straight line
Implemented serializeAllChannels -> builds the full avfilter.curves format from all channel data
Created avfilter_curves.xml -> new effect definition with per-channel parameter support
Fixed avfilter.curves being silently excluded from Kdenlive's effects list

R, G, B tabs are working correctly and affecting the video output. The "All" tab (master curve for all channels) is still being worked on.

Week 2 starts tomorrow.

Tomaz Canabrava — Sun, 31 May 2026 00:00:00 +0000

I'm Tomaz Canabrava, a developer with over 20 years of experience with compiled and non compiled languages. Having worked for projects in large and small companies, I have a broad understanding of the software development process.

My strong focus is in Rust, a systems programming language that I use to build high performance, reliable software. My previous focus was in C++ with Qt.

You can see the work I do on my GitHub, and at KDE

Shanghai Report: Collaboration Talks with OpenKylin

Tomaz Canabrava — Sun, 31 May 2026 00:00:00 +0000

Back in March at FOSSASIA in Bangkok, I got invited to visit the OpenKylin team in Shanghai. I mentioned it briefly at the end of that report, and here we are — the follow-up post.

Some progress on Oxygens icons and more…

Nuno Pinheiro — Sat, 30 May 2026 11:27:06 +0000

So... progress continues on Oxygen

Over the last few weeks me and Pravin Kumar have been filling in some of the gaps in the icon set. There are still quite a few missing icons around the place, but slowly Oxygen is becoming a bit more complete again.

Its fun revisiting this old project after all these years. Sometimes I find myself looking at old icons wondering what younger me was thinking. Sometimes the answer is "not much"or, the answer is "way too much"..

Either way, Oxygen continues to grow.

Talking about fun...

I've also been spending some time investigating QML styling and themeing. And in this case not because i have immediate plans do this, but mostly because i am curious about what is possible and where the limitations actually are.

One thing I learned over the years is that there is often a large gap between what a toolkit "officially" allows and what a sufficiently stubborn designer can get away with

Some of the ideas are probably completely unreasonable. Some not so much

Which usually means they are worth exploring.

I've been experimenting with possible directions for O² and thinking about how a future visual language could work. And this that im doing now is more of an exploration on the range rgther than what it actualy look slike

Nothing concrete yet.

Mostly experiments.
Questions.
Terrible ideas.
Possibly a few good ones hidden among them.

If things continue to move forward we (via KDAB) probably make a video showing some of these investigations, experiments and concepts. Sometimes its easier to explain visual ideas by showing them instead of writing walls of text about them.

So stay tuned

And as always... if you are using Oxygen, thank you.

Its nice seeing that this old project still has a few new stories to tell.

April/May in KDE Itinerary

Volker Krause — Sat, 30 May 2026 08:00:00 +0000

Since the previous report two month ago, Itinerary got support for booking URLs, a newer foundation for its Android packages, and more detailed shared vehicle information.

New Features

Booking URLs

Some public transport services provide booking deep links together with their journey search results. That is, you can directly book the journey you have just searched in Itinerary or KTrip on the provider website, without having to search for the same journey again there. Both apps provide that option when available now.

Booking link on a train journey.

Infrastructure Work

GBFS v3 support

The handling of shared vehicles in KPublicTransport recevied a rework to properly support the much more detailed modelling of vehicle types in newer GBFS versions. Since the early versions of GBFS this has evolved from a simple enum to a complex type describing all kinds of properties of the available vehicles.

As practically all systems supporting rental vehicles for first/last mile routing (OpenTripPlanner, MOTIS, etc) are based on the GBFS datamodel, being limited to an oversimplified set of fixed types was increasingly getting into the way and prevented using newer features of those backends.

Qt 6.11 upgrade for Android

There has been a long overdue update of the Qt version used for KDE’s Android apps. As noted previously this unfortunately means losing support for Android versions 8 and below. ARM32 builds have been discontinued in the process as well, assuming that devices capable of running Android 9 or higher would also be able to run ARM64 code.

There have also been various other fixes related to the Android platform integration:

Notification interaction works properly again.
Notification icons are now handled more in line of what Android does.
Several issues related to safe area margins (ie. rounded screen corners and display cutouts) in Kirigami haven been fixed.

All of this also benefits all of KDE’s Android apps.

IATA SSIM flight schedules

Air France/KLM published their current flight schedule as open data, in IATA SSIM format. A newly built tool allows to convert that into a GTFS feed that Transitous can then consume, using Wikidata to provide translated airport and airline information.

Flight data isn’t new in Transitous, but this dataset is particularly interesting given its size. It’s not limited to Air France/KLM themselves, but also includes all (?) flights from their partner airlines. In total it’s nearly 400.000 flight patterns to almost 1.000 different airports. That essentially connects all currently disconnected public transport “islands” we have in Transitous.

Flight from BER to BLR.

The good news is that it’s holding up to that without a loss in performance, and door-to-door routing from e.g. Berlin to Tokyo actually works.

However, there’s a couple of reasons this isn’t rolled out yet and only available on the test instance:

As with the already existing flight data, connectivity between flights and ground transportation is tricky. I’ve written about this years ago already, applying the same approach helps here as well. Additionally, we get terminal information in the SSIM data in some cases, which further improves this, especially at very large airports.
We have no way yet to model check-in times in MOTIS, resulting in unrealistic transfer times from ground transportation to flights. It’s on the roadmap there, and also needed for services like Eurostar, or to model security checks at e.g. the Barcelona Sants station.
As a side-effect of that the router also finds clever tricks to bypass minimum transfer times between flights.
Inter-terminal transfers don’t seem to work reliably, probably because OSM routing doesn’t yield viable connections there. Unlike for railway stations in many countries, airport internals are unfortunately rarely mapped in detail in OSM yet.

For more details see also the discussion in PR 2090.

Events

Registration for this year’s Open Transport Community Conference in October in Bern, Switzerland, opened a few days ago. That’s as close as it gets to an Itinerary conference. If you are interested in attending better sign up quickly, many tickets were already gone after the first day.

Fixes & Improvements

Travel document extractor

Added or improved travel document extractors for Condor and monbus.es.

This has been made possible thanks to your travel document donations!

Public transport data

Improved parsing of trip and route names in OpenTripPlanner responses (bug 519906).
Adapted to Deutsche Bahn journey query API changes, fixing missing departure and arrival times there.
Added support for wheelchair accessibility information from MOTIS.
Added support for querying free-floating rental vehicles from Entur.
Removed accidental apostrophe in front of flags in the country selector.

All of this also directly benefits KTrip.

Itinerary app

Fixed Itinerary showing an empty page when opening a file with it on a fresh installation.
Fixed barcode scan mode on Android.
Added support for Matrix SSO login.
Fixed arrival platform display in journey search results.
Show calendar icons/colors when available.
Don’t load all reservation data when initializing the grouped statistics model. This improved performance of the first access to the My Data page.
Be slightly more clever when to clear seat reservation from alternatives.

How you can help

Feedback and travel document samples are very much welcome, as are all other forms of contributions. Feel free to join us in the KDE Itinerary Matrix channel.

This Week in Plasma: 6.7 Beta 2 Released

Nate Graham — Sat, 30 May 2026 00:00:01 +0000

Welcome to a new issue of This Week in Plasma!

This week the team continued getting Plasma 6.7 in great shape for release. So there was lots of focus on bug-fixing and UI polishing.

We’ve released the second beta of Plasma 6.7, jam-packed with the latest fixes. If you can, please install it and test everything! There are many options for doing so.

Notable UI improvements

Plasma 6.7

Made it impossible to accidentally drag a window so far off a screen edge that it couldn’t be moved back. (Vlad Zahorodnii, KDE Bugzilla #495635)

Uninstalling an application now removes it from the history section of all the various launcher widgets. (Christoph Wolk, KDE Bugzilla #437303)

Made auto-hide panels compatible with the “Switch desktop on edge > Always enabled” setting. (Francesco Panarese, KDE Bugzilla #370964)

The Application Launcher’s “All Applications” view now groups apps case-insensitively, so apps whose first letter is lowercase no longer get pushed into their own group. (Christoph Wolk, KDE Bugzilla #501788)

Clarified how the option to create a virtual screen works in the screen chooser dialog. (David Redondo, KDE Bugzilla #517296)

Plasma 6.8

The lock screen now fully respects the timeout value set by PAM on the underlying system, instead of adding its own mandatory delay on top of it. This means on systems with the delay set to 0, you can re-type your password immediately after getting it wrong. (Tobias Fella, plasma-desktop MR #3702 and plasma-workspace MR #322)

The lock screen now notifies you when the “Slow Keys” accessibility feature is turned on, just in case you’re failing to type your password and don’t know why. (Martin Riethmayer, plasma-desktop #3726 and plasma-workspace MR #6626)

Discover’s dialog about a Flatpak app being replaced by another one now reassures you that your data will be automatically transferred, and also warns you that favorites/shortcuts/etc. to the old app will have to be re-made manually. (Nate Graham, discover MR #1342 and discover MR #1343)

Reduced the amount of visual flickering when Discover checks for updates. (Aleix Pol Gonzalez, KDE Bugzilla #513220)

Notable bug fixes

Plasma 6.6.6

Fixed a case where KWin could crash when a monitor was rapidly power-cycled or some of its settings were rapidly changed. (Vlad Zahorodnii, KDE Bugzilla #520145)

Fixed a case where the kactivitymanagerd service could crash in the background. (Marco Martin, KDE Bugzilla #520595)

Fixed a clipboard-related issue that could make XWayland-using apps lag or freeze right after locking the screen. (Vlad Zahorodnii, KDE Bugzilla #520674)

Fixed an issue that could make the large text of the digital clock displayed on the lock and login screens look kind of jagged with certain specific fonts. (Filip Fila, KDE Bugzilla #516314)

Plasma 6.7

Worked around an oddly-specific issue in Qt that could make widgets break when enabled in the System Tray after having previously disabled them and then restarted the computer. (Tobias Fella, KDE Bugzilla #520144)

Worked around an issue with the hardware or firmware on specific laptops that could trigger an infinite stream of keyboard brightness OSDs after closing the lid. (Vitaly Repin, powerdevil MR #632)

Fixed an issue that could make a renamed file on the desktop visually disappear (it still existed, and could be accessed through Dolphin) while multiple Activities were in use, or move to another location when there was only one Activity. (Akseli Lahtinen, KDE Bugzilla #520633 and KDE Bugzilla #511920)

Fixed an issue that made it impossible to use a hardware key to authenticate to an 802.1x-protected network. (Katharina Bogad, KDE Bugzilla #520449)

Fixed an issue that made the Networks widget show the wrong icon for an OVS bridge network. (Ivan Perevalov, KDE Bugzilla #517384)

Fixed an issue that could make Plasma’s built-in remote desktop server lag or freeze when copying certain specific things in certain specific apps. (Paul Hoskinson, KDE Bugzilla #520175)

Fixed an issue that made it impossible to focus the Network Widget’s search field using Ctrl+F. (Akseli Lahtinen, KDE Bugzilla #515280)

Fixed an issue that made the buttons on the fingerprint enrollment dialog get misplaced. (Harald Sitter, KDE Bugzilla #515824)

Fixed an issue with the Breeze theming of GTK apps that made sidebar separator lines turn bright white with dark color schemes. (Levi Leal, KDE Bugzilla #484383)

Plasma 6.8

Fixed two issues that could make KWin crash or fail to evaluate mathematical calculations from the Overview effect. (Alexander Lohnau, KDE Bugzilla #519923 and KDE Bugzilla #483147)

Fixed an issue that made it impossible to open the panel context menu while already in edit mode. (Tobias Fella, libplasma MR #1468)

How you can help

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.

Would you like to help put together this weekly report? Introduce yourself in the Matrix room and join the team!

Beyond that, you can help KDE by directly getting involved in any other projects. Donating time is actually more impactful than donating money. 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.

You can also help out by making a donation! This helps cover operational costs, salaries, travel expenses for contributors, and in general just keeps KDE bringing Free Software to the world.

To get a new Plasma feature or a bug fix mentioned here

Push a commit to the relevant merge request on invent.kde.org.

Marknote 1.6.0

Carl Schwan — Sat, 30 May 2026 00:00:00 +0000

After a few months of development, Marknote 1.6.0 is out!

This release is packed with new features. First of all, sub-folders are finally supported. This allows you to better organize your notes. This feature is still very new and at the moment, we don’t support creating these sub-folders in Marknote and you will need to create them in Dolphin or your preferred file manager. But we are planning to improve this further in future releases. Each notebook now also displays how many notes are stored inside.

Another big new change is that the command bar exposed by Marknote, now allows you to search for notes across all your notebooks.

If you feel fancy, we also added an optional background blur effect for the editor similar to what is also available in other KDE apps like NeoChat.

Finally, we made it easier to add emojis to your notes by adding emoji completions to the text editor.

This release also fixes various minor bugs; contains small refactoring and improves the state of the translations.

Packager section

You can find the package on download.kde.org (kirigami addons) and it has been signed with my GPG key.

Web Review, Week 2026-22

Kevin Ottens — Fri, 29 May 2026 13:57:07 +0000

Let’s go for my web review for the week 2026-22.

What I Learned About Billionaires at Jeff Bezos’s Private Retreat

Tags: business, politics, culture, ethics

Wondering how those very rich people think and perceive the world? Here is an explanation. I felt unease reading through this.

https://www.theatlantic.com/magazine/2026/05/billionaire-consequence-free-reality/686588/?gift=fXb4ymsFcV2ntAzqIpmYvZ5SHmVudSgCCvY8EbJPC2Q

Secure Boot and Microsoft CA Rollover - a heads-up for distributions

Tags: tech, microsoft, linux, security

Microsoft has been deploying new CA certificates late… Now distros have to wake up and prepare new signatures for their shims quickly.

https://blog.einval.com/2026/05/22#secure_boot_ca_rollover

Big Tech’s Anti-Labor Playbook Has Come for Wikipedia

Tags: tech, wikipedia, community, business, work, ethics

This is very concerning. We don’t need Wikipedia to fall prey to this kind of tactics… On the contrary!

https://medium.com/@jakeorlowitz/wikipedia-is-doing-the-capitalist-thing-56a393232943

Google, I Dump Your Ass!

Tags: tech, google, web

I guess it’s time we realise Google doesn’t send much traffic on the open web / small web / indie web (call it as you please) and so there’s no need to let them harvest.

https://jaredwhite.com/20260522/google-i-dump-your-ass

The AI Gold Rush Is Eating Its Own

Tags: tech, ai, machine-learning, gpt, wikipedia, cognition, business

This is clearly the Ouroboros moment in our industry. People pushing for such restructuring and layoffs are drinking the kool-aid and will ultimately be responsible for killing what put them there in the first place.

https://blog.ppb1701.com/the-ai-gold-rush-is-eating-its-own

The Community is the Achievement; the Achievement is the Community

Tags: tech, knowledge, commons, community, ai, machine-learning, gpt, copilot, ethics, diversity

Very interesting take. This gives very valid ground on why tech communities should reject AI based contributions. Not doing so will indeed hinder the commons communities rely on to exist and improve. This is a path to prevent getting better at inclusivity and diversity (which is really needed).

https://linguacelta.com/blog/2026/05/LLMs.html

Affordances for me, but not for thee

Tags: tech, ai, machine-learning, gpt, ethics, politics, accessibility

This is a fact I don’t get… people are going their way to satisfy the need of a LLM but not the ones of fellow humans. I guess it’s the conclusion which is somewhat right, it’s about who has power. This is sad if true… also I doubt it’s the single explanation.

https://werd.io/affordances-for-me-but-not-for-thee/

The price of humans

Tags: tech, ai, machine-learning, gpt, copilot, marketing

Interesting point… Didn’t think about it this way. We’ll see I guess. Maybe human made services will actually get a premium rate indeed. Wouldn’t be a bad outcome I guess?

https://blog.umangsurana.com/blog/price_of_humans/

Can we have the day off?

Tags: tech, ai, machine-learning, gpt, work, culture, productivity

I mean, with the announced productivity gains of generative AI… It doesn’t feel like a big ask. 😜

https://mlsu.io/posts/day-off/

BitWarden selling out? Self hosting a password vault?

Tags: tech, self-hosting, security

With Bitwarden sinking, it’s maybe time to look at alternatives? This AliasVault option looks like an interesting contender even though a not young.

https://firesphere.dev/articles/bitwarden-selling-out-self-hosting-a-password-vault

A cheap VPS is a good front

Tags: tech, self-hosting, security, vpn, wireguard

Sounds like a good solution to self host things at home while having some protection.

https://ergaster.org/thoughts/front-server/

The mysterious XF86AudioPlay issue

Tags: tech, audio, hardware

This is an odd and unexpected one! Funny after the facts bit clearly annoying otherwise.

https://michael-prokop.at/blog/2026/05/20/the-mysterious-xf86audioplay-issue/

Serving files over HTTP three ways: synchronous, epoll, and io_uring

Tags: tech, linux, io, asynchronous

Good post to have an idea of the modern IO APIs available.

https://theconsensus.dev/p/2026/05/18/serving-files-three-ways.html

Rust Patterns & Engineering How-Tos

Tags: tech, rust

The writing isn’t perfect, but it covers quite a few important topics in Rust. Seems to be a nice resource even though it’s still work in progress.

https://microsoft.github.io/RustTraining/rust-patterns-book/

How Virtual Tables Work in the Itanium C++ ABI | File Descriptor Two

Tags: tech, c++, type-systems, memory

Wondering about the memory layout emitted by the compiler when a virtual table exists for a type? This is a good summary.

https://peter0x44.github.io/posts/vtables-itanium-abi/

The worst job interview I ever had

Tags: hr, interviews

Urgh… indeed this sounds like a very bad experience. Don’t do this to applicants!

https://www.oliverio.dev/blog/the-worst-job-interview-i-had

What is a harmonic? An interactive comic about additive synthesis

Tags: physics

Need a refresher on harmonics? This is a quick and fun way to do so.

https://melatonin.dev/additive-synth-comic/what-is-a-harmonic/

Why Japanese companies do so many different things

Tags: japan, business, culture

Interesting exploration of the Japanese business culture and why it’s so different to most companies found in Western countries.

https://davidoks.blog/p/why-japanese-companies-do-so-many

Bye for now!

Qt Creator 20 - CMake Update

Qt Dev Loop — Fri, 29 May 2026 10:54:11 +0000

Here are the new CMake changes in Qt Creator 20:

SPDX Cryptographic Algorithm List: Spring 2026 Update

Agustín Benito Bethencourt — Thu, 28 May 2026 12:52:33 +0000

The SPDX Cryptographic Algorithm List keeps growing. New cryptoClass values, a structured docs folder, PQC as a new property, and SCANOSS as our first user-contributor. Here is what happened in the past months.

GSoC 2026: Week 1 (Coding Period)

Roshani Kumari — Thu, 28 May 2026 11:53:00 +0000

The community bonding period is over, and coding started, so this feels like the right moment for a first blog post. I'm contributing to KeepSecret this summer as part of GSoC 2026, working on single-wallet UX and page navigation architecture.

What I did during community bonding:

->Close/dismiss button for entry detail panel

Before the Community Bonding Period:

Resolving three issues:

!17 (focus the search field when the Search action is triggered),
!18 (fix the "New Entry" dialog title, which was incorrectly saying "Create New Item") and
!20 (hides the sidebar when only one wallet exists, worked on the five layout states and cover edge cases like narrow windows with multiple wallets, single-wallet with an item open, and all three pages visible at once).

Week 1 plan:

This week, I'm working on Import/export: study existing wallet data structures in KeepSecret. Define file format and design the export flow.

Port KeepSecret's actions to the new org.kde.kirigami.actioncollection API from kirigami-app-components. This wasn't in the original proposal but it's a good addition, suggested by my mentor, notmart (Marco Martin) — it means users will be able to configure keyboard shortcuts for actions like "New Wallet" and "New Entry" through a standard KDE dialog.

More updates next week. The code is at invent.kde.org/utilities/keepsecret

GSoC 2026 KDE KeepSecret Kirigami Qt / QML

Introducing Agentic Test Generation Skills for Qt Quick

Qt Dev Loop — Thu, 28 May 2026 08:02:56 +0000

Writing unit tests can be one of the most time-consuming and least creative phases of software development. For every QML component a developer writes, an equivalent volume of test code must follow - covering properties, signals, mouse and key interactions, state transitions, and edge cases.

KDE Plasma 6.7 Beta Release

KDE Community — Thu, 28 May 2026 00:00:00 +0000

Here are the new modules available in the Plasma 6.7 beta:

plasma-bigscreen
union

Some important features and changes included in 6.7 beta are highlighted on KDE community wiki page.

Help stress-test the Union theming system

This releases marks the first public tech preview of the new Union theming system!

To make it easier to test Union in 6.7 Beta 2 and onwards, Union can now be enabled globally by setting it as your Application Style in System Settings > Colors & Themes > Application Style. Applications must be restarted to use Union.

If you’d like to test Union with a specific application, type QT_QUICK_CONTROLS_STYLE=org.kde.union [program name] into a terminal, where [program name] is, for example, systemsettings, plasma-systemmonitor, plasma-discover, spectacle, or any other QML-based app. Don’t set the environment variable globally, or this will break Flatpak apps.

The intention is for these apps to look as similar as possible when styled with Union to how they look without Union (though any minor visual improvements should be considered intentional!).

If you find any issues, make sure they’re Union-specific by running the app without Union, either by launching it with Breeze as your Application Style or by not overriding the QT_QUICK_CONTROLS_STYLE environment variable; this uses the current styling system so you can compare the two.

If you’ve found a Union-specific issue, report it here.

Everything else

View full changelog

Krita 5.3.2 Released!

Krita News — Wed, 27 May 2026 00:00:00 +0000

Today we're releasing Krita 5.3.2 and 6.0.2. This release fixes a number of issues with the text tool, and improves the Selection Action Panel significantly. Furthermore, Android now handles resource copying in the background, preventing a common crash on startup. In addition to that, many more bugfixes were made, including some by new contributors!

Fix conversion of layers names passed to GMic (Bug 517975)
Fix reversal of the layers when importing .kra as layers (Bug 514760)
Fix font selection in qt6 and improve font dropdown.(Bug 515548)
Fix text not getting selected when created on a normal layer (Bug 516006)
Make keyframe selection change layer selection.
Fix text shape not handling whitespace chars properly.
Fix KisAnimationRenderingOptions not loading frameExportConfig.
Several fixes for RGBE file loading.
Check for export status of every animation frame and error out on QFile::copy failure, Improve KisAnimationRender error handling (Thanks, Raidon Chrome).
Fix Selection Action Panel disappearing when toggling selection visibility (Bug 518633)
Add a Selection Action Panel toggle to the selection tool options docker.
Android: Copy assets without blocking main thread. This could take so long that Android thinks the application is not responding and prompts the user to terminate it.
Several fixes to testing whether the file can be created when saving a document.
Switch base image to Clang 21 on Windows.
Fix number of pixels in A1 paper preset (Thanks, Ming-Chuan Lin).
Add a context menu to the Selection Action Panel, and add these to the global menu bar too.
fix segfault in PSD COS parser (Thanks, Arimil).
Fix word selection when there's hard breaks present (Bug 518338).
Prevent division by 0 in tool outline.
Add buttons for italic and bold to font style.
Fix toggle italic action.(Bug 518890)
Fix font style-selection search algorithm in text properties docker. (Bug 518874)
Several icons for python plugins and the crash logs were added (thanks, Arkady Flury).
Fix warp transform preview not showing until first adjustment (Thanks, Ivan Valenzuela).
Revert "Fix Transform and Move shortcuts conflicting Timeline arrow key actions" (Bug 515703).
Create a qquickwidget based popup for handling popups with qquickwidgets, to improve the look and feel of the font dropdown.
Fix freeze on opening a hi-dpi image with a vector layer (Bug 519785)
Text: avoid potential assert when checking the text type.
Text: fix a bunch of potential array index crashes by using a dedicated function.
Don't move line origin if Alt is held at start (this interferes with users binding the Alt key to the line tool quick switch).
Fix saving the title element on paths correctly. This broke some symbol libraries (Bug 520345).

Check out the release notes for a full overview of all the new features in Krita 5.3 and 6.0.

[!WARNING] A particularly annoying set of bugs with the layer docker crept in. We're releasing a fix as soon as possible. We recommend waiting for the fix.

[!WARNING] One again, we consider Krita 5.3.2 suitable for productive work; 6.0.2 is, because of the many changes from Qt5 to Qt6 more experimental.

Download 5.3.2

Windows

[!NOTE] We are no longer making 32-bit Windows builds.

64 bits Windows Installer: krita-x64-5.3.2-setup.exe
Portable 64 bits Windows: krita-x64-5.3.2.zip
Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

64 bits Linux: krita-5.3.2-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

MacOS disk image: krita-5.3.2-signed.dmg

Android

Krita on Android is still beta; tablets only.

Source code

For source archives, please download one of the 6.0.2 archives and build with Qt5.

Download 6.0.2

Windows

[!NOTE] We are no longer making 32-bit Windows builds.

64 bits Windows Installer: krita-x64-6.0.2-setup.exe
Portable 64 bits Windows: krita-x64-6.0.2.zip
Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

64 bits Linux: krita-6.0.2-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

MacOS disk image: krita-6.0.2-signed.dmg

Android

Krita 6.0.2 is not yet functional on Android, so we are not making APK's available for sideloading.

Source code

md5sum

For all downloads, visit https://download.kde.org/stable/krita/6.0.2/ and click on "Details" to get the hashes.

Key

The Linux AppImage and the source tarballs are signed. You can retrieve the public key here. The signatures are here (filenames ending in .sig).

Monthly Report - May 2026

Krita News — Wed, 27 May 2026 00:00:00 +0000

Krita 5.3.2/6.0.2 is here. Read on for a look at development news and the Krita-Artists forum's featured artwork from last month.

Development Report

Krita 5.3.2/6.0.2 Released

Krita 5.3.2/6.0.2 was released, containing various bugfixes and improvements from the nearly two months since 5.3.1/6.0.1.

Fixes Since Last Month

In the Text Properties docker there are now buttons to toggle Bold and Italic next to the Font Style chooser, toggling italics with Ctrl+I works properly the first time, and an issue where some fonts wouldn't allow choosing Regular style was fixed (bug; CCbug; change).

A freeze on opening a high PPI image with a vector layer was fixed, as well as the image progress bar getting stuck (bug; change 1, change 2).

Developments in the Unstable Builds

In Krita Next, the Selection Tools now have a tool option to Move Selected Content by dragging the inside of a selection. (wishbug; change by Ricky Ringler)

Wolthera has made some improvements to the Wide Gamut Color Selector. L*a*b* and YCbCr are converted to LCh (lightness, chroma, hue) instead of directly using their channels, meaning they are now able to map properly to the HSV-based selector layouts (change). Additionally, the static hue edge option is now implemented for when hue is shown in a bar instead of a ring (change).

Community Report

April 2026 Monthly Art Challenge Results

The winner of the "Microadventure" challenge is…

Bumblebee hug by npc

Join This Month's Art Challenge!

For May's theme, last month's winner has chosen "Animals and Patterns"

Featured Artwork

This month's featured forum artwork, as voted in the Best of Krita-Artists - March/April 2026:

Recharge by zegalur

One Heartbeat by Rhea_Asma

Resilience Amidst the Chaos by Valquer

Fungal Paradise by RoamingOwl

Siamese Cat by Xaphyrx

Nominate and Vote For Next Month's Featured Artwork!

Participate in next month's nominations and voting to voice your opinion on the Best of Krita-Artists - April/May 2026.

Krita is Free - But You Can Contribute!

Krita is free to use and modify, but it can only exist with the contributions of the community. A small sponsored team alongside volunteer programmers, artists, writers, testers, translators, and more from across the world keep development going.

If this software has value to you, consider donating to the Krita Development Fund. Or Get Involved and put your skills to use making Krita and its community better!

Additional Changes

Krita Plus (Stable, 5.3.2/6.0.2):

Preset Image Sizes: Correct the A1 at 300ppi preset to be 7016x9933px instead of 7008x9933, and the A1 600ppi preset to be 14031x19866px instead of 7008x11811. (change by Ming-Chuan Lin)
File Formats: PSD: Fix a crash in text parsing. (change by Arimil)
Text: Fix detection of hard breaks as a word boundary when selecting words. (bug; change by Wolthera van Hövell)
SVG: Fix symbol libraries with title elements being mis-positioned when drag-and-dropped. (bug; change by Wolthera van Hövell)
Transform Tool: Fix Warp transform preview being empty until modifying the transform. (bug, bug; change by Ivan Valenzuela)
Line Tool: Don't move line origin when Alt is held at start of a line, only afterward. If the Activate Line Tool canvas input was assigned to Alt+Left Click, it would start off moving an empty line. (change by Carsten Hartenfels)
Selection Actions Bar: Add actions to disable or configure the Selection Actions Bar to the Select menu and a right-click context menu on the bar itself. (change by Luna Lovecraft)
General: Add icons for the Python plugin import, show log, and calligraphy increase/decrease angle/width actions. (change 1, change 2, change 3 by Arkady Flury)
Android: Fix startup crash on Android 7. (bug; change by Carsten Hartenfels)

Krita Plus (Stable, 5.3.3/6.0.3-prealpha):

File Formats: Avoid crash when export ICC profile has no TRC present, but colorants are. (bug; change by Wolthera van Hövell)

Krita Next (Unstable, 5.4.0/6.1.0-prealpha):

File Formats: PNG: Use 72ppi when a PNG file has undefined resolution, instead of ending up with an undefined number around 60million that crashes Krita when attempting to adjust it. (bug; change by Ivan Yossi)
General: Skip adding empty image updates into the updates queue, to prevent getting stuck if an update area is hugely miscalculated. (CCbug; change by Dmitry Kazakov)
Linux Wayland: Color Management: Add a CIE color diagram to the OS-managed display color management settings. (change by Wolthera van Hövell)
Windows: Fix file type names displayed in File Explorer. (bug; change by Elena Sagalaeva)

Nightly Builds

These pre-release versions of Krita are built every day.

Note that there are currently no Qt6 builds for Android.

Get the latest bugfixes in Stable Krita Plus (5.3.3/6.0.3 prealpha): Linux Qt6 Qt5 — Windows Qt6 Qt5 — macOS Qt6 Qt5 — Android arm64 Qt5 – Android arm32 Qt5 – Android x86_64 Qt5

Or test out the latest Experimental features in Krita Next (5.4.0/6.1.0-prealpha). Feedback and bug reports are appreciated!: Linux Qt6 Qt5 — Windows Qt6 Qt5 — macOS Qt6 Qt5 — Android arm64 Qt5 – Android arm32 Qt5 – Android x86_64 Qt5

Splitting Konsole views from Helix to run tools

Akseli Lahtinen (Aks) — Mon, 25 May 2026 19:39:00 +0000

I have been tinkering with Helix editor lately since I quite like it.

It's a fun little editor. Can recommend for those who like modal editing. I do not know if it'll ever replace Kate editor for me, but I'm challenging myself to try new tools, just for the fun of it.

With Helix, I've used this git tool called gitu that is rather quick and easy to work with. Though I still use lazygit for more complex tasks.

Main pain point for me has been how to use some of these tools like gitu within Helix. Lazygit could be done with some magic, but I was never really satisfied with it.

I also tried Zellij for terminal multiplexing and running commands between two splits and so on. It was a bit cumbersome to get it to work as I wanted, since Zellij has tons of features I'll never need. This also caused my fingers to get entangled since I had to remember all sorts of shortcuts. Just not for me.

In Konsole terminal, there is a shortcut for splitting views easily and automatically to a fitting size. I use it a bunch. But because I'm lazy, I would have to press the shortcut, go to the other splitview, type the command for other tool, do things and then close commands. I wanted something a bit more automated.

I found that Konsole can be set to allow scripting over dbus commands: Scripting Konsole.

So I made myself a little shell script that I placed in my path: konsole-split.sh!

Here's what it does:

#!/usr/bin/env bash

# In konsole settings, make sure
# - run all konsole windows in single process is disabled
# - enable the security sensitive parts is enabled

if [ $# -eq 0 ]; then
 echo "Command is missing!"
 exit
fi

# Split the view automagically. We can use MainWindow_1 since we have only one process
qdbus6 "$KONSOLE_DBUS_SERVICE" /konsole/MainWindow_1 org.kde.KMainWindow.activateAction split-view-auto >/dev/tty

# Get the session of the current terminal window
CURRENTSESSION=$(qdbus6 "$KONSOLE_DBUS_SERVICE" "$KONSOLE_DBUS_WINDOW" org.kde.konsole.Window.currentSession) >/dev/tty

# Run the given arguments as a command in that session
qdbus6 "$KONSOLE_DBUS_SERVICE" /Sessions/"${CURRENTSESSION}" org.kde.konsole.Session.runCommand "$@" >/dev/tty

It's really simple, but now I can use this in my helix config like this:

[keys.normal."+"]
b = ":sh git log -L %{cursor_line},+1:%{buffer_name}" #This is git log for a line, also useful, kinda like git blame
s = ":sh konsole-split.sh 'exec scooter'" # Scooter is a search and replace in multiple files tool, very handy
g = ":sh konsole-split.sh 'exec gitu'"

In practice, what happens is:

In helix, i press +
Then I select the command, in this case gitu, so g
Konsole splits itself automatically to a comfortable size
It then gets the session of that new split
And runs the gitu command with exec
- So if the execution stops/fails, it just closes the split instantly

This works really well for my needs, and I was surprised to see how simple it was to create something like this. I think the error handling when command does not work could be better, but oh well, works for me for now.

Let me know if you do anything similar or have any improvement ideas! :)

Implementation Plan for Tournaments in Mankala Engine

Sayandeep Dutta — Mon, 25 May 2026 14:51:04 +0000

We are almost at the end of our community bonding period. It’s been nearly 1 month since GSOC 2026 results, and the time to formulate a proper plan for the future plan of action regarding our project💡

Here is the breakdown of a rough plan of what I want to achieve during these 12 weeks.

(Project Setup and Implementation Plan) 💻

Week 1:

Set up the project environment and go through the implementation of https://kibao.org/
Discuss and plan the changes to be started first based on priority.
Examine ‘main.cpp’ and other game files to understand how the working and how ‘tournaments.cpp’ can be implemented.

Week 2:

Fix the user registration page with options for username and icons.
Design pre-defined selectable icons in ‘Krita’.
Write a blog post about “how to add tournaments”.

Week 3:

Start with ‘tournaments.cpp’ and check if the strings like ‘usernames’ and ‘icons’ can be retrieved from the user pages.

Week 4:

In ‘tournaments.cpp’, make the logic for detecting players online or joining tournaments with ‘room codes’.
Create a Blog post on current progress.

Week 5:

Create a page for users to host and enter tournaments. In the hosted ‘tournament’, allow superusers/organizers to edit rules like number of days, variant type, and number of players.

Week 6:

Filling empty spots with computerized opponents using the same logic as the ‘Play with AI’ option.
Examine and fix matchmaking between the players in tournaments, if the elimination and hierarchy work after elimination.

Week 7:

Design the UI for ‘tournaments.qml’, integrating the logic of the.cpp file.

Week 8:

Make the leaderboard where the winner rankings show up.
Create a Blog post describing the implementation.

Week 9 and 10:

Examine the working and the build after completing the tournaments.cpp and tournaments.qml.
Test and play with others in demo tournaments to get feedback on the working process.
Add Voice chat for users playing the game. (if possible)

Week 11 and 12:

Document the changes made, review the overall codebase, and finalize it for the submission.
Create a Final Blog post summarizing all work.

Thanks for reading. Happy coding🚀

Week 1 : Coding Begins

Yash Bavadiya — Mon, 25 May 2026 03:57:00 +0000

It's May 25. Community bonding is over. Coding starts today.

The last few days of bonding were about wrapping loose ends, got two MRs merged: warn before deleting tracks and snap playhead to snap points. A few others are still open and in review, but the coding period waits for no one.

Now for the actual project.

This week I'm starting on the Curves Widget , the first of three widgets I'm building this summer for Kdenlive.

The current CurveParamWidget has a channel dropdown (R, G, B, All), but switching channels wipes the previous curve. There's no memory per channel. So if you carefully tune the red channel and switch to green, your red curve is gone. You'd have to apply the effect multiple times, once per channel which is exactly the kind of friction the proposal is trying to eliminate.

The fix is per-channel tabs, each storing its own curve independently. All channels serialize together into avfilter.curves format: r='0/0 0.5/0.7 1/1' g='0/0 1/1' b='0/0 1/1'

Backward compatible with existing projects, no data loss when switching tabs.

This week's goal is foundation work: understand the full CurveParamWidget architecture, design the tab skeleton, and get the per-channel data structure in place. No full functionality yet, get the structure right first, then build on it.

I'll post every week on Sundays. Daily progress goes to JB on Matrix.

Let's go.

Introductory Blog

Ojas Maheshwari — Sun, 24 May 2026 15:12:09 +0000

Hello, I am Ojas Maheshwari.

I am a C++ engineer who is currently writing code for KDE community for GSoC '26. My project involves performing "font subsettting" on a PDF rendering library called Poppler which Okular (KDE's Universal PDF Viewer uses).

This site will contain general blogs as well as the official documentation and progress updates on what I did through the whole journey including:

My approach and plan.
The problems I faced and how I solved them.
My thinking process wherever possible.

This is an introductory page to see if the site works correctly. Thanks :D

“Long-Term Support” doesn’t mean what you think

Nate Graham — Sat, 23 May 2026 19:05:14 +0000

My last post about good beginner-friendly KDE-focused operating systems sparked some discussions about the concept of “Long-Term Support” (LTS) releases.

But what does this term mean? It’s a bit generic-sounding, making it easy to interpret as meaning almost anything. So let’s go to the source: how the term is defined by the operating systems using it! Here are the non-commercial ones:

Debian Stable says:

Security updates are provided by Debian security team for three years. This generally means that each stable release is supported for its whole life plus an extra year (or so) after a new version of stable is released. In addition, further security support is provided by the LTS and LTS/Extended projects.

Ubuntu says:

LTS stands for long-term support — which means five years of free security and maintenance updates

Kubuntu says:

The latest Long Term Support (LTS) version of the Kubuntu operating system for desktop PCs and laptops, Kubuntu 26.04 [is] supported with security and maintenance updates, until April 2029.

(I didn’t include openSUSE Leap because its marketing material doesn’t use this term, though what it offers is fairly similar in practice)

So these operating systems are fairly consistent about what “Long-Term Support” means to them:

Each discrete OS release will continue receiving updates for a certain number of years.
Those updates will include fixes for security issues.
Those updates may include whatever “maintenance” means; Ubuntu & Kubuntu promise this, Debian doesn’t say.
Those updates will not include any new features, UI improvements, or other non-bug-fix releases from the software’s developers. That is to say, each piece of software is effectively locked to a specific version for the life of the release.

That’s it! So let’s look at what’s NOT promised:

Lack of bugs
Lack of crashes
Fixes for non-security issues
Personal support for issues you encounter
Support for newer hardware devices (Ubuntu offers “hardware enablement” kernels for desktop installs by default, but they come with no stated guarantees and don’t cover the parts of hardware support that go beyond the kernel)

That doesn’t mean an LTS release of Debian, Ubuntu, or Kubuntu will be devoid of these things. It just means they aren’t promised. Probably you’ll get a lot of them anyway, but there’s no guarantee.

I think this is where some of the persistent confusion around the LTS topic comes from.

LTS releases are fairly reliable as long as you use the most popular software from their included software repositories. So in the circumstances when this stops being the case, I think sometimes people can feel betrayed. They think, “I thought this was supposed to be stable! Why didn’t anyone fix this bug yet? Where’s my long-term support?”

But Debian, Ubuntu, and Kubuntu never promised any level of reliability or absence of bugs. They promised that the version-locked software in their repos would receive security fixes for a certain number of years. Ubuntu and Kubuntu also offered a certain amount of non-guaranteed best-effort hardware compatibility improvements and non-security bug fixes.

That’s it!

So it’s important to understand what you’re actually getting with an LTS-style OS. And maybe it’s not for you. There are plenty of other options for people with different desires:

I want newer software

If you’re a software developer or a technology enthusiast, you may want to get software on or closer to its developers’ release schedules. This will give you a stream of new features, UI improvements, and fixes for bugs. In this case, the better option is a rapidly-updating OS like Arch Linux, openSUSE Tumbleweed, Fedora KDE, or one of their children.

The trade-off here is that you may have to live with some things that are currently working getting broken after updating. In other words, the bugs are unstable, unlike in an LTS OS where the bugs are stable.

I personally fall into this group, which is why I use a rapidly-updating OS and not an LTS OS.

I want fewer bugs

I think a lot of people choose an LTS OS to experience fewer bugs, but this is generally not a strength of the LTS product. When an LTS OS freezes on a specific set of software, all the bugs in those versions of the software are frozen, too. Unless the LTS OS provider fixes any of those bugs themselves or backports fixes for them, users will be exposed to them for the lifetime of the release.

With a rapidly-updating OS, when software developers fix bugs in their software, you’ll get those bug-fixes quickly. As long as the software itself is becoming less buggy over time, a rapidly-updating OS shipping software close to its developers’ release schedules will likewise become less buggy over time.

It’s not all puppies and rainbows, though. A fast pace of change means more opportunities for those developers to accidentally introduce new bugs, and also for the introduction of integration issues: bugs caused by software being mis-configured or incompatible with other software. LTS OSs excel at minimizing integration issues between software, because a frozen set of software isn’t a moving target for QA testing.

So in a lot of ways, this choice boils down to whether you’re more bothered by software bugs or by integration issues.

I want better hardware support

If the manufacturer of your device didn’t provide much or any Linux software support for it, a rapidly-updating OS is likewise a better option here. You’ll quickly get all the components that improve hardware support, not just the parts in the kernel.

I want a true reliability guarantee

If time is money for you, this makes sense. And to get it, you’ll need to pay for a commercially-supported operating system. For example, Canonical offers “Ubuntu Pro” with a level of support that includes the following:

Build with confidence with 24/7/365 phone and ticket support. Get prompt help when something breaks on any of the packages in the Ubuntu Main and Universe repositories, including the most widely used open source applications and toolchains. Our 24/7 plans now include SLAs not only for initial response times, but also for ongoing follow-up updates ensuring continuous visibility and faster remediation throughout the lifecycle of your support case.

Wow! Now that’s support. It costs $300 per year for workstations (servers are over 5x as much).

Red Hat and SUSE offer similar services at similar prices.

And they aren’t cheap! But if time is money, those prices may look pretty reasonable. And you’ll get to talk to a perky and friendly person over the phone when you encounter a covered problem, and someone will to take direct responsibility for getting a fix delivered.

What about Flatpak and Snap?

In principle, these technologies allow an LTS-style OS to offer the best of both worlds: a stable base with apps updating more rapidly.

In practice, what you get is a mixing of both worlds. The base OS retains its LTS characteristics, while apps become rapidly-updating, giving you some exposure to breakage coming from new versions alongside more features, UI improvements, and fixes for existing bugs.

We’re spoiled for choice in our ecosystem, which means everyone can find a free software operating system that matches their needs and desires. But you have to know what those needs and desires are, and also successfully map them to the available options! Hopefully this blog post has helped explain what the LTS-style operating systems offer, and who should use them.