Welcome Kaidan 0.15.0! This release adds experimental support for calls. In addition, it contains some very useful improvements and lots of fixes.

Most of the work has been funded by NLnet via NGI Zero Entrust and NGI Zero Commons Fund with public money provided by the European Commission.

Audio/Video Calls

Kaidan has supported voice and video messages for a long time. Starting with this release, you can even have an audio or video call with a contact! An incoming call is indicated via a notification and you can either accept or reject it.

Please note that there are still some features missing and some setups may not work properly. Especially, calls are only supposed to work on Linux at the moment. But wee wanted to share the current achievements with you to get some feedback! Our goal is to extend the A/V calls functionality and make it available on other operating systems in the future.

Notifications for Group Chat Replies

Formerly, you got a notification if someone mentioned you in a group chat while the corresponding setting was enabled. But you could miss replies to your messages. Kaidan notifies you now on receiving replies as well.

Message Input Field Focusing

In contrast to the soft keyboard on a mobile device, which needs to be opened each time you want to enter something, your keyboard is always reachable on a desktop device. Why not make use of that circumstance? Kaidan ensures that the most relevant message input field stays focused to allow entering text without an additional click into the corresponding field. That way, you can interact smoothly with the user interface and be more productive.

Advanced Message Highlighting

Kaidan 0.14 introduced highlighted messages if you opened their context menu. Messages are now also highlighted while they are being corrected or while you are choosing emojis to react to them. If another message was already highlighted before, that message is highlighted again once you sent the correction/reaction.

Integrated Search Field

With Kaidan, you can quickly search for chats and messages. But while searching for messages, the opened search bar reduced the space for messages. On mobile devices, the search bar even consumed unnecessary space within the chat list. Both problems are solved now! The search field is integrated into the main toolbar above the messages resp. the chat list. You can even focus each search field via an own keyboard shortcut to directly search without moving the cursor.

Password Manager Fallback

Since Kaidan’s last version, passwords are stored in a password manager if the system provides one. But there was no fallback yet. It is now possible to use Kaidan even if no password manager is available. In that case, the passwords are stored in an unencrypted file. Once Kaidan detects a password manager on start, the unencrypted passwords are automatically migrated to the password manager.

Changelog

There are several other improvements. Have a look at the following changelog for more details.

Features:

• Add support for audio/video calls (XEP-0166: Jingle, XEP-0167: Jingle RTP Sessions, XEP-0176: Jingle ICE-UDP Transport Method, XEP-0215: External Service Discovery, XEP-0320: Use of DTLS-SRTP in Jingle Sessions, XEP-0353: Jingle Message Initiation) (@melvo)
• Show busy indicator while saving captured image/video data (@melvo)
• Notify on receiving reply to own group chat message if ‘On mention’ notification setting is enabled (@melvo)
• Select file after opening in folder on Linux if supported (@melvo)
• Improve media capturing look/behavior (including preview after capturing image until image is saved) (@melvo)
• Restore focusing of last focused user interface elements (especially message input field) for various use cases (@melvo)
• Keep message bubble highlighted on reacting/correcting (@melvo)
• Allow to select message for correction via Ctrl+Up/Ctrl+Down (@melvo)
• Integrate search field into main toolbar increasing space for messages and, on mobile devices, even for chats in chat list (@melvo)
• Show message search field via Ctrl+Shift+F (@melvo)
• Display toolbar buttons on mobile devices exactly as on desktop devices (@melvo)
• Hide horizontal separator above top-most chat unless chat list is scrolled (@melvo)
• Store passwords in unencrypted file if no password manager is available or corresponding command-line option provided (@fazevedo)
• Migrate unencrypted passwords to password manager if available on start (@fazevedo)

Bugfixes:

