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] 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

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-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.

• 64 bits Intel CPU APK

• 64 bits Arm CPU APK

• 32 bits Arm CPU APK

Source code

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

Download 6.0.2

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-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

• krita-6.0.2.tar.gz

• krita-6.0.2.tar.xz

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).

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

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:

1. In helix, i press +

2. Then I select the command, in this case gitu, so g

3. Konsole splits itself automatically to a comfortable size

4. It then gets the session of that new split

5. 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! :)

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🚀

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.

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

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.

Welcome to a new issue of This Week in Plasma!

This week the focus was squarely on polishing up Plasma 6.7 in preparation for release on June 16th. Bugs were squashed, user interfaces were improved, and amidst it all, a lovely community contribution added support for monitoring modern Intel GPUs. Check it all out:

Notable UI improvements

Plasma 6.7

Clearing the clipboard while any items are starred no longer asks if you want to clear the starred items as well; now they are never automatically cleared, and you have to do this manually, on the logic that if you starred those items, you probably want to keep them around! (Tobias Fella, plasma-workspace MR #6583)

When the Disks & Devices widget appears after you plug in a disk, it no longer briefly flashes with the notification icon. (Bohdan Onofriichuk, KDE Bugzilla #495141)

Plasma 6.8

When Discover prompts you to delete data and settings for a no-longer-installed Flatpak app, doing so now sends all that stuff to the trash rather than deleting it immediately and irreversibly. (Nate Graham, KDE Bugzilla #520220)

Re-arranged the sections on Discover’s home page to put the “Editor’s choice” section closer to the top. (Raresh Rus, discover MR #1333)

Reduced the amount of visual jankiness in Discover’s “overall progress” indicator UI during system updates. (Taras Oleksyn, KDE Bugzilla #510282)

Made the search on Discover’s Updates page case-insensitive. (Tobias Ozór, discover MR #1328)

Notable bug fixes

Plasma 6.6.6

Fixed a case where Plasma could crash when you switched Activities using the Activity Pager widget. (Marco Martin, KDE Bugzilla #520065)

Worked around a Qt regression that made job progress notifications remain visible on screen until explicitly dismissed. (Kai Uwe Broulik, KDE Bugzilla #520120)

Fixed an issue that broke the setting to remember your approvals in the screencasting permission dialog. (David Redondo, KDE Bugzilla #517454)

Fixed an issue that mis-rendered non-default window decoration themes when using a scale factor below 100%. (Vlad Zahorodnii, KDE Bugzilla #520272)

Fixed an issue that broke Global Themes’ ability to add and position widgets as expected. (Marco Martin, KDE Bugzilla #512005)

Plasma 6.7

Fixed some cases where Plasma could crash when plugging in or unplugging screens. (Marco Martin, KDE Bugzilla #468430)

Worked around a Qt issue that could sometimes make the crash reporter tool itself crash in a loop. (Harald Sitter, KDE Bugzilla #517353)

Fixed an issue that could make Discover sometimes crash when installing a Flatpak app from a downloaded .flatpakref file. (Tobias Fella, KDE Bugzilla #520371)

Fixed a case where Plasma could crash while a Weather Report widget was checking for weather updates. (David Edmundson, kdeplasma-addons MR #1051)

Fixed a bizarre issue that could make the Kickoff Application Launcher widget grow vertically on X11 immediately after opening it following a switch to an alternative widget and back right after login. (Harald Sitter, KDE Bugzilla #515116)

Strengthened the system to prevent gaps from appearing between the screens in a multi-monitor setup. (Xaver Hugl, KDE Bugzilla #507702)

Fixed an issue in the Global Theme creator feature that saved panel settings incorrectly. (Akseli Lahtinen, KDE Bugzilla #520489)

Fixed an issue in the Digital Clock widget that mis-colored the dots for calendar events on the previous month. (Young Lord, plasma-workspace #6587)

Fixed two pointer issues seen while zoomed in using KWin’s Zoom effect: duplicated pointers while shaking to make them bigger, and pointers becoming visually de-synchronized while dragging things. (Xaver Hugl, KDE Bugzilla #489265 and KDE Bugzilla #513233)

Fixed an issue that could make Discover report different states in different pages for an app currently being installed or uninstalled. (Oliver Beard, KDE Bugzilla #520028)

Plasma 6.8

Fixed an issue that made it impossible to add an app to your favorites list immediately after un-installing and re-installing it. (Christoph Wolk, KDE Bugzilla #494542)

Frameworks 6.27

Fixed a visual glitch sometimes seen in Discover’s sidebar when the app was launched. (Nate Graham, KDE Bugzilla #520337)

Notable in performance & technical

Plasma 6.7

Fixed a couple of memory leaks discovered in KWin. (Xaver Hugl, kwin MR #9235)

Plasma 6.8

Added support for the Intel Xe driver to the System Monitor app and widgets. (Hunter Hardy, KDE Bugzilla #512866)

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.

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

Make your website or blog fediverse-ready

Tags: tech, fediverse, blog

It’s not complicated, and a good thing to do.

https://stefanbohacek.com/blog/make-your-website-or-blog-fediverse-ready/

Dumb Ways for an Open Source Project to Die

Tags: tech, foss, community

Not sure it warranted the “dumb” mention in the title. Still it’s likely a good idea to have a list of the ways projects can die.

https://nesbitt.io/2026/05/19/dumb-ways-for-an-open-source-project-to-die.html

On Google declaring war on the Web

Tags: tech, google, ai, machine-learning, gpt, attention-economy, knowledge

Ultimately, they just want people to stay on the pages they fully control and not have them visit anything out of their mall.

https://tante.cc/2026/05/20/on-google-declaring-war-on-the-web/

I don’t think AI will make your processes go faster

Tags: tech, ai, machine-learning, copilot, engineering, processes, productivity

Good overview of why we don’t see a speed up in development processes when AI tools are introduced. The bottlenecks don’t magically get destroyed.

https://frederickvanbrabant.com/blog/2026-05-15-i-dont-think-ai-will-make-your-processes-go-faster/

Twelve Ways to Be Wrong About AI-Assisted Coding

Tags: tech, ai, machine-learning, copilot, productivity, research, science

Or why most of the studies we see out there can’t be trusted. They’re full of holes and flaws. We’d really know people who know what they do in humanities to conduct such studies to get a chance at a proper picture.

https://third-bit.com/2026/05/20/twelve-ways-to-be-wrong/

Misconceptions about the UNIX Philosophy

Tags: tech, unix, history, microservices

I agree with this short history tour. It’s the composability which matters.

https://posixcafe.org/blogs/2024/01/05/0/

Shell Tool Testing

Tags: tech, tests, shell

A proof that you don’t need much to write a test suite.

https://zork.net/~st/jottings/shell-tool-testing.html

Spork: A posix_spawn you can use as a fork

Tags: tech, unix, linux, processes, research

fork() doesn’t want to die. But help is coming it seems. Maybe the day it disappears from kernels is “near”.

https://dl.acm.org/doi/epdf/10.1145/3713082.3730396

C++26: More function wrappers

Tags: tech, c++

Time to retire std::function in new code.

https://www.sandordargo.com/blog/2026/05/20/cpp26-copyable-function

Scaling Rust codebases: Lessons learned organizing large projects and managing errors

Tags: tech, rust, architecture, complexity, pattern

Nice suggestions on how to structure larger Rust code bases. The proposed error handling is particularly neat and tidy. This is doable in other languages but tends to be more verbose.

https://kerkour.com/rust-organize-large-projects-code-error-handling

SIMD-accelerated integer-to-string conversion

Tags: tech, simd, performance

Really smart SIMD trick which packs a punch.

https://lemire.me/blog/2026/05/18/simd-accelerated-integer-to-string-conversion/

Dependency cooldowns are unfair; we should use phased rollouts instead

Tags: tech, security, supply-chain

This is a good point. I feel unease at the current trend pushing toward cooldowns. The proposed rollout scheme is much better and fairer.

https://illegalcode.net/rfcs/phased_rollouts.html

Stop Using Pull Requests

Tags: tech, codereview, pairing, mob-programming, trust, productivity

The title is a bit too much of a blanket statement. Still there’s indeed a lovely no between pair programming and merge requests. If possible you should favour the former. Yet it rarely happens in practice, there are reasons for that.

https://a4al6a.substack.com/p/stop-using-pull-requests

organizational knowledge

Tags: tech, organisation, knowledge

Knowledge management is hard. It’s almost never a tool problem despite what people claim.

https://jarche.com/2026/05/organizational-knowledge/

Three Tips for Succeeding as an Accidental Leader

Tags: tech, leadership, management, learning

The responsibilities drop on people before they’re ready for it (I see it first hand regularly at customers). Such tips are thus welcome and helpful during the transition.

https://www.jrothman.com/newsletter/2026/05/three-tips-for-succeeding-as-an-accidental-leader/

Two facilitation methods starting with a single line: Actions|Results & +|Δ

Tags: facilitation, decision-making

Nice little facilitation formats. I’ll try those for sure.

https://improvesomething.today/single-line-facilitation/

Three ways people respond to a problem (other than solving it)

Tags: problem-solving

Very good points. Solving problems is not necessarily what happens when they are identified.

https://improvesomething.today/responses-to-problems/

Bye for now!

We're excited to announce the release of version 1.14.0 of the Qt Extension for Visual Studio Code! This release introduces QML Live Preview with hot-reload capability, bringing real-time feedback directly into your editor.