This week we released a beta of Plasma 6.8, and it’s ready for testing. Before branching, the team landed a lot of great improvements to make sure it’s an awesome release. Check it out:
Notable new features
Plasma 6.8
The Kup backup system has moved to Plasma! That means it will get regular releases, and we’re encouraging OS developers to start including it. It really works very well for off-device backups.
Notable UI improvements
Plasma 6.6.7
Discover once again shows Snap versions of apps in the source selector menu rather than as separate apps. (Gabriel Kuznik, KDE Bugzilla #519204)
Changing the volume really quickly no longer causes irritating-sounding clipping noises in the volume level preview sounds. (Jeremy Senkiw, plasma-pa MR #424)
On the lock and login screens, clicking the “Show On-Screen Keyboard” button (renamed from “Virtual Keyboard”) now always shows the keyboard as you would expect, irrespective of its typical visibility settings. (Kristen McWilliam and Nate Graham, KDE Bugzilla #467209 and plasma-workspace MR #7044)
The Input Method widget has been somewhat similarly overhauled. Now it’s primarily used to switch between on-screen keyboard visibility modes, but also lets you manually show the keyboard while an XWayland-using app is focused, because these apps don’t have support for making the keyboard appear automatically. (Kristen McWilliam, plasma-workspace MR #6876)
The Kickoff Application Launcher widget is now always big enough by default to fully accommodate all items in its sidebar, rather than sometimes being scrollable — occasionally by even just a few pixels, which was fairly silly. (Christoph Wolk, KDE Bugzilla #515175)
Spectacle no longer shows a weird and misleading message about successfully copying the image to the clipboard after you use the “Share…” feature to share the image elsewhere. (Tobias Fella, spectacle MR #586)
Improved the keyboard navigation behavior of the Digital Clock widget’s calendar view. (Christoph Wolk, plasma-workspace MR #6900)
On System Settings’ Quick Settings page, the list of frequently-used pages is never just empty; now it shows a default set until you’ve used the app enough so that it knows what pages you frequently use. (Tobias Fella, KDE Bugzilla #522711)
Changed the percentages shown on the Power & Battery widget to use fixed-width “tabular numerals”, so other UI elements don’t slightly jump around as the numbers change when using some fonts. (Christoph Wolk, powerdevil MR #674)
If you have multiple panels with System Tray widgets on them, clicking the “Show Notifications” button on the “You missed some notifications” notification now only opens the notification history widget on the first/main panel. (Ameen Al-Asady, plasma-workspace MR #7028)
In the Clipboard widget’s history view, the inline buttons for the selected item now only appear when it’s hovered or when any of the buttons have keyboard focus. This makes it possible to make the buttons disappear so you can read all of the selected item’s text. (Christoph Wolk, KDE Bugzilla #520130)
Reduced a bit of awkwardness in the way you rename audio devices. (Tomáš Hnyk, KDE Bugzilla #508211)
Notable bug fixes
Plasma 6.6.7
Fixed a really weird bug in the Kickoff Application Launcher that could make phantom representations of apps in one category appear in other categories after you scrolled around there for a bit and then switched to the other category. (Christoph Wolk, KDE Bugzilla #515229)
Plasma 6.7.6
Fixed a weird bug that prevented moving focus from the password field of a network shown in the Networks widget back up to the widget’s search field. (Christoph Wolk, KDE Bugzilla #525321)
Plasma 6.8
Plasma no longer crashes if you query the wallpaper using D-Bus while the wallpaper settings dialog was open, and then switching wallpaper plugins. (Alperen Yildiz, KDE Bugzilla #525207)
Copying text in LibreOffice apps now adds it to the persistent history every single time, rather than only every other time. (Tomáš Hnyk, KDE Bugzilla #519510)
Middle-click-pasting text that was selected in a non-Qt-based app into a Qt-based app now works every time, rather than every other time. (Tomáš Hnyk, KDE Bugzilla #506325)
Fixed an issue that could make some tool settings in Spectacle’s full-screen annotation UI appear off-screen. (Mirko Laruina, KDE Bugzilla #524499)
Fixed an issue that could leave the wallpaper previews in the Activity Switcher sidebar all black, instead of showing the wallpaper. (Nicolas Fella, KDE Bugzilla #378693)
An invalid XWayland configuration file inside /etc/xdg/Xwayland-session.d/ no longer prevents KWin from launching XWayland at all. (Ilya Katsnelson, kwin MR #9894)
Entering and exiting full-screen mode no longer makes Task Manager tasks’ “I’m playing audio right now” indicators disappear or get stuck in a partially transparent state. (Christoph Wolk, KDE Bugzilla #522471)
Frameworks 6.31
Fixed a bug that made the “Frames and Outlines Contrast” theme setting not take effect in certain apps where it was expected to work. (Akseli Lahtinen, KDE Bugzilla #525364)
Manually setting your home folder to “Indexed” on System Settings’s Search page no longer creates an un-removable clone of that entry. (Nicolas Fella, KDE Bugzilla #487212)
Qt 6.11.1
Fixed a serious QML issue that could make QML-based UIs break with nonsensical property errors. (Fabian Kosmale, Qt bug #149607 and Qt bug #146886)
Notable in performance & technical
Plasma 6.8
KWin has gained support for the commit_timing Wayland protocol. (Xaver Hugl, KDE Bugzilla #513283)
Remote desktop connections now benefit from even lower latency. (David Edmundson, krdp MR #237)
Gear 26.12
System Settings’ KDE Wallet page has been ported to QML. (Nicolas Fella, kwalletmanager MR #78)
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
Tags: tech, book, reading, tv, social-media, attention-economy, politics, history
The argument presented is maybe a bit too mechanical for my taste. That said there’s indeed something to be said about the decline in literacy and its consequences on our societies.
Shows some insights into the kerfuffle around the Navier-Stokes recent resolution. The behavior of OpenAI in this affair is ludicrous. In my opinion this is showing research malpractice… Why care about the scientific method when you have a shot at good PR?
Interesting way to deal with deprecation in Python. Indeed sometimes it doesn’t hurt to keep the not so ideal old name… but you want to push user code to know they miss an opportunity in readability by using the old name.
Visualizing Rust’s Vtables: How dyn Trait Works In Memory
Tags: tech, c++, rust, memory, type-systems
Interesting exploration of how static and dynamic dispatchs work behind the scene in Rust. The chosen tradeoffs are different than in C++ and that’s something to keep in mind.
Good point. The metaphors we use have obviously some limits. In the case of the “sinking ship” when used for software it doesn’t quite work as there’s no bottom…
Or why it’s stupid to judge people on their non virtuous behavior while at the same time fostering the structures which ensure that virtue does not pay. So indeed, some people read the odds properly and act accordingly…
Such a wonderful species we are… not. Things can get really nasty when someone starts exploiting beliefs and gains some sort of power. And then, the blame game begins. Unfortunately it regularly happens.
Koko is KDE's image viewer, sharing its name with the rather famous gorilla, and yes, putting a gorilla in the icon would have made perfect sense... but we all love cats, and so did KOKO, so here we are
And while making this ridiculously cute thing I kept thinking about something that has been bothering me more and more. Hopefully the cuteness of the cat will alleviate the ranty nature of what follows
Why is so much of what we design today so f...... boring?
We have incredible displays, GPUs doing absurd things, animation engines, shaders, QML, tools I could only dream about 20 years ago... and somehow so much of what we make with all of that looks like the same five rectangles arranged in slightly different ways.
Clean. and forgettable, austere but not in a brutalist way, its.... just booooring .
I've spent quite a bit of time recently bringing bits of old Oxygen back to life, and I know there is a temptation to read that as nostalgia, as if my answer is “look, things were better when we had shiny icons!”
It isn't.
I don't want the future to look like 2008.
In fact I think this sudden fascination with old interfaces, skeuomorphism, Winamp skins, old games, old icons and all the rest is a symptom of something else. People are looking backwards because they miss design having a personality. They miss opening something and actually having a reaction to it.
And now we have AI.
And f'ing..... makes the whole thing even more urgent to me. AI is spectacularly good at producing things that look like things that already exist. And if our design ambition was already reduced to producing safe, familiar, derivative variations of whatever everyone else is doing or that we have done... congratulations, they have automated it,.... and and I can't feel much more from such things... other than plain sadness.
So I don't want us to go backwards. I want us to go somewhere.
Make something NEW!!!
Make something strange. Make something excessive. Make something beautiful, ugly, funny, annoying, charming, stupid, brilliant, probably all of those at once. Make something somebody will hate enough to write a 14 rant bolg post about.
Just please make us feel something.
see you soon in aKademy for more ranting and maybe a beer or 2
Also played with this for the plasma-studio app. I think i can do better
OOOOO and OBVIUSLY if you want our sort of Crazy JOIN us in Oxygen, or KDE or anything
The first maintenance release of the 26.08 series is out with the usual batch of stability fixes and workflow improvements. Highlights include a big batch of fixes for crashes when changing Timeline Preview settings, deleting sequences, stopping audio recordings, and using ripple editing when the Project Monitor is hidden. This release also fixes Effects Zones not being kept inside the clip boundary and tabs are now readable on theme changes on Windows.
Join us at Akademy
Some of the team members will be in Graz for Akademy, celebrating 30 years of KDE. Also Jean-Baptiste Mardelle will be giving a talk about Kdenlive.
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 20th anniversary of the first Akademy-es, the organizers have chosen a campsite to do a slightly different event focusing on the community side of KDE.
There will still be of course talks, so remember you can submit one until this September 13th!
Two weeks ago, I released AppStream 1.2.0. This release contains a lot of great changes, but one of the most important ones concerns how media are being handled, and AppStream’s default image export format.
AppStream is a Freedesktop metadata standard to describe software components. That can be anything from system services over fonts to console and graphical applications. AppStream metadata is supposed to give users enough information to decide whether they want to install a piece of software, to represent that piece of software, and to give the operating system enough information to decide whether a software component should be installed automatically and (to some extent) what capabilities and relations it has, to provide the user with sensible options.
Especially for the first two goals, and especially for GUI applications, AppStream supports icons and screenshots, which are used to showcase applications. Today, AppStream is used by all kinds of services, from Linux distributions over firmware updates to Flatpak and desktops directly. AppStream’s original design however comes from the perspective of Linux distributions in 2011, where you may want to browse the software catalog offline, without delay, and without pinging an external server (which could be a privacy concern).
Therefore, a common way to deploy an AppStream-enabled software repository is to ship all icons of all applications in the repository to the user as part of the repository metadata download. AppStream does support remote icon downloads nowadays, and for a while I thought that this would become the default eventually. However, especially in today’s world, having a bandwidth-saving, instantly responsive, privacy-protecting application browsing experience seems more important that ever.
PNG images are great!
The only format that AppStream supports for icons and screenshots (which are downloaded on-demand from your distributor’s CDN) has always been exclusively PNG. PNG images are perfect for icons, because they compress well (especially for common icon shapes), are fast and simple to load, and can be loaded anywhere, by any toolkit or webbrowser. They also ensure we deliver faithful screenshot images, even though we may have scaled or re-rendered them. Still though, PNG images are less great for screenshots, as they are not very efficient, which puts strain on any CDN that has to deliver them, as well as on people’s internet connections when browsing screenshots. Having smaller thumbnails alleviates that problem a little, but does not fully solve it.
But even for icons, PNG could be improved upon: In many cases, icons are re-downloaded with the repository metadata again and again, so having a large icon tarball adds up to the data transferred during metadata refreshes. AppStream also now supports large 128x128px icons, which nobody in 2012 expected we would need, adding even more data that will be re-downloaded. Saving some space here translates directly to lower bandwidth costs as well as faster downloads for users.
To improve PNG file sizes, the AppStream Compose library, which handles all image processing and metadata catalog composition, was running optipng on all generated PNG images. That does create smaller PNG images, but they were still relatively large compared to other image formats.
For a long time though, there was no alternative to PNG images for icons: There was no lossless image compression format that could give us the same quality as PNG images and that was also widely supported.
JPEG-XL vs PNG in AppStream
Since 2021 we have JPEG-XL (JXL), which offers a true lossless mode with often better compression than PNG. The issue was that JPEG-XL wasn’t widely supported. Then, in 2025, the PDF Association selected JPEG-XL as the preferred image format for HDR images in PDFs, and now we are finally getting browser support and more ubiquitous availability of the format (you can try it right now in Firefox!).
For screenshots, using JXL’s lossy mode, it has obvious and extreme size advantages over PNG, so supporting JXL or WebP for screenshot images was an obvious choice. If JXL would support the lossless case very well as well though, we could serve many use cases with the same exported image format, which is very attractive to me.
So, the obvious next question was whether it was worth the pain of switching the icon format, so I did some measurements on real icons. For that I used the AppStream component icon pool that Debian Unstable ships, which is almost 5000 application icons of various sizes, and converted them to PNG:
Icon size
Icons
PNG total
JXL total
Pool saved
PNG avg
JXL avg
Median saved
Mean saved
Worst
Best
Larger as JXL
48×48
1544
3.7 MiB
3.0 MiB
17.8%
2.4 KiB
2.0 KiB
17.9%
16.7%
-118.7%
60.0%
206
64×64
2018
7.0 MiB
5.8 MiB
17.8%
3.6 KiB
2.9 KiB
18.0%
15.8%
-112.7%
70.0%
279
128×128
1411
11.2 MiB
8.7 MiB
22.0%
8.1 KiB
6.3 KiB
20.1%
17.5%
-89.7%
61.0%
209
TOTAL
4973
21.9 MiB
17.5 MiB
19.9%
4.5 KiB
3.6 KiB
18.6%
16.6%
-118.7%
70.0%
694
PNG images saved with libpng at effort=4, compression=9, then optimized using optipng -o2, JXL images encoded using vips jxlsave lossless=1 effort=7 strip=1 via VIPS/libjxl.
As the table shows, using lossless JXL images over size-optimized PNG images (using optipng’s default settings) provides a roughly 20% gain. This does not look like much, until you consider how often these files are downloaded: A 20% file size reduction may only save 1-2 MiB of disk space, but if they are downloaded over and over again by many clients, it will save a lot of bandwidth.
Interesting JXL encoding findings
As a sidequest, I was curious why some images were larger than their PNG counterparts when encoded with JXL, and what the ones that were significantly smaller were.
In short, the biggest size reductions for JXL existed on images that were already small as PNG, and contained large, flat color surfaces with hard edges and simple shapes. They were not very interesting, and much of JXL’s wins come from accumulating smaller gains across all files, which compound the bigger icons get (especially at 128x128px, where JXL truly shines).
The events were JXL loses to PNG are more interesting: For example, it does quite poorly with pixel-art images that have a lot of repeating patterns. Those are encoded well by PNG, but less efficiently by JXL. Take for example Vonsh:
Icon of Vonsh, an SDL-based snake game, which PNG compresses better than JXL
My guess is that while PNG can exploit the repeating pixel patterns for compression, JXL’s predicts surrounding pixels from its neighbours, which fails too often and makes it pay almost full entropy per pixel. In this single rare case, the PNG is at 5.4 KiB, while the JXL is almost 8 KiB in size.
Other cases I looked at were arguably buggy input data, where color channels were hidden under the alpha channel of the input image. PNG could probably again exploit repeats, while we were forcing JXL to encode pixels that were invisible in the final image. This is arguably a problem with the original input data. Currently, AppStream does not make any changes to icons at all, but in future we might add a filter that removes invisible colors from images to solve this pathological case (it was only two icons out of 5000 though, so it is not a high priority).
The third case I found where JXL loses to PNG were icons with checkerboard-like patterns:
For those, PNG can likely again exploit the repeating patterns, while a checkerboard layout is pretty bad for left/top predictors like JXL’s. However, in this case the size difference (and loss for JXL) is only 450 bytes, so even though JXL loses to PNG, it does so not by much.
JXL in AppStream
Given these findings, JPEG-XL is the default image format starting with AppStream 1.2.0. AppStream Compose will encode all images losslessly as JXL, while screenshots are encoded in lossy mode at Q=90 effort=7. Since the optipng step does not happen for JXL images, this comes at no speed penalty and is even a bit faster on modern x86_64 CPUs (where libjxl can use SIMD). PNG is still available, and Compose can be told to switch between the two formats.
Upsides of JXL in AppStream right now
If you use JXL in Compose or the recent release of appstream-generator, you will get much smaller images and, for screenshots, will benefit from other JPEG-XL features such as progressive decoding, providing a far nicer user experience. libAppStream has supported JXL icons since version 1.1.3, so your clients will need that version or a newer one, and all software centers will have to support loading JXL images (which all of them do, provided the right plugins are installed).
Downsides of switching to JXL too quickly
JXL is a very new format, so web browsers might not yet display it if you are serving webpages. Your clients may also have bugs in processing JXL images, as the format is still “new”. For example, switching on JXL in Debian sent KDE Discover into an infinite loop on startup while trying to load the icons (an issue which has been fixed, but clients will need that patch first before JXL is switched on).
This currently makes JXL enablement only possible when you know that your clients can support it. This is the case for me in Debian Unstable and Debian 14, which are using JXL images for a few weeks now, but not for any older releases. Platforms like Flatpak have it even harder, because they do know even less about their clients. So, even though it has big advantages, you may want to hold off on using JXL right away, and force PNG by setting the ImageFormat key to png in appstream-generator‘s configuration, or passing --image-format=png to appstreamcli compose.
It is also worth mentioning that JPEG-XL is much, much slower on systems that do not have SIMD instructions or for which the libjxl/jxl-rs library does not have them (such as apparently riscv64 right now). If this is a concern, you might not want to switch to JXL right away.
Media pipeline improvements
Besides the JXL default change, AppStream 1.2.0 also comes with a complete overhaul of its media processing pipeline. While libappstream, AppStream’s main library, does not do any media processing and comes with very minimal dependencies to be embedded in client applications and used on servers, the same can not be said about libappstream-compose, AppStream’s library to build metadata generating applications (the server-side part, usually).
The compose library has to render fonts into font specimen cards, inspect translation files, render SVG images, decode all kinds of raster images, inspect video files, etc. Especially the fonts, and the fact that fonts can appear in SVG images, has caused issues in the past, as libappstream-compose is a heavily threaded library and most font libraries can only work from a single thread. This forced the library to essentially go into single-thread mode anytime anything that could touch a font was being processed.
AppStream also originally was created for a “safe world” where applications were vetted by the distributors before their metadata was processed. This is increasingly not the case, so it made sense to put at least a few guardrails on the most complex part of the pipeline: The media processing. As part of the change, media processing was split out into a separate worker process. This solved two problems at once: Font handling was isolated in a single-threaded binary – if we wanted to handle fonts in parallel, we could simply spawn more workers. And, being in a separate process, the media processing could now be sandboxed.
As part of the multiprocess changes, Compose also switched from using GdkPixbuf to VIPS for image processing. The latter allows for much more fine-grained control over the image output and encoding, and comes with a lot of well-maintained filters and operations, which made it possible to eliminate a fair chunk of AppStream’s hand-rolled image processing operations. As part of this transition, we unfortunately lost the ability to read XPM images, which dropped about 20-30 applications from the pool at Debian. But in the name of security, this is a sensible choice, especially since most XPM icons were very small and low-resolution, and applications using them could benefit from adding a high-quality PNG icon anyway. With VIPS, we also now restrict the amount of image formats we can load to a sensible set, so extremely niche or unexpected formats will be outright rejected (this includes sane-but-unusual formats for screenshots and icons, such as TIFF images).
The Compose library, with all of these changes, will now just request high-level operations (e.g. “render a font card for this font to a JXL image”) from the worker, and provide it with input data in sealed memfds and output locations as FDs as well. On Linux systems, the worker will use Landlock if available, to block all write access to the filesystem, deny device access and deny TCP and UDP as well. The sandbox can certainly be tightened a fair bit in future, but this was a good and safe start to gain some experience with it without having things break too easily, given the many places Compose is used in (also, Landlock’s API is surprisingly nice to use, so it was easier than I thought to add in this early version).
With all of these changes, the libappstream-compose library is now also officially marked API-stable, so you should be able to rely on it in future to build new things (its API has barely changed in the past, and now with the new media API and defaults change in place, it was time to declare it stable).
I want to see / try this!
Currently, the easiest way to have a look at the new data is to check out Debian Unstable. If you have a JXL-enabled browser, you can also see the icons in AppStream Generator’s HTML pages for Debian Sid. If you are using appstream-generator for your distribution, you will also get much more pleasant statistics and HTML pages, as well as fully deterministic media output and a whole bunch of security updates, so, update to its recent 1.0 release.
Please keep in mind that if you switch to JXL, the client tools receiving the image data have to support it. Support varies depending on the Linux distribution, so, test it first and switch the default back to PNG in case you encounter any issues.
What’s next?
With so many features and changes landed, the next changes in AppStream will focus on improving what already exists and fixing any issues (there will be more blogposts about the other features 1.2.x delivers!). Testing with the entire Debian archive as data source makes me fairly confident though that there will not be many problems. In the longer term, tightening the media processing sandbox will also be something we might want to do, e.g. by hiding parts of the filesystem tree or filtering syscalls.
For JPEG-XL, one obvious question is “Will you add support for it to the Freedesktop icon-theme specification as supported format alongside PNG, SVG(Z), and XPM?”. For on-disk icon repositories, JXL’s space-savings are less compelling, and it being HDR-capable is also not necessarily a killer feature (PNG can go a long way!). However, JPEG-XL’s ability to immediately decode larger images at reduced resolution without resampling could legitimately be very powerful here, as applications could ship a single large image and quickly decode it at 1/2, 1/4 or 1/8 the size for different purposes in their UI. JPEG-XL also supports spot-color extra channels, which applications could use as masks to recolor raster icons at render time. This could be incredibly nice to color symbolic icons on-the-fly without any SVG and CSS. JXL also provides richer metadata, which might be neat for (license/author) documentation. So, the answer here is: Maybe it makes sense to allow another format, but this will have to be discussed first, as it would force JXL into every toolkit and desktop, which is a much bigger ask than supporting it only in AppStream.
As always, let me know what you think and please report any issues or bugs directly against AppStream or AppStream Generator if you encounter problems that are with the tools, and not with a project’s metadata.
Besides maintenance and debugging work, this year, my work on Kdenlive was mostly dedicated to refactoring the Kdenlive keyframes system to make it more powerful. This is part of a NGI Zero Commons grant via NLnet, see my last status report from february for some more context.
Previously, keyframes were set globally for an effect, touching all its parameters. With the updated logic, you can now decide to add keyframes only to a specific parameter, and parameters can have independant keyframes. This work will soon be made available for testing, and will be part of the next 26.12.0 Kdenlive release.
This new widget allows to move keyframes for several effects in one step, and also supports keyframe scaling, meaning that you can easily stretch a group of keyframes.
Effect Stack Before
Effect Stack After Refactoring
Basic keyframe features remain in the effect stack, like add/remove keyframe and seek to previous/next keyframe, but all other keyframe-related features have otherwise been removed from the effect stack into a dedicated Keyframes panel. The parameter values now have a colored background to indicate if you are currently on a keyframe or not.
One drawback is that it uses more space, but we plan to futher refine the interface in the next months before the final release.
New features
Beyond the obvious possibility to add per-parameter keyframes, and manage keyframes from several effects in one place, a few other features were included in the rewrite:
Move keyframes with keyboard
You can now grab the selected keyframes with the usual shortcut, then move them frame by frame using arrow keys.
Zoom and Keyframe scaling
Zooming and scrolling can be used with the standard mouse wheel events, and it is now possible to scale selected keyframes by selecting them and dragging with the Ctrl modifier.
And all the rest
The Keyframes interface also allows to filter parameters by name to only show matching parameters, useful if you have lots of effects on a clip.
All this work will also make it much easier to add new keyframe features in the future.
Performance
"Adding new features is nice, but what about performance?" you may ask. Well, good news: this work also involved some cleanup and performance improvements. People working with lots of keyframes (for example with object tracking) will really enjoy the changes.
For example if you have a clip with more than 1000 keyframes, you will enjoy:
Much faster project load time (can be as much as twice as fast)
Much faster keyframe operation (changing a keyframe value was previously very laggy)
Much better playback speed when the clip is selected (was previously very choppy)
And even if you don't use that many keyframes, the general workflow should be a lot smoother.
Meet us at Akademy
Part of the Kdenlive team will be in Graz for KDE's Akademy, celebrating 30 years of KDE. Be there to meet us!
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.
New in Plasma 6.8: Union now themes QtWidgets applications, such as Dolphin and Kate. Bear in mind this support is preliminary and you will encounter bugs. When you do, please report them here!
To test Union:
Make sure the union package is installed (name may differ depending on your distro)
Launch System Settings
In the sidebar, navigate to Colors & Themes → Application Style
Click “Breeze (Union)”
Click Apply
This will apply Union styling to both QtQuick and QtWidgets apps.
The intention is for these apps to look as similar as possible when styled with Union to how they look with Breeze — though any minor visual improvements should be considered intentional!
If you find any issues, make sure they’re Union-specific by running the app with the Breeze style to compare the two. If the issue is Union-specific, report it here!
New size and clean up, the symbolic needs to point to point to a correct version of the icons for how its used in plasma, renaming on the applet to the correct linked version would be more optimal IMO. Commit.
ngraham
New
Old
OOOOO and OBVIUSLY if you want our sort of Crazy JOIN us in Oxygen, or KDE or anything