• Fix overlapping message bubble tail (@melvo)
• Fix medium preview hovering if hidden drop area info is hovered (@melvo)
• Fix updating OMEMO 2 keys for all use cases (@melvo)
• Fix deadlock on logout during upload of multiple files (@melvo)
• Fix creating additional database connection on wrong thread (@melvo)
• Fix sending/resetting whether message is being composed for various corner cases (switching chat, logging out, disabling corresponding setting) (@melvo)
• Fix updating last message on receiving initial message after setting up existing account in Kaidan for first time (@melvo)
• Fix resetting draft message after canceling message correction (@melvo)
• Fix resending failed message reaction (@melvo)
• Fix selecting previously selected message after changing reactions (@melvo)
• Fix restoring message highlighting and cancel ongoing correction/reply on removing corresponding message (@melvo)
• Fix displaying last message sender in chat list after draft message removal (@melvo)

Notes:

• Kaidan requires Kirigami Addons 1.8 now
• Kaidan requires QXmpp 1.14 now

Download

• Source code (.tar.xz) (sig signed with 04EFAD0F7A4D9724)
• Linux (Flatpak on Flathub)

Or install Kaidan for your distribution:

The docs-kde-org project currently relies on an old, hard forked version of dblatex, which is bundled directly within the repository. This makes maintenance difficult.

What’s dblatex?

From the man page: dblatex is a program that transforms your SGML/XML DocBook documents to DVI, PostScript or PDF by translating them into pure LaTeX as a first process. MathML 2.0 markups are supported, too. It started as a clone of DB2LaTeX.

My task is to swap the bundled dblatex with the one present in the upstream repos and make the PDF generation work reliably. Then switch the rendering backend from pdfLaTeX to XeLaTeX to support native unicode (to fix rendering issues for languages like Arabic, Chinese, Japanese, Korean, etc).

If that doesn’t work out, I’ll extract the dblatex fork into its own repository to ease maintenance.

Checkpoints to achieve

• Swap our current fork and use the latest upstream version. Also compare these two.

• Migrate from pdfLaTeX to XeLaTeX

• Verify our fixes and confirm if all the PDFs are being generated properly.

I’ll be sharing my progress and struggles (setting this website up was probably a struggle in itself) from time to time as I start this project. This work is part of Season of KDE, mentored by Johnny Jazeix.

We are happy to announce the release of Qt Creator 19 Beta!

You find a selection of improvements and fixes below. Please have a look at our change log for more detailed information.

I have a pile of hard drives. 3.5” Spinning rust. There’s like a dozen of them, some labeled cryptically (EBN D2), some infuriatingly (1) and some not-at-all. Probably most of them work. But how to effectively figure out what is on them? FreeBSD to the rescue.

Hotplug Just Works

All the drives are SATA. I do have an IDE drive, I use it for opening beer bottles. And an ST-225 for old-time’s sake. But SATA it is, and there’s spare SATA data- and power-cables dangling out the side of my PC. This particular machine runs FreeBSD 14.3, and connecting a drive (data first, then power) yields some messages in the system log. Old-school, the command to read these is still dmesg, which prints:

ada3 at ahcich0 bus 0 scbus0 target 0 lun 0
ada3: <WDC WD3200AAKS-00SBA0 12.01B01> ATA-7 SATA 2.x device
ada3: Serial Number WD-WMAPZ0561055
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 305245MB (625142448 512 byte sectors)

That matches information printed on the label of the disk (this drive is from 2007, has a 1 written on it in black marker – it may have been a drive in the English Breakfast Network server back then). It also tells me that the disk is registered with the system as ada3.

FreeBSD’s disk subsystem is a stack of “GEOM classes”. The geom(4) manpage tells me that it is a modular disk I/O request transformation framework, but the important bit is geom(8), the command to query the disk subsystem. Running geom disk list ada3 tells me what is known about disks involved with ada3. This actually doesn’t tell me much I don’t already know:

Geom name: ada3
Providers:
1. Name: ada3
   Mediasize: 320072933376 (298G)
   Sectorsize: 512
   Mode: r0w0e0
   descr: WDC WD3200AAKS-00SBA0
   lunid: 50014ee0aabd8fe3
   ident: WD-WMAPZ0561055
   rotationrate: unknown
   fwsectors: 63
   fwheads: 16

