Kwi has continued to mature at a fast clip over the past week, with many a bug slain and a significant amount of UI refinement.

Exciting news also from our important upstream, the Ghostty project: Earlier than we had anticipated, libghostty-vt was released in version v1.0 on the weekend. This provides Kwi with a stable API/ABI from our headless terminal emulation backend, which will greatly aid distros and packaging efforts in particular.

For the Ghostty project this is the culmination of a solid half-decade of work - congratulations to mitchellh and many other contributors over there!

Progress Tracker

• Terminal:
  • Shift-click now extends selections, just like in Konsole (feature request #528514)
  • Sharper, better rendering of geometric symbols at fractional scales
  • Improved grid size calculations at fractional scales
  • Improved font baseline placement
  • Additional performance improvements in text rendering
  • Configured SSH aliases/hostnames are now used in tab titles instead of resolved IPs; this was filed as a regression defect against Konsole we fixed in Kwi (bug #524673)
  • Fixed a greyscale glyph placement bug that caused e.g. Noto Sans Mono's i character to act up when LCD filtering was disabled in the text renderer (bug #528550)
• Tab bar:
  • New output causes background tabs to get colorful title text to communicate activity, à la Konsole (feature request #528658)
  • Dragging files, URLs and similar over tabs now raises them after a brief delay, to make it easy to drop those contents into the tab (feature request #15)
  • On popular request, the tab bar is now overall significantly more compact (on Matrix and reddit, and in other places)
  • Tab button contents are laid out more pleasingly
  • Ditto for tool buttons on the tab bar
  • As a small cleanup, the typically redundant default tab icon is no longer shown; special status icons remain (by popular request on Matrix)
  • Icons that are line art (e.g. many symbolic Breeze icons) are now colorized to match the tab title text (which goes nicely with the above activity coloring)
  • If the window is fullscreen, care is taken that tab buttons are proper click targets at the screen edge (c.f. good old Fitts' law) (bug #528546)
  • Default tab switching shortcuts now match Konsole's (both primary and alternate; requested on Matrix)
  • The bottom divider below the tab bar now looks better and more consistent with other KDE apps at fractional scale
  • A window's terminal grid size is now preserved correctly when the window is moved between screens with different fractional scales (bug #528515)
• Other UI:
  • Kwi now supports the "Find Action" dialog that many other KDE apps offer (similar to a Command Bar in other apps), available via the standard Ctrl+Alt+I shortcut (requested on reddit)
  • The background opacity slider now uses a less granular tick step to make it look less busy, and space for its label is reserved so the slider doesn't change width during use
  • All windows now share a single QML engine, slightly improving resource usage
• Portability:
  • Sandboxed Kwi (Flatpak) now works on certain NixOS, and potentially other, systems with unusual PATH/filesystem setups (bug #528754)
  • Kwi now works on BusyBox-based systems (by using the portable timeout -s instead of timeout --signal=; reported on Matrix)
• Dependencies:
  • Bumped our libghostty-vt dependency first to v1.0, then to v1.0.1
• Project bits:
  • Updated the example screenshot for Kwi's KDE apps listing (note: the CDN updates these only very slowly)

Additionally, because Kwi is built on KDE's latest technologies, we sometimes get to find and fix bugs upstream of the project, or contribute new features needed by Kwi.

Upstream This Week - by Kwi, for everyone:

• We fixed a bug in KDE's KDBusAddons library so that running Kwi from a terminal will open the new window in the terminal's current working directory, even if Kwi is already running (MR #75, bug #528661).
• We fixed a bug in KDE's Kirigami UI library that made it impossible to configure Alt+Arrows as shortcuts in Kwi (MR #2234, bug #528659).
• We worked on components in KDE's Kirigami Application Components UI Library to allow the "Find Action" action dialog to work in apps which can open multiple windows, along with enabling some code cleanups/reductions in Kwi (MR #27).
• Further in Kirigami Application Components, we fixed a bug that made it hard to search for certain actions using the search field in the "Find Action" dialog (MR #26).
• One more in Kirigami Application Components, we have a contribution remaining in flight that will fix invoking actions in the dialog using the Enter/Return keys (MR #29).
• In KDE's Breeze UI theme we fixed the rendering of slider tickmarks at fractional scale (MR #649), as seen in Kwi's Settings dialog.

Update on Release

As mentioned last week, Kwi continues to undergo the "KDE Review" process at the moment, a community quality gate through which it will graduate to become an official KDE project. While we have already completed the required checklist, the minimum mandatory duration is two weeks. Kwi will complete this on November 18th.

Shortly thereafter we plan to tag a v0.1 release and publish to Flathub!

Outlook

Also mentioned last week, we're working on a way to make it easy to switch classic KDE apps such as Yakuake and Dolphin to embed Kwi.

While the Kwi-side bits have been in place since its initial publication, this is mainly about providing a central setting to make this easier for users (currently it requires fiddling in the filesystem). We now have a prototype implementation, and plan to submit a merge request to the relevant KDE project (roughly in the dependency stack of System Settings) soon.

Now the bad news: Expect Kwi development to move a bit slower in coming weeks, and focus mainly on important bug fixes. There may even be a brief interruption in this newsletter! The reason is brief interruption by work on other projects related to things nearly as old as UNIX terminals.

Once we are back to full capacity, we plan to begin work in earnest on the implementation of the much-requested Split Panes.

13 Nov 2026 12:00am GMT

KDE e.V., the non-profit organisation supporting the KDE community, is looking to hire a software engineer to help improve the software stack that KDE software relies on. Please see the call for proposals for more details about this contract opportunity. We are looking forward to your application.

The full call for proposals has more details.

12 Nov 2026 12:00am GMT

It has been brought to the attention of the KDE security team that NeoNova Animated Wallpaper (https://github.com/abbygraceton1992/NeoNova-KDE-Wallpaper) is shipping malware.

This report came from Serg Star who spotted it reviewing this code. It's great that we have people spotting this stuff, though it may be too late for some.

The Malware

The package looks very legit, its an animating wallpaper that works as advertised, they even did later commits on top adding configuration options!

However since the initial commit the code has been shipping hidden malware.

A script (hidden in a base64 string in a base64 string) makes a web request to download an "image", which is another bash script which in turn downloads a libary .so file into ".config/Plasma6Library.so" and launches it via LD_PRELOAD=~/.config/Plasma6Library.so sleep 999999
The payload thus far looks like this: https://github.com/BishopFox/sliver which is designed to allow remote control.

If you have installed this wallpaper, a good test would be checking for .config/Plasma6Library.so and I would suggest starting anew.

What Happens Now

There is only so much we can do with 3rd party content. We have reported it to all relevant places including Pling and OpenDesktop who have taken swift action within hours of us getting the report.

It it a stark reminder to be vigilant and wary when installing external content from other sources especially those that run in unsandboxed contents, and a reminder to those of us working on the Linux desktop to continue working on technologies that allow for safer and better distribution.

11 Nov 2026 12:52pm GMT

New release for plank-player, aura-browser and bigscreen-ui

Wow, new releases! We are releasing applications and a new UI framework this month.

Bigscreen UI is a library of shared Qt Quick components to build applications for TV, built on Kirigami.

Plank Player and Aura Browser were originally released as part of the Plasma 5 release schedule. We have updated them to use Bigscreen UI, and released them independently for now. The eventual goal is to move them to the KDE Gear release schedule.

Location	Sha256 Sum
plank-player-26.11.0	2cea69c6790546c1e4d19cf6a8320be28c780f5856993e78683fe1640eb49d66
aura-browser-26.11.0	0f5007e4e665874020c3042a2c7a914898516e91a385be20144f437ea7ef77be
bigscreen-ui-0.1.0	c19186dd22c3c4e9fa7dcc76e87ef995d1a78f5d0d79f4788f85e221ce6a1ca3

Bigscreen UI

bigscreen-ui is a new library of UI components to build applications for Plasma Bigscreen, with a focus on making it easy to implement arrow navigation for remote control. The components were extracted out of the ones used in the Plasma Bigscreen shell, now decoupled for application development purposes.

Learn more about it on GitLab, and see the example application. We plan on introducing official documentation as the API stabilizes.

Aura Browser

Aura Browser is a web browser for Plasma Bigscreen, with a focus on making it easy to navigate pages with a remote.

Plank Player

Plank Player is a media player for Plasma Bigscreen. Users can either browse media via the homescreen, or invoke the application directly on the media. It is built on Qt Multimedia, which brings support for other features such as subtitles and audio tracks.

11 Nov 2026 12:00am GMT

One of the big things I wanted to achieve during this HDR project is to have a decent tone and gamut map filter, something Krita never had all these years, in spite of us having unbounded floating point editing as well as color management via LCMS that works with this unbounded floating point.

The unbounded floating point allows us to have values that might be (0.0, 0.5, 1.0) in linear rec2020, and then when converted to linear sRGB this becomes (-0.37, 0.56, 1.0). Now, the range of each channel here is [0 1], so if we try to represent that as an inbounds sRGB colour (which we need to do if we want to save for web), the default behaviour is to clip the out-of-bounds values, so we get (0.0, 0.56, 1.0). This changes the proportion between the blue and the red and green channels, meaning the hue and saturation will shift. In some cases, it can cause colours to gradually shift to values like (0.0, 1.0, 1.0). This is, for example, why your phone camera won't shoot that lovely orange sunset just right: The colors are too colourful and get pushed towards yellow due clipping. So to combat this, you do gamut mapping: you shift the colour in bounds by a certain algorithm before or after doing the conversion.

Gamut Mapping

The most common gamut mapping algorithm is chroma-reduction. This assumes that the target space and the source space have their greys at the same location (taking into account white point adaptation). Then, the colors are converted to a third space, a opponent color space that also has its greys in the same location.

Opponent color spaces are spaces where the luminosity are separate from the chromacity and hue, and the chromacity and hue themselves are expressed as a red-green and a yellow-blue contrast, following the opponent theory of human color vision. A typical example of an opponent color space is LAB, but there's many others, like YCbCr, ICtCp and OkLAB. These opponent colorspaces can then be translated to a Hue, Chroma and Luminosity space by treating the red-green and blue-yellow contrasts as Carthesian coordinates, and converting those to polar coordinates, giving us hue as the angle, and chroma as the length.

Then, for chroma reduction, you do a binary search to find the edge of the gamut, with each iteration, increasing the chroma or decreasing it, until the difference between the desaturated color, and the clipped version of the color is below a significant difference. That significant difference is called the minimum delta E, E being the name given to color difference by itself.

Shown above: a slice of LAB chromacity plane, with a black-to-white gradient diagonally. The first image is plain clipping to sRGB, while the second uses chroma reduction gamut mapping. In the first image, the chroma of the colors bottomleft and topright are so bright that when clipping they end up way with the wrong luminosity than they should have in reality. By doing chroma reduction, we pull these colours so far back in that their luminosity is preserved.

Krita implements CSS-4's chroma reduction method, and offers it with 3 different opponent spaces: LAB, ICtCp and OkLAB.

This is because the delta E calculation for LAB is a little off, in particular, LAB is known to give weird results with the blue, with bright blues looking a little purple in LAB. ICtCp and OkLAB are much more modern and are particularly designed to have much better handling of the blue hues, which is visible in the gamut mapping:

ICtCp and OkLAB also had the advantage of being possible to implement in an ad-hoc manner starting from XYZ, so I didn't need to integrate them directly into our color management system yet.

Besides binary search, there's the cusp method. Here, you figure out the luminosity and maximum chroma of a given hue (the cusp), and use that to approximate the gamut boundary. There's two ways to calculate the cusp:

The first is to use 6 polynomials, but that method only works with OkLAB as the opponent space and target RGB spaces that are matrix shapers. This in turns had to do with the simplicity of OkLAB as a colour space compared to other opponent spaces.

The second is to create a look up table of cusps per hue. Here, you take the known cusps in the target colour space and convert them to the opponent space to get their chroma and luminosity. This works for both CMYK and RGB spaces, as we know the likely cusps for those: Red, Yellow, Green, Cyan, Blue and Magenta and the interpolations between those. It also works with LAB, ICtCp and OkLAB equally. I went with this second method for now, but the first method is going to be more precise, and is worth investigating.

With the cusp for a given hue, you can then draw a triangle, going from black, to the cusp, to the reference white of the target space (important to keep in mind when combined with ICtCp-pq!), and back to black. The maximum chroma for a given lightness can then be derived by calculating the intersection between the current chroma and luminosity, and the zero chroma (grey) version of said luminosity.

Both the CSS4 gamut edge seeker algorithm and Ottoson's algorithm use a curved top (cusp to reference white) section for the triangle here, but I am skeptical that this is strictly necessary. The colour only needs to be pushed into gamut enough so that once you clip it doesn't cause massive hue and luminosity changes.

The interesting thing about the cusp method is that with the location of the cusp, you can decide to not just intersect with the grey of a given luminosity, but instead draw the line slightly towards the luminosity of the cusp. Bjorn Ottoson has a blogpost with experiments demonstrating this, and while not right now implemented in Krita, I would like to give it a go in the future as it can give more chromatic results.

There's other methods. Scaling ("chroma compression") methods, for example, generate a histogram of chromacity and lightness at a given hue-angle in the input image, and then the same for the target gamut. The resulting algorithm then doesn't need to do any binary search, but can just scale the chromacity of the input by taking the maximum source chroma and scaling it by the maximum target chroma. This is also not yet implemented in Krita, but it might be interesting for CMYK output. Technically this is what ICC's perceptual and saturation intents are all about, but those suffer from being too generic: a desaturated image that is fully in-gamut for the target space will get treated with the same lookup table as a fully saturated image, leading to odd results. A image-specific filter might give much better results.

Finally, when the target space is greyscale, we don't bother with either method and just set the saturation to 0.

Tone Mapping

Tone mapping is a subset of gamut mapping, where we only try to get the full range of tones (luminosity) into a target range. This is used to prepare HDR images for SDR output.

This is typically done by applying a so-called "filmic" curve. The name "filmic" derives from these curves mimicking real world chemical film's tone properties, which when mapped onto a graph somewhat resembles a flattened "S". The top part of this S-shape is referred to as the "shoulder" and the bottom part the "knee", or, because it is quite tiny compared to the "shoulder", the "toe".

In the following section I'll be using a picture of a blue orb on a grey background with some sparkles. I drew the original image on an HDR display, and it's brightest highlights are around 8.0 (8 times higher than the reference white). Because most people don't own a HDR display, I'm not going to try and share the image. Instead, I'm sharing the above image with two different exposures: The first is 0 exposure, it just clips all the colors. The second is with -2 exposure, showing how the highlights are supposed to look, but now the shadows are too dark. What we are looking for in the following images is that the sparkles are distinct from the highlight on the orb. That the blues look nice and don't hue shift too much and that the shadows are not too light or too dark.

When looking for curves to implement, I wanted to have curves that were user configurable. So the first curve I implemented was the extended Reinhard curve. This is a pretty well known solution and the curve allows selecting the maximum white that gets mapped to 1.0. While it has a nice shoulder, it doesn't have a knee or toe of any kind, which means it loses the contrast that is present in the HDR image.

I then briefly looked at the Hermetic Filmic Curve as described by bt 2390-8, which has both a shoulder and knee. However, that one is applied in the PQ transfer instead of linear light, and the PQ transfer requires decisions about the brightness of the reference white, so I wasn't sure how to do that one properly.

Then, I came across John Hable's Piecewise Filmic Curve: A very configurable curve which has various parameters for editing the shoulder and toe. It takes a bit to configure, but as you can see, once configured, it preserves the contrast quite well:

I implemented both curves on top of LAB, and xyY. This means that they're applied to the luminance channel only.

Frequently, you will see the discussion on whether to apply the tone mapping to individual channels, or to apply it to a Luminance channel only. The base argument for using individual channels is that it'll give chroma reduction as the colour will get lighter. The argument for applying it on a luminance channel is that it is more radiometrically correct. Though, it is correct that the bright colors now become more chromatic.

This is because to get the luminance channel, the colors need to be converted to a opponent space (typically, xyY, for easy conversion). But, when dealing with 'hdr' colours, like (3.0, 2.0, 0), it is not just the brightness that is high, but also the chroma. When tone mapping in an opponent space, the chroma is untouched. This leads to overly chromatic colours near the bright highlights, and these chromatic colours differ per opponent color model:

However, we already have a solution to reduce chroma: chroma reduction gamut mapping. So if you apply that after applying the tone mapping, the chromatic highlights get fixed:

Is this better than per-channel tone mapping? I think it depends on the application. Gamut mapping can be quite slow, and isn't exactly shader friendly, so I can imagine why real-time applications (game engines), would prefer per-channel tone mapping (which more or less does its own form of gamut mapping). Meanwhile, the results of luminance channel tone mapping plus gamut mapping afterwards gives much more chromatic results, which might be more interesting for illustrative works.

Similarly, per-channel mapping only works in a RGB context, and Krita has more models than that to support. By doing our tone mapping in an opponent space, we get the same results regardless of what colour space the image is in, which should make it nice and predictable to work with.

This is one of the reasons that Krita's tone and gamut mapping filter share the same dialog (they can still be applied separately). The other reason is that we can reduce the amount of colour space conversions if we clump together the two transforms. Furthermore, experience tells me that illustrative artists tend to prefer a single filter here.

OCIO Lut baking

While I was pretty happy with the tone and gamut mapping filter, we were still missing something:

OCIO is the colour management library used by the vfx industry, and it's strength lies in a big portable configuration that can be much more easily designed that a library of icc profiles. Due this, a well made OCIO configuration often has its own tone mapping solutions, and it would be good if Krita could use these too.

The first thing to decide is what we're exactly baking. OCIO can be quite flexible, but the way it is implemented in Krita is that we have the standard pipeline provided by OCIO, where we…

1. start off in the assigned color space
2. go to the config's preferred linear color space
3. Apply the exposure.
4. Apply the looks.
5. Go to the display color space, apply the view transform.
6. Apply the channel swizzle.
7. Apply the gamma.

This made things a little tricky, as it is impossible to go from the display colour space back to the assigned image colour space. Furthermore, ideally we'd apply all transforms, including the view transform, so that we get an image that looks exactly like the one you see.

Initially I thought of reducing the scope, and creating a baking transform that applies everything in the config's preferred linear space, except the view transform. This didn't work out, as the gamma transform being applied linearly was too unintuitive.

So then, the next attempt was to apply the whole pipeline. This in turn means that the result is in the display color space. This too has some issues, as it requires the display space to be the exact same as the one selected in the preferences. Now, this is required anyway on wayland, as we have no way to determine from a given ocio display what we need to tag the wayland output as. But on the flip side, the default OCIO PQ transform is tied to 100 nits, and we do not yet have the ability to configure the nits level of Krita's rec2100 PQ surfaces, so the look will remain a little off when using HDR output until we do have that kind of support.

For this reason though, we ask whether you want to convert from the display colour space to the image colour space, or keep the display colour space. That way, the baked result can be quickly saved as an untagged image, like png, and then wrangled by some external script.

Above: Image baked with blender's current ocio config, using the sRGB display device and the 'aces 2.0' view transform.

We've had this "Baking" of the config on our wishlist since OCIO was first integrated, so I'm pretty pleased we managed to get it in, even though it still has some papercuts.

Further Work

So, right now, Krita has a built-in tone and gamut mapping filter, which works on luminance, and OCIO lut baking, where the tone mapping generally works per channel. Overall, the OCIO lut baking is probably going to be best for film workflows, while the built-in filter is going to be useful for non-ocio workflows, or when the artist prefers the more chromatic results of the built-in filter.

Because the colourfulness is going to be the key quality of the built-in filter, it'll be interesting to look at the other gamut mapping options, especially the adjustment-towards-the-cusp.

For CMYK workflows, the gamut mapping filter isn't too useful right now, as most artists work in sRGB, and the clipping errors towards CMYK there are very rare. Chroma compression might be interesting to experiment with here, but that requires generating a histogram of the chroma over hue, and I'll need to figure out how to do that while keeping the UI performant.

The built-in filter also doesn't have adjustment layers enabled just yet. This is because once we allow it as an adjustment layer, we'll need to always support it. And because there's a ton of tone-mapping curves out there, and I want to have a period of experimentation before we commit to a particular set.

In the future, I might need to seriously look at splitting up the gamut and tone mapping filters. Benefits here are for example allowing per-channel filter anyway (which is now impossible because the filter tries to find a space that can both gamut and tone map). From further experimentation, I get the feeling that the desaturated results I got tie in strongly with the configuration of the curve, so with a user configurable curve it might get better results. Other things to consider is to allow other models for tone mapping besides LAB and xyY, as that leads to different chromatic colors being applied. At the same time, I don't want to make this initial filter too complicated.

There's also some image-aware tone mapping techniques out there. I haven't investigated them enough though, so I have no idea if they're useful for Krita's purposes.

As for which of these is the correct one? That depends on the artist. Tone and gamut mapping are generally considered to be artistic operations, because there's always trade-offs and only the artist can tell which trade-offs and qualities are acceptable. Hence why I am trying to find a good set of tools for artists to work with.

Appendix

Manually tone mapping.

So, you can sort of manually tone map in Krita, because it supports unbounded workflows. It is a little annoying however, with some pitfalls.

Firstly, you will want to take an HDR image, and scale it's range into a [0 1] range. You do this by first color picking or using the HDR metadata tab to find the brightest pixel.

Then, you go into the select-a-color dialog by clicking the dual color button at the top. There, you type in the brightest channel value into each channel input. With your HDR color in hand, create a new layer, and fill it with this color. Then set the layer's blending mode to "divide". Now the whole image is in a [0 1] range. Then, you can either use the color adjustment filter or the levels filter to make everything visible again, but you will need to use the RGB adjustment, and not the lightness one, as the later goes through lab, and somehow that means everything gets desaturated.

This generally desaturates the whole image a little, as it is a form of per-channel tone mapping, so I personally pump up the saturation after my levels corrections.

The other pitfall here is that it becomes really hard to get a good curve the higher the brightest white is, because the curve needs to be fine-tuned more and more to both get nice shadows and nice highlights at the same time. The tone mapping filter is easier to use, in this case.

10 Nov 2026 10:56am GMT

Tagoross released AI Openness: How The Terms Relate, package 3 of 5. Its document and diagram show how AI openness terms differ, conflict and build on each other. It helps non-experts evaluate vendor lock-in and sovereignty risks of AI models.

10 Nov 2026 7:00am GMT

Today KDE releases a bugfix update to KDE Plasma 6, versioned 6.8.3.

Plasma 6.8 was released in October 2026 with many feature refinements and new modules to complete the desktop experience.

This release adds two weeks' worth of new translations and fixes from KDE's contributors. The bugfixes are typically small but important and include:

View full changelog

10 Nov 2026 12:00am GMT

09 Nov 2026 4:27pm GMT

This year we again participated in Google Summer of Code and we had 11 successful projects.

These are the projects that were completed successfully:

Drawy

Drawy lets you create ideas, diagrams, and visual notes on an infinite whiteboard with a smooth and responsive canvas.

• Abdelhadi Wael implemented the support for Rich Text as part of the Google Summer of Code. His work has been merged to master.

join.kde.org

One of the current KDE Goals is to improve the long term sustainability of KDE by recruiting and keeping more newcomers.

• Ansh Singhal worked on creating a new website which would be the KDE's primary contributor entry point and central hub, routing users to the right resource. The website is not officially published but its source code can be found here.

Lokalize

Lokalize is the localization tool for KDE software and other free and open source software. It has been improved a lot during last months to provide new features for translators.

• Navya Sai Sadu worked on redesigning Lokalize's Translation Memory Tab to help translators use it. Multiple reworks such as integrating the TM Manager into the TM Tab, enabling multi-TM selection and modifying search query in TM Tab to use the selected TMs were done and are still waiting to be merged MR.

Okular

Okular is KDE's universal document viewer and Poppler is a PDF rendering library it uses.

• Ojas Maheshwari implemented font subsetting in Poppler.

Instead of embedding the full font file inside the PDF whenever adding an annotation or filling a form, we subset the font file to get a newer version containing only the required mappings and embed that. This makes the file much smaller saving space on disk.

KStars

KStars is the KDE astronomy software providing an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. KStars also helps astrophotographers point and adjust their telescopes and photographic equipment to take the best astronomical pictures through a framework called Ekos.

• Pavan Kumar S G added an AI guiding assistant to Ekos that learns the systematic error signature of the user's own mount and issues predictive, feed forward corrections alongside the existing guider.

Marknote

Marknote is a rich text notebooks organizer.

Prayag Jain introduced a robust, commonmark compliant block editor inspired by popular editors like Notion.

digiKam

digiKam is an advanced open-source digital photo management application which provides a comprehensive set of tools for importing, managing, editing, and sharing photos and raw files.

Srirupa Datta added a natural-language input to digiKam's Advanced Search so users can describe queries such as "landscape photos with red labels taken in Paris last summer," which will then be converted into editable search criteria such as tags, labels, dates, and locations.

Kdenlive

Kdenlive is a free and open source video editor created by KDE contributors that let's you cut, and edit your movies, documentaries and family videos.

Yash Bavadiya worked on improving the effect widget system, which covered replacing the channel dropdown with a tab-based interface so each color channel (RGB, Red, Green, Blue, Alpha, Luma) has its own independent curve; building a standalone gradient widget with support for arbitrary draggable color stops; adding bezier curve handles to the time remapping panel so speed transitions can ease in and out smoothly.

KeepSecret

KeepSecret is a password manager for viewing, editing, creating, or deleting passwords.

Roshani Kumari worked on improving the user experience and adding new features such as import/export of passwords, adding a built-in password generator, and much more.

Mankala

Mankala is a two-player board game containing multiple variants.

Sayandeep Dutta developed a tournament interface for Mankala Engine, utilizing QXMPP to pair users and computerized opponents and create a leaderboard page to display rankings.

Sayandeep's implementation includes such fancy features as bots, in game chat and real-time voice chat.

Plasma Mobile

Tushar Gupta reworked networking modules (KCM) to make them more mobile friendly. Among other things, Tushar implemented the Wi-Fi connection configuration in QML; complete Wi-Fi security support, including enterprise networks; Wired and Hotspot connection configuration; and VPN configuration using QML.

Next Steps

The 2026 GSoC period is finally over for KDE. A big thank you to all the mentors and contributors who have participated in GSoC! We look forward to your continuing participation in free and open source software communities and in contributing to KDE.

---

Help Fund Further Development

You too can support KDE software development. Donate to our fundraiser and help our community thrive!

09 Nov 2026 12:00am GMT

Chessament 1.0.0 has been released. Chessament is a chess tournament manager. It supports individual Swiss-system tournaments.

Chessament allows to run a full tournament, from registering the players to calculating the standings. To ease the entering of players you can use the rating list of the International Chess Federation.

Chessament aims to be backwards compatible with tournaments created with previous versions of the program as long as possible.

Packagers

The package is available on download.kde.org and it's signed with my PGP key.

Binary releases for Windows and Linux (as Flatpak) will be available soon.

08 Nov 2026 3:00pm GMT

I am happy to announce that Dolphin has a new view mode: Columns. Each column shows one folder. Select a folder and its content opens in the next column, so the path from the folder you opened down to your selection stays on screen. This layout is known as Miller columns, after Mark S. Miller, who created it in 1980.

It is now in the master branch of Dolphin, not yet in Dolphin 26.12. We can still bring it into 26.12 until November 12th, if the testers find it ready. Otherwise it will ship in Dolphin 27.04. Either way it needs testers, so read on.

A bit of history

Dolphin had a column view from KDE 4.0, built on Qt's QColumnView. When Peter Penz moved the views to the new KItemViews engine for Dolphin 2.0 in 2011, the column view was not ported, and it was gone. Bug 387455, "Column view in Dolphin", was opened in 2017. With 32 people in CC, it has been one of the most requested features. It is now closed.

Sebastian's start

In February 2026 Sebastian Englbrecht opened MR !1185, a first Miller columns view built on KItemViews. After a few weeks of review he handed it over to me, and I continued it until MR !1524 was merged. He wrote:

Yeah, thank you very much meven for taking this to and over the finish line. I came to my limits and wouldn't have been able to polish it this well.

Thank you Sebastian, without your first version this would not exist.

What it does

• The folder that you open is the first column. Up, Back and the breadcrumb add its parent in front.
• A folder or an archive that you select opens the next column. Left, Right and Return move between the columns.
• The location bar, the window title, New Folder, Paste and the terminal panel follow the last column.
• Columns fit their content by default, or use a fixed width. Drag a handle to resize a column, double click it to fit the columns.
• Sort, grouping, hidden files, zoom and previews apply to every column, and a restored session brings back the open columns.
• Ctrl+4 switches to the mode, and Settings > View > Columns has its options.

The Columns mode is in the Dolphin application only for now. Konqueror and other apps that embed Dolphin's file view do not offer it yet.

The testers

The view behaves the way it does because people tried it and told us what was wrong, in more than 600 comments. Lluc Pallejà tested nearly every interaction and filed over a hundred comments with screencasts. Nate Graham did the UX review. Roke Julian Lockhart Beedell, Alexander Wilms, Karol, Kai Uwe Broulik, Leopold Luley, Akseli Lahtinen, Felix Ernst, Blenux, Ke, Linux ForAll and others found bugs and argued the details. Kudos to all of you.

Please test it

Whether the view goes into Dolphin 26.12 is decided on November 12th, see the KDE Gear 26.12 schedule. Until then, it needs people using it on their own folders, with their own habits.

On Arch Linux, the dolphin-git package from the AUR builds Dolphin from master. On any distribution, kde-builder can build it:

kde-builder dolphin
kde-builder --run dolphin

If your distribution ships a recent KDE Frameworks, as Arch Linux or Fedora do, add --no-include-dependencies to build Dolphin alone. Then switch to Columns with Ctrl+4.

Try your daily navigation, the keyboard, long names, large or remote folders, drag and drop, and resizing the window. Tell us also how it feels that the first column is the folder that you opened, as reviewers disagreed on this.

Please report bugs in the view-engine: columns mode component of Dolphin, with the steps and a screenshot or screencast when you can. General impressions are welcome in the comments of this post.

That's all, folks.

08 Nov 2026 2:25pm GMT

Eike's lovely new terminal Kwi depends on the latest releases of ghostty-vt library. This means you should probably build it yourself as distros will often be slower than Eike. :)

Ghostty is written in Zig, but it supports cmake and is, therefore, buildable by kde-builder, just add the following lines to your kde-builder.yaml:

project ghostty:
repository: https://github.com/ghostty-org/ghostty.git

It surprises me how many non-KDE projects I have in my kde-builder.yaml every time I open it.

08 Nov 2026 1:49pm GMT

The last maintenance release of the 26.08 series is out with the usual batch of stability fixes and workflow improvements. Project management is more robust, with improvements to recovering corrupted projects, autosave behavior, and handling of archived projects. Other highlights include fixes to several crashes and freezes, keyframe copying, custom effects and improved undo/redo performance.

Under the hood, we fixed compatibility with Qt 6.12 and added improvements to the regression test suite and packaging build-related fixes. This version also includes a fix on MacOS for a Qt related startup crash triggered by the latest MacOS updates.

Kdenlive needs your support

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

For the full changelog continue reading on kdenlive.org.

07 Nov 2026 9:10am GMT

Make sure you commit anything you want to end up in the KDE Gear 26.12 releases to them

Next Dates:
November 12, 2026, 23:59 UTC: 26.12 Freeze and Beta (26.11.80) tarball creation
November 13, 2026: 26.12 Beta (26.11.80) release
November 26, 2026, 23:59 UTC: 26.12 RC (26.11.90) tarball creation
November 27, 2026: 26.12 RC (26.11.90) Release
December 3, 2026, 23:59 UTC: 26.12 tarball creation
December 4, 2026: 26.12 packages released to packagers
December 10, 2026: 26.12 Release

https://community.kde.org/Schedules/KDE_Gear_26.12_Schedule

07 Nov 2026 8:22am GMT

Welcome to a new issue of This Week in Plasma!

This week many widgets shipped with Plasma got quite a bit of polish. Feature work and performance work were also notable this week… really, a bit of everything! Have a look:

Notable new features

Plasma 6.9

There's a new picture of the day wallpaper plugin that displays art made by noted FOSS artist David Revoy. (Guillermo Villafuerte, kdeplasma-addons MR #1150)

You can now choose the position of OSD popups on the screen, if the default position doesn't work for you. (Mathias Schuh, KDE Bugzilla #501654)

Running systemd-ask-password --no-tty in systemd-257 or higher now shows a nice KDE-style password prompt. (Daan De Meyer, plasma-workspace #6433)

Plasma Browser Integration now supports the Glide browser. (Jan Buchar, plasma-browser-integration MR #178)

Notable UI improvements

Plasma 6.6.8

You can now click to focus the Calculator widget and then interact with it using the keyboard as expected. (Christoph Wolk, kdeplasma-addons MR #1191)

The Media Frame widget now changes the image displayed in its compact form immediately when the slideshow displayed in the popup advances to the next image, rather than after a delay. (Christoph Wolk, kdeplasma-addons MR #1199)

Plasma 6.8.3

Opening the font dialog from the Digital Clock widget now pre-selects the currently-used font. (Niccolò Venerandi, plasma-workspace MR #7348)

Plasma 6.9

Widgets added to the desktop are now created at a size that makes them large enough to be useful without any cut-off content. (Felix Desyatirikov, plasma-workspace MR #7342 and bluedevil MR #274)

Spinning a mouse wheel over a scrollable horizontal row of Task Manager thumbnails now scrolls them, as expected. (Christoph Wolk, KDE Bugzilla #448504)

The way multiple panels interact with one another at screen corners has been improved in a variety of ways. (Niccolò Venerandi, plasma-workspace MR #7330)

Multiple graph styles used in System Monitor widgets are now presented in a nicer and more appropriate way when used on a panel. (Niccolò Venerandi, libksysguard MR #498)

New

Old

The Calculator widget now animates the buttons being pressed when you interact with it using the keyboard rather than the pointer. (Christoph Wolk, kdeplasma-addons MR #1190)

The Dictionary, Disk Quota, and Konsole Profiles widgets now use up-to-date behaviors and styling for their list views. (Christoph Wolk, kdeplasma-addons MR #1192, kdeplasma-addons MR #1193, and kdeplasma-addons MR #1220)

Launcher menus now use "natural sorting", meaning something like "Transformers 10" is shown after "Transformers 9", rather than after "Transformers 1". (Peder Bergan, KDE Bugzilla #524466)

Searching for a keyboard layout on System Settings' Keyboard Layouts page now works a lot more intuitively. (Tobias Fella, plasma-desktop MR #4060)

You can now use the "Forward" button on your fancy mouse to trigger actions on the desktop. (Niccolò Venerandi, KDE Bugzilla #494216)

You can now open the clipboard settings from its Meta+V popup, just like you already can from its panel widget popup. (Kai Uwe Broulik, plasma-workspace MR #7345)

Frameworks 6.32

When using a non-integer scale factor, icons throughout Plasma and Kirigami-based apps are now a little bit less blurry and pixelated, and also don't wiggle around so much while their parent window is being resized. (Arjen Hiemstra, Ilya Fedin, and Eike Hein, KDE Bugzilla #522336, KDE Bugzilla #527335, and kirigami MR #2225 respectively)

Notable bug fixes

Plasma 6.6.8

Keyboard navigation within the list of timers in the Timers widget now works as expected. (Christoph Wolk, kdeplasma-addons MR #1247)

The "Timer finished" message you can configure the Timer widget to show is no longer hardcoded to English by default. (Christoph Wolk, KDE Bugzilla #413374)

Plasma 6.8.3

Fixed a recent regression that made KWin crash when a DisplayLink screen was connected. (Xaver Hugl, KDE Bugzilla #527984)

Fixed a case where System Monitor could crash when you scrolled around after killing some processes. (Arjen Hiemstra, KDE Bugzilla #502879)

Plasma no longer lets you use scripting to set a panel's spacing value to 0, since that would make Plasma freeze when its widgets were dragged to rearrange them. (Niccolò Venerandi, KDE Bugzilla #528228)

Using the Pager widget's "Selecting current virtual desktop: Shows the desktop" setting no longer triggers rapid flashing when you scroll over it. (Niccolò Venerandi, KDE Bugzilla #471241)

Using the Minimize All widget to minimize and then restore all windows now restores focus to the previously-focused window as well. (Niccolò Venerandi, KDE Bugzilla #450137)

Fixed an issue that could make icon positions sometimes get scrambled on multi-screen setups when one screen was disconnected at the same time as another one was connected. (Błażej Szczygieł, plasma-desktop MR #4163)

Fixed an issue that could break the layout on System Settings' Display Configuration page if you used it to turn off a screen and then immediately reverted that change. (Błażej Szczygieł, KDE Bugzilla #527131)

Timers saved in the Timer widget can once again be dragged around to re-order them. (Christoph Wolk, kdeplasma-addons MR #1224)

Plasma 6.9

Fixed an issue that could freeze an RDP stream initiated from the very confusingly-named "Windows App" RDP client app for macOS. (Chris Maria, krdp MR #289)

Opening the color dialog from the Color Picker widget no longer makes Plasma freeze while it's open. (Madhur Dhillon, KDE Bugzilla #525094)

When the Timer widget is placed in a vertical panel, it no longer acts as a trap for the Up and Down arrow keys when focusing widgets with the keyboard. (Christoph Wolk, kdeplasma-addons MR #1225)

Rapidly clicking on the "Previous Image" and "Next Image" buttons on the Media Frame widget no longer sometimes tries to open the current image in an external app. (Niccolò Venerandi, KDE Bugzilla #371832)

Notable in performance & technical

Plasma 6.8.3

Spectacle's "background mode" feature is now a little bit faster to launch and consumes less memory. (Frog Chen, spectacle MR #621)

Plasma 6.9

Plasma no longer leaks a little bit of memory when you right-click on files or folders on the desktop. (Zühtü Eren İncekara, plasma-desktop MR #4152)

Fixed a couple of memory leaks in System Monitor. (Méven Car, libksysguard MR #479)

Spectacle is now faster to launch in general. (Kai Uwe Broulik, spectacle MR #618, spectacle MR #619, and spectacle MR #620)

System Settings' Accessibility page is now much faster to load. (Tobias Fella, plasma-desktop MR #4183)

System Settings' Spell Check page was ported to Qt Quick, giving it a more modern UI and opening the door for faster and easier future improvements. (Tobias Fella, plasma-desktop MR #3975)

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.

KDE's annual fundraiser has raised 35% of the funds we're hoping for, but with two months left in the year, we need your help to get it over the finish line! If you can, consider making a donation.

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.

07 Nov 2026 12:00am GMT

Here's the data!

A script element has been removed to ensure Planet works properly. Please find it in the original post.

Thank you all for filling the survey I mentioned in my other post here. We got 1518 full responses total, which is a lot!

Without further ado, here's the data in charts.

FYI: I am not a data scientist, just a random guy trying to piece up something.

General usage statistics

First I want to go through some general usage stuff.

What is your desktop icon usage like?

In general, people tend to actually not use them much. They still may have some icons, but they get mostly ignored.

A lot of people use the desktop as a place to store temporary files they're working on, then presumably move them somewhere else when done with them. As a to-do list of sorts.

Then there's shortcuts to applications people use a daily.

Lastly, not as many store files on desktop regularly.

So to me it seems that people ignore them most of the time, but use them as shortcuts for apps to do work, or just need a temporary place for something they're working on.

Note that this was a multichoice question. I allowed people to pick "I don't really use desktop icons", because I believed all these could be true at the same time: People don't necessarily think about them often, but they use them.

Raw data

What is your desktop icon usage like?	Count
I add shortcuts to applications I use daily	394
I use desktop as a temporary place for things I'm actively working on	649
I store files on my desktop regularly	259
I don't really use desktop icons	819

Average desktop icon amount

I calculated the average of the icon values, and it seems the average of everyone is 9 icons on desktop.

There were some people typing in 128937128973987 or similar so I removed those. Sorry, I don't believe you! Send me proof!

But the largest amount I'm willing to believe was 150 icons. That's a lot!

Automatic or manual sorting?

This is surprisingly even. I expected way more people move icons around, but it's literally 60/40 situation.

Raw data

Do you use automated arrangement or position the icons manually?	Count
Automatic	605
Manual	913

Icons on side of monitor when screen changes

Here's the real juicy parts: How do we want icons to behave when something happens?

When icons are placed on the side of the monitor, and screen resolution changes, we did not really know what users want the icons to actually do.. Until now!

The survey had users to make choice between example images. I have added the images here as a refresher.

Monitor resolution expands

Leave icons at current position.

Move icons to the new resolution.

Overwhelming majority of you want the icons to move to the new resolution and not stay in the current position, which I find interesting, as some might find that a bit jarring! But in a way, it makes sense.

Raw data

Monitor resolution expands.	Count
Leave icons at current position	244
Move them to the new resolution	1274

Monitor resolution shrinks

Rearrange icons to fit the new resolution in their original form.

Rearrange them automatically to new position, from start.

This had even more overwhelming majority! Only 71 of you want the automated arrangement. So this preference is quite clear!

Raw data

Monitor resolution shrinks.	Count
Rearrange icons to fit the new resolution in their original form	1447
Rearrange them automatically to new position, from start	71

Monitor resolution shrinks, but the area where you move new icons has already some icons

Move all icons, to make room for the others.

Rearrange them automatically to new position, from start.

Here 1/3 of the people wanted them to be automatic and start over from the beginning. Moving all icons makes sense, but I think it's going to be more difficult to make and more bug prone.

Raw data

Monitor resolution shrinks, but the area where you move new icons has already some icons.	Count
Move all icons, to make room for the others	1052
Rearrange them automatically to new position, from start	466

Desktop is full of icons

You have added so many files on the desktop that it's full, then you add some more! We wanted to know what should happen in this case.

Add a scrollbar so you can scroll for more icons!

Tell user the desktop cant show more icons, but they can be found from Desktop folder.

Show user an "overflow menu" that has the icons that do not fit inside a popup.

Most of you seem to want the popup, which makes sense as this is very much what happens on mobile: When there's a lot of icons on the screen, and you try to add more, they turn into folders instead.

I was surprised the scrollbar was the second choice, as that's already what happens on Plasma, and I have heard so many times that it's confusing.

My personal favorite, the warning, is at third. It's my favorite because it's the least complex. :)

Raw data

How should the desktop adapt?	Count
Add a scrollbar so you can scroll for more icons!	467
Tell user the desktop cant show more icons, but they can be found from Desktop folder.	309
Show user an "overflow menu" that has the icons that do not fit inside a popup	742

Monitor is changed to vertical mode

A usecase I very rarely encounter, but felt like we should look into anyway.

Keep icons where they are, just rotate them in place.

Rearrange icons so that they are somewhat close to the original arrangement.

Most of you want a rearrangement, though rotating in place seems to fit many as well. I would prefer rotating in place as implementor as it's the simplest, since we do not have to relayout everything.

Raw data

How should icons on your desktop adapt to rotating your screen?	Count
Keep icons where they are, just rotate them in place	557
Rearrange icons so that they are somewhat close to the original arrangement	961

Monitor disconnection

This is one of the most difficult ones to solve, as screens often behave weirdly when plugged/unplugged. Sometimes we do not know fully if the screen is ready or not, reporting back weird resolution, etc..

As a note for this question, the reverse would happen: The icons would be back on the reconnected screen.

They move to the remaining screen.

They aren't visible on the remaining screen.

I was expecting most to vote for the moving to the remaining screen, and I was right! However, I did not expect it to be this small divide.. A lot of you are fine with the icons not showing on the remaining screen!

Raw data

What should happen to the icons on that screen?	Count
They aren't visible on the remaining screen	626
They move to the remaining screen	892

Conclusions

Most of these things are what I expected, though I did not expect as much divide: I was expecting 90/10 divisions, not 60/40!

But thank you all for answering to the survey. I will have to properly mull over and plan now with all this data in my hands.

Note that this data does not decide anything, but it works as a guidance for us.

There's a lot of writing for me to read about the icons, so I will go through that over time. But thank you for these responses, as it will help us KDE folk figure out how to fix the desktop icon situation, as it's still bit flakey.

No promises when, but I want to get into it when I have gotten more Union bug fixes done.

Thank you again! Your help has been very valuable. <3

ps. Hope you don't mind my crappy charts. I am using chartjs for it, but if you have javascript off, you should see the images I took instead.

A script element has been removed to ensure Planet works properly. Please find it in the original post.

06 Nov 2026 7:52pm GMT