Well, actually this tells me that the dmesg and geom output are in mibi- and gibi-bytes, and that they’re consistent. How about partitions on this disk, though? geom part list ada3 tells me (here I’ve removed several partitions, along with many other lines that are not very useful right now; the output is extensive):

Geom name: ada3
scheme: GPT
Providers:
1. Name: ada3p1
   Mediasize: 819200 (800K)
   efimedia: HD(1,GPT,a43a2da3-bb5f-11e5-8d81-f5e4d894ddb1,0x22,0x640)
   label: (null)
   type: efi
   index: 1
2. Name: ada3p2
   Mediasize: 315679277056 (294G)
   efimedia: HD(2,GPT,a43c9069-bb5f-11e5-8d81-f5e4d894ddb1,0x662,0x24bff9c0)
   label: (null)
   type: freebsd-ufs
   index: 2

So it is a GPT-partitioned disk, and at least one of the partitions is an “old-fashioned” UFS partition. That’s FreeBSD before ZFS became the de-facto standard filesystem (maybe just for me). This disk is simple to deal with (further notes below)!

After I’m done with the disk, I power it down first with camcontrol standby ada3. I can hear the disk stop spinning and then pull out the connectors (power first, then data). And move on to the next disk. After disconnecting, dmesg confirms that I unplugged the correct drive:

ada3 at ahcich0 bus 0 scbus0 target 0 lun 0
ada3: <WDC WD3200AAKS-00SBA0 12.01B01> s/n WD-WMAPZ0561055 detached
(ada3:ahcich0:0:0:0): Periph destroyed

This way I can step through all of the drives in my pile and then jot down what disk does what (or, in rare cases, decide they can be zeroed out and re-used for something else).

Dealing with non-GPT disks

The scheme reported by geom part list is GPT if you’re sensible, but of course it is possible to bump into MBR and BSD disklabels as well. The geom subsystem abstracts all that away, and the only realy difference is the names of devices.

Scheme BSD, also known as BSD disklabel, gives you ada3a and ada3d, rather than numbered partitions. It is possible to apply this to a whole disk. It is also possible to have a BSD disklabel inside an MBR partition, but that’s a late-90s kind of setup.

Scheme MBR gives you numbered partitions, but FreeBSD calls these slices instead of partitions and so you end up with ada3s1 instead of ada3p1.

Dealing with UFS

UFS partitions are pretty simple: mount them somewhere and things will be OK. I go for read-only, and I have a /mnt/tmp for all my arbitrary-disk-mounting activity. So mount -o ro /dev/ada3p2 /mnt/tmp it is (ada3p2 is the partition name found earlier).

This particular disk turned out to be my main workstation drive around 2017, with a handful of still-interesting files on it. Ones I would not have missed if I hadn’t looked, but it was nice to find a presentation PDF I gave to SIDN once-upon-a-time.

After looking, umount /mnt/tmp to unmount and release the disk. After that, power-down and disconnect as described above.

Dealing with ZFS

Slightly newer disks might be ZFS. Here’s the partition information for one:

Providers:
1. Name: ada3p1
   Mediasize: 250059309056 (233G)
   label: backup0
   type: freebsd-zfs
   index: 1

It’s a GPT partition with a label, and ZFS on it. That means it’s part of a ZFS pool, and is probably referred to within the pool by its label. Possibly by its ID. In any case, ZFS needs to be imported, not mounted, because the filesystems are contained as part of the storage pool. The command to discover what is available is zpool import , which doesn’t actually import anything.

   pool: zbackup
 config:
        zbackup        ONLINE
          gpt/backup0  ONLINE

That’s encouraging: the pool consists of a single drive and everything is online. To make the filesystems in this pool available, I need to import it. I’ll force it (-f, because it was probably untimely ripp’d from whatever machine it was in previously), without mounting any of the filesystems in it (-N), readonly (-o readonly=on) with a temporary name (-t zwhat), like so: zpool import -f -N -o readonly=on -t zbackup zwhat

After importing the pool, zfs list tells me what filesystems are available:

zwhat                       36.2G   189G    25K  /zwhat
zwhat/home                  36.2G   189G  36.0G  /tmp/foo/

I can mount a single ZFS filesystem just like a UFS filesystem. The ZFS filesystem knows where it would want to be mounted (/tmp/foo, I have no idea what I was doing back then), but we can treat it like a legacy filesystem: mount -t zfs zwhat/home /mnt/tmp

After looking, umount /mnt/tmp to unmount and release the disk. After that, power-down and disconnect as described above.

Dealing with Linux ext4

If the disk comes from a Linux machine, then it may have an ext4 filesystem on it. I still usually pick that when installing Linuxes. Here’s the partition information for one:

scheme: MBR
Providers:
2. Name: ada3s2
   Mediasize: 64428703744 (60G)
   rawtype: 131
   type: linux-data

There is ext4 support in the FreeBSD kernel, although it is named ext2 (and some ext4 filesystems use unsupported features, and then it won’t mount). But for simple cases: mount -o ro -t ext2fs /dev/ada3s2 /mnt/tmp does the job.

Dealing with linux-raid

I found two disks, both WD Caviar Blue, labeled EBN D1 and EBN D2 with similar layouts. Those are linux-raid disks, and this is something I can’t deal with in FreeBSD. Heck, I’m not confident I can deal with them under Linux anymore, either.

Providers:
1. Name: ada3s1
   Mediasize: 493928031744 (460G)
   efimedia: HD(1,MBR,0xa8a8a8a8,0x3f,0x398033d3)
   rawtype: 253
   type: linux-raid

Re-purposing Disks

KDE has a lovely partitioning tool, but I wouldn’t be me if I didn’t go for the command-line approach. Make sure the disk isn’t mounted anywhere, but is powered up.

Zero out the first gigabyte or so of the disk: dd if=/dev/zero of=/dev/ada3 bs=1M count=1024 I guess this isn’t strictly necessary, and geom warns during this operation that the GPT is corrupt and the backup GPT (at the other end of the disk) should probably be used. Ignore that.

Destroy the partition table some more: geom part destroy -F ada3 , now it is really dead.

Make a new GPT partition table on the disk: geom part create -s gpt ada3

Start adding partitions to the partition table. I (now) use labels with the last digits of the drive’s serial-number. This drive gets a gigabyte of swap (just in case) and the rest is a ZFS partition which I can add to a pool later.

• geom part add -t freebsd-swap -s 1G -l swap-159666 ada3
• geom part add -t freebsd-zfs -l zfs-159666 ada3

Why the labels-with-serial-numbers? Well, that’s so that I can subsequently create a ZFS pool from labeled partitions, and it remains obvious where the parts of the pool come from and also prevents name-collisions from naming everything backup0 and so.

I've been administering KDE's participation in the Google Summer of Code program for the last few years (and mentoring on some). This post is just some personal thoughts on the differences between what the KDE organization expects and what usually the applicants want (I'm not in everybody heads, it's assumptions from my experience). I don't provide any solution (because I don't have any) and there is no judgment (both point of views are valid), just a personal point of view.

Applicants point of view

GSoC is a individual competitive program which can be a huge boost to start a career. There are usually two major reasons for the applicants to participate in GSoC:

• the money.
• the experience and the line in the CV for real life work.

There is, for a lot of applicants, no genuine interest in the projects (at least at the beginning, the first interaction is often "I want to start contributing to KDE and prepare for GSoC"), and they mostly want a GSoC slot. Small digression, on one of my projects, two people already asked to contribute and if we were doing GSoC, but after telling them that contributions are welcomed and we will only propose a topic if we feel enough confidence that the contributor would stay after, they told us they preferred to choose another project.

Contributors consider GSoC as an end of their studies, not a project they want to contribute after: there is also a change of life to consider between university life and work life and a balance to achieve when starting the latter (which could be in a different town/country) which may be a reason for the drop of interest.

Organization point of view

GSoC is an opportunity to welcome new contributors to our community. The organization usually expects from GSoC:

• contributors willing to contribute regularly to their projects.
• implementation (partial or total) of the proposed ideas.
• having a positive return on investment (is the time spent mentoring worth the result?)

GSoC is mostly a step to have contributors learning about the projects, and contribute in the long-term. Long-term is purposely vague; what we expected for the GCompris project was the contributor would contribute at least one year and mentor for the next GSoC (so a loop was present, and applicants would also gain an experience on mentoring, while giving some relief to the other experienced mentors) but it can vary depending on the project.

For the return on investment, mentors do not consider it good having spent more than three months mentoring for projects they could have done in less time they spent to mentor the contributor. Helping someone grow is always personally rewarding but we still hope this person will also show us the results of the teaching by improving our projects in the future.

Impacts of the differences

There is a huge difference on the expectations. What can we do to reach a common ground where everyone is happy?

• Organizations cannot force anyone to contribute after the GSoC end.
• If money is the main motivation to stay, most organizations will not have money to hire applicants to work after (and do we want to hire someone only motivated by money? No, it's not OSS values, we love passion).
• Find ways to create a real interest for the organization. In KDE, we have the chance to have tons of projects with different topics (astronomy, education, digital painting, video editing, scientific plotting, games, desktop environment, system administration, internationalization, ...) where it is easy to participate to other projects from time to time and learn new things if we are curious enough.
• Be stricter on the entry point for organizations: explicitly say in the beginning that we expect a long-term relationship not just the equivalent of an internship. It should reduce the number of applicants and only keep the ones with a genuine interest (if applicants are honest of course).
• Organizations/Mentors could reduce their objectives of GSoC and consider that contributors are here to produce and spend less time on training/mentoring, expecting contributors already know the basics, but this would totally spoil the nature of the program.

Another track is to find the projects where contributors stay / don't stay and understand the difference. Most of the big KDE applications don't manage to keep their contributors, while smaller ones do. Maybe as a contributor, it's because it's more difficult to take decisions, feel included/listened on large projects because they have a high maturity level/long-term contributors and a well-defined vision? Whereas on smaller projects, there are fewer constraints from the existing environment and it feels more rewarding and motivating to contribute there?

To conclude, here are the statistics for KDE retention the last years:

That is, an average of 15 people sign up each year, of which

• an average of 90% finish
• 44% continued contributing 1 year later
• 28% continued contributing 2 years later
• 22% continued contributing 3 years later

We would of course love having more contributors staying at least one year but it's almost half and a quarter that stay active for a few years!

Today we're releasing Krita 5.2.15. This is a bug fix release with a number of crash fixes and workarounds to improve use with the Xiaomi Pad.

Changelog

• Fix crash when using a smudge brush (Bug 512243)
• Update GMic to 3.6.4.1 in krita/5.2 branch
• Fix crash when undoing liquefy (Bug 498696)
• Fix crash when an embedded profile is faulty (Bug 509875)
• Fix loading of TIFF files with JPEG compression
• Force SVG gradients to work in premultiplied alpha mode, counter to specification (Bug 502118, more info in commit)
• Fix Transform and Move shortcuts conflicting Timeline arrow key actions (Bug 513855)
• Don't compress touch events matched to shortcuts
• Treat 3+-finger-touch cancels as ends (Bug 510993)
• Prevent rotation notice jitter around zero
• Allow combining zoom and rotation popup messages
• Disable context menu on overview widget (Bug 514238)
• Make touch scrolling not trigger menu (Bug 513413)
• Xiaomi stylus button and curve fixes (handle pageup and down) (more info in commit )
• Steeper tablet curve for Xiaomi devices (more info in commit)
• Don't flicker window on Xiaomi devices
• make xcodebuild an archival build to avoid unwanted debug entitlements.

Download

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-5.2.15-setup.exe
• Portable 64 bits Windows: krita-5.2.15.zip
• Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with 5.2.11, the minimum supported version of Ubuntu is 22.04.

[!WARNING] Starting with 5.2.11 has updated the AppImage runtime, which is known to be incompatible with the old versions of AppImageLauncher. Developers of the AppImage runtime suggest to remove or update AppImageLauncher. See this report: Issue 121 More AppImage troubleshooting info is available here: FUSE

• 64 bits Linux: krita-5.2.15-x86_64.AppImage

MacOS

Note: We're not supporting MacOS 10.13 anymore, 10.14 is the minimum supported version.

• MacOS disk image: krita-5.2.15.dmg

Android

We consider Krita on ChromeOS as ready for production. Krita on Android is still beta. Krita is not available for Android phones, only for tablets, because the user interface requires a large screen.

• 64 bits Intel CPU APK
• 64 bits Arm CPU APK
• 32 bits Arm CPU APK

Source code

• krita-5.2.15.tar.gz
• krita-5.2.15.tar.xz

md5sum

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

Key

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

This is second beta of Plasma 6.6, which includes several bugfixes before final release on 17th February 2026.

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

• plasma-login-manager
• plasma-keyboard
• plasma-setup

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

We are happy to announce the release of Qt Creator 18.0.2!

This release fixes a range of smaller issues like the persistence of the "Always save files before build" option and an issue that occurred when using some custom toolchains with vcpkg. It also updates the wizard templates for the Qt Safe Renderer.

Welcome to a new issue of This Week in Plasma!

This week the Plasma team focused almost entirely on bug fixing. And let’s let the results speak for themselves: we fixed 18 high and very high priority Plasma bugs, or 28% of all open ones! Lots of polishing for Plasma 6.6 to make it a great release.

Notable New Features

Plasma 6.7.0

Added a dedicated setup UI for configuring shared printers on Windows networks. (Mike Noe, KDE Bugzilla #406211)

Notable UI Improvements

Plasma 6.6.0

Desktop switching and Present Windows shortcuts now use the Meta key by default for more consistent system-wide behavior. (Antti Savolainen, kwin MR #8597)

Plasma can now report printers’ waste receptacle levels and notify users when they fill up. (Mike Noe, KDE Bugzilla #514525)

KRunner’s buttons have been reorganized to be consistent with other Plasma widgets, making the interface feel more familiar and coherent. (Taras Oleksyn, plasma-workspace MR #6203)

Plasma 6.7.0

System Settings’ Wi-Fi & Networking page now uses clearer Wi-Fi security labels, correctly showing WPA2 and WPA3 support for both Personal and Enterprise networks. (Lynne Megido, KDE Bugzilla #493238)

There are now keyboard shortcuts for switching virtual desktops and opening the Present Windows effect that use the Meta key, to be consistent with other globally-scoped keyboard shortcuts. (Antti Savolainen, KDE Bugzilla #508187)

Frameworks 6.23

Improved the visual fidelity of thumbnail images in open/save dialogs throughout Plasma and KDE apps. (Méven Car, KDE Bugzilla #489298)

Notable Bug Fixes

Plasma 6.5.6

Fixed an issue that could sometimes make KWin crash after periods of idleness. (Vlad Zahorodnii, KDE Bugzilla #513687)

Fixed an issue that would make Plasma crash when you disabled widgets in the System Tray and clicked the dialog window’s “OK” button rather than the “Apply” button. (David Edmundson, KDE Bugzilla #478625)

Fixed an issue that could sometimes make KWin crash after repeatedly pressing the “Activate window demanding attention” shortcut (Meta+Ctrl+A by default) while multiple windows were demanding attention. (Vlad Zahorodnii, KDE Bugzilla #500748)

Fixed a common case where Plasma could crash after certain games crashed first. (David Edmundson, KDE Bugzilla #506562)

Fixed a common case where Plasma could crash when configured with a weather station from the Environment Canada source in its Weather Report widget. (Bohdan Onofriichuk, KDE Bugzilla #514553)

Fixed a case where changing the visibility of the Media Player widget in the System Tray while music was playing could make Plasma crash. (David Edmundson, KDE Bugzilla #514823)

Spectacle once again remembers the location where you last saved a screenshot the next time you save one. (Noah Davis, KDE Bugzilla #511649)

Fixed an issue causing 24” 16:9 aspect ratio monitors to get the wrong default resolution. (Anton Golubev, kwin MR #8681)

Plasma 6.6.0

Fixed a surprisingly common issue whereby KWin could sometimes crash when you frantically wiggled the pointer to try to stop a monitor from going to sleep. (Vlad Zahorodnii, KDE Bugzilla #487660)

Fixed a case where KWin could crash when you deleted a virtual desktop that still had windows on it. (Vlad Zahorodnii, kwin MR #8680)

Fixed another KWin crash, this one more random. (Xaver Hugl, kwin MR #8677)

Fixed a long-standing issue whereby tooltips opened by buttons in Plasma widget popups could move onto the panel and get stuck there after you closed the widget popups. (Marco Martin, KDE Bugzilla #475646)

Fixed an issue that made popups of panel widgets undesirably change their size when you moved their panel to an adjacent screen edge. (Christoph Wolk, KDE Bugzilla #512273)

Fixed an issue making certain sub-menus of Plasma widgets not have transparent backgrounds, which was especially visible with menu blurring turned on. (Marco Martin, KDE Bugzilla #513307)

Fixed an issue in the HDR calibrator tool that made long pieces of text overflow from their boxes. (Nate Graham and David Edmundson, KDE Bugzilla #514687)

Fixed an issue that made Plasma forget the IPSec certificate passwords of L2TP VPNs. (Mickaël Thomas, plasma-nm MR #460)

Fixed an issue causing apps launched using D-Bus activation to be omitted from System Monitor’s Applications table. (Arjen Hiemstra, KDE Bugzilla #510235)

Fixed an issue in System Monitor that could make the Applications table’s “Details” panel un-scrollable under certain circumstances. (Arjen Hiemstra, KDE Bugzilla #506150)

Fixed an issue in Discover that could sometimes make Flatpak apps’ languages packages fail to get grouped with the apps. (Harald Sitter, KDE Bugzilla #513111)

Plasma 6.7.0

Fixed an issue that broke KRunner’s Activities plugin from actually finding any activities. (Sam Morris, KDE Bugzilla #514000)

Fixed an issue that caused long boot menu entries to be cut off in the Breeze GRUB Menu styling. (Sébastien Bouchard, KDE Bugzilla #513107)

Frameworks 6.23

Fixed an issue that caused a large variety of crashes in Plasma and KDE apps related to devices appearing and disappearing. (Nicolas Fella, solid MR #232)

Fixed an issue making KWallet crash on OpenSUSE-based operating systems. (Nicolas Fella, KDE Bugzilla #490788)

Fixed an issue in Kirigami-based System Settings pages and apps that made it impossible to return to the first page when using a right-to-left language like Arabic or Hebrew. (Youssef Al-Bor3y, KDE Bugzilla #511295)

Notable in Performance & Technical

Plasma 6.6.0

Plasma’s system monitoring infrastructure received further fixes to improve OpenBSD support. (Rafael Sadowski, libksysguard MR #454)

PackageKit 1.3.4

Implemented support for DNF5 in PackageKit, which fixes a huge number of issues relevant to people using Discover on Fedora-based operating systems. (Neal Gompa, packagekit PR #931)

How You Can Help

“This Week in Plasma” still needs your help! Publishing these posts is time-consuming and needs community assistance to be sustainable. Right now there are two ways to help:

• Help put together the posts using the current mostly manual process
• Help automate the process

Work can be coordinated in the relevant Matrix room.

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 keep KDE bringing Free Software to the world.

To get a new Plasma feature or a bugfix mentioned here

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