I found this gem on Resonite the other day and I was wondering who the artist was. I tried searching it on Kagi, Google Images, TinyEye, Bing, my own fediverse instance...but nothing! I seriously cannot find where this is from and would super appreciate if anyone knows anything about this one. Thanks!

Ive recently made a custom control center and wanted some opinions :)

Im planning on uploading it to my github soon!

Any good ideas for improving it ?

When inserting an audio CD, KDE creates various folders of conversions of the audio files. This is a cool feature but it's slow and there's no system setting to turn it off, it seems.
There are system settings for changing the conversion settings but no setting to turn it off?

We continue with the 7-day marathon of KDE versions with the sixth and latest major release of the KDE desktop environment at the time of this post, KDE Plasma 6.0.0, released on February 28, 2024, demonstrated in an OpenMandriva Cooker build, although it was compiled on the same day as the first maintenance release of the KDE Plasma 6.x version series, 6.0.1, i.e., March 5, 2024, it was delivered with 6.0.0. Fun fact: The only downloadable bootable ISO files of Linux distributions that included Plasma 6.0.0 that I found at the time would have remained lost media if I had never located any of them, which is something I ironically did with KDE 4.0.0 (January 11, 2008), GNOME 3.0.0 (April 6, 2011), KDE Plasma 5.0.0 (2014), and GNOME 40.0 (March 24, 2021) because I was not an adult at the time these versions were released, having been born on May 14, 2003, and turning 18 on May 14, 2021 (GNOME 40.1, the first minor release of the GNOME 40.x series, was the latest version of GNOME at the time, if I recall correctly).

Hi,

Under Wayland one remote desktop app cannot cover every compositor, so this needs work in each one, including KWin.

We are investing in a draft called RemoteDesktop1 with GNOME and KDE, working toward wlroots too, aimed at headless multi user sessions (no monitor, no portal click, many users on one host). On the KDE side we fund a KWin implementation. Attach to an existing local Wayland session is in better shape already (TigerVNC 1.16 w0vncserver).

We shared this on r/wayland a few days ago and got good questions there: https://www.reddit.com/r/wayland/comments/1wvsql0/bringing_headless_remote_desktop_to_wayland/

Full writeup on our community, including the KDE work and the session startup proposal:

https://community.thinlinc.com/t/bringing-headless-remote-desktop-to-wayland/2084

Happy to answer questions. (We are Cendio, we make ThinLinc and maintain TigerVNC / noVNC.)

Been working on a small KDE Plasma 6 widget called Audio HUD.

It provides a compact, live overview of your audio output directly on the desktop, including:

• Output device and reported codec
• Sample rate and PCM bit depth
• Active playback applications and their audio formats
• Volume and mute status
• Sample-rate matching between active streams and the output

One of the bigger improvements in this release is routing-aware monitoring, which allows the widget to follow playback streams through processing chains such as EasyEffects.

I've also worked on making the interface more compact and adaptable, with native Plasma backgrounds and support for light and dark colour schemes.

It's open source and designed specifically for Plasma 6.

GitHub: https://github.com/noisetta/audio-hud

Latest release: https://github.com/noisetta/audio-hud/releases/tag/v1.2.0

I'd be interested to hear what other KDE users think, especially any suggestions for improving the interface or usability!

Logitech has no Options+ for Linux, so I ended up with my own app for my MX Master 4.

Up front: I didn't write the code. Claude (Anthropic's AI, in Claude Code) wrote all of it. I told it what I wanted and tested every build on my mouse. It is built for Plasma 6 on Wayland.

What it does:

- **Actions Ring.** A menu around the cursor (bubbles, pie or tiles), drawn with layer-shell. A bubble runs an action, opens its own sub-ring, or works as a dial you turn with the wheel: volume, tabs, zoom, undo, Krohnkite layouts.

- **Gestures.** Hold a button and swipe. A live compass shows how the swipe was read, and you can tune the distances, the diagonal dead zone and when it fires.

- **Buttons.** About 70 ready actions, a third of them KWin and Plasma global shortcuts (Overview, desktop grid, window tiling, Spectacle), plus key combos, commands, scripts and macros.

- **The rest.** Wheel and SmartShift, pointer speed, haptic patterns, Easy-Switch, battery in the tray.

- It runs as a systemd user service and has a D-Bus API for scripts.

Limits: tested on exactly one setup (MX Master 4, Bolt receiver, Plasma 6 Wayland, Arch-based). Other MX mice may work; I can't check. The ring needs layer-shell, so it does not work on X11.

Code, screenshots and an Arch package: https://github.com/nictonus/mxoptions

If you have an MX mouse and try it, I'd like to hear what breaks.

I've released KDynamicWallpaperTools 1.0.0, a toolset for creating and building dynamic wallpapers for KDE Plasma 6.

It includes a graphical interface for:

• Converting GNOME dynamic wallpaper definitions, such as from this collection.
• Building animated AVIF wallpapers for use with this dynamic wallpaper plugin for KDE.
• Creating native KDE Plasma day/night wallpaper packages.
• Editing existing wallpaper sequences, including solar timing and automatic sunrise/sunset calculations.

The project provides DEB and RPM packages, along with the source code.

Project and downloads:
https://gitlab.com/deusrex/kdynamicwallpapertools/

Feedback, bug reports and suggestions are welcome.

During my experience whit KDE plasma, I always wanted to make a custom task switcher. I have looked through the tutorial on KDE.org, and sailed the web in search of a more in depth explanation for it, or something that is close to what I would want, but at the end it was only time lost.

Are custom task switchers unpopular?
Is there a more in depth tutorial online?

Thank you for your support.

AI disclosure up front. HyprKwin is written with heavy use of an AI coding assistant (Claude Code). Most of the code was written by it, at my direction: I decide what goes in, use it as my daily driver, and review and test every release. I know some people would rather not run code made this way, and that's fair. I'd rather you know now than find out later. I won't claim the AI makes the code good or bad; the tests are the claim I'll stand behind:

• A test suite that drives a real nested KWin with real key presses and window drags on Plasma 6.6, 6.7 and the 6.8 beta. It checks window positions, focus and the border's pixels.
• A soak test that does random everyday things for two hours on two monitors: opening and closing windows, switching workspaces, unplugging a monitor, reloading the script. It watches for errors, leaks and slowdowns. The last run was 30,000 actions with no errors.
• Upgrade rehearsals from older releases with lived-in settings.

It's GPL-3.0 and on GitHub, so you can read all of it.

What it is. I moved from Hyprland (Omarchy) to Plasma, missed the tiling, and didn't want to give up Plasma to get it back. HyprKwin is a KWin script, not a fork. You keep panels, widgets, Overview, KRunner, activities and System Settings, and get:

• Dwindle, master (including centred, three-column), monocle and scrolling (niri-style) layouts, chosen per workspace
• Hyprland's keybindings by default, and a keys guide you can search with Meta+K
• Per-monitor workspaces, as in Hyprland, on top of Plasma's virtual desktops
• Groups (tabbed windows), scratchpads, workspace rules, and window rules in Hyprland syntax
• A coloured or gradient focus border, and optional animations (a separate effect)
• An importer for your existing hyprland.conf, and hyprkwinctl for scripts and status bars
• Everything is set on its own settings page in System Settings

What I'm asking. It has been on the KDE Store for a few weeks, with a few hundred downloads, and 1.0 is meant to be the "stable, names frozen" release. Before calling it that, I'd like it to run on setups other than mine. I'm especially interested in:

• Plasma 6.8, which is out on Wednesday
• Multi-monitor, especially mixed scaling and hot-plugging
• Non-US keyboard layouts (the workspace keys follow your layout's digit row)
• Upgrading from the Store version with your settings in place

Installing the RC. It's GitHub-only for now; the Store stays on 0.16.1:

1. Download hyprkwin-1.0.0-rc1.kwinscript from the release page.
2. System Settings › Window Management › KWin Scripts › Install from File…
3. Log out and back in. KWin keeps an already loaded script's old code until then.

It needs Plasma 6.6-6.8 on Wayland. Turning it off in KWin Scripts puts everything back as it was.

Bugs: GitHub issues. The form asks for the output of hyprkwinctl version. Comments here are fine too.

Thanks for having a look, and for the blunt feedback, which I expect.

Title. I followed the instructions on the github page but I could only find one installation for fedora that just installs the command centre. Dolphin looks very different upon applying the theme, not as shown in the KDE store page. If anyone else is using this, or knows how to have this kind of setup, please lemme know, I'm just a newbie to theming!

Source: https://github.com/loofiboss-bit/NoxForge/releases/tag/v16.0.0

Before the latest update I was able to set the exact threshold limit for maximum battery charge, now I only have the option to limit it?

Pretty self explanatory. I haven't found any static blur desktop effects out there

I have been trying to do this for seven months but with trial and error got it now. I am an AI (Average Individual) and can make mistakes... Please don't be too harsh. Also, it requires PyQt6 compiled against KDE Craft... I'll upload the bridge, the .pyd and the pyqt site-package (The links are a part of me trying to make a java ide that feels like bluej as bluej javafx renders fonts in an unreadable way in my computer. I don't know java as I am a python dev...) Links:
Bridge

The dynamic link library (.pyd)

The Custom PyQt6 site-package (download as a folder and add it to you pip site-packages)

Claude and I have been working on rvwasm: a full Debian desktop running KDE Plasma 6, entirely inside a browser tab. Nothing is streamed from a server; the whole machine runs on your own computer, in the page.
Try it: https://plasmaontheweb.com (desktop Chrome / Edge / Brave; a fast CPU helps a lot) Source: https://github.com/Pogo-Bash/rvwasm

How it works in short:

• Kernel: Joel Severin's [linux-wasm](https://github.com/joelseverin/linux-wasm), a Linux kernel compiled to WebAssembly where every process is a Web Worker.
• The desktop shell is native: plasmashell, Qt 6 and KDE Frameworks are compiled straight to WebAssembly (about 100 packages), so the panel, Kickoff and widgets don't go through emulation.
• Apps are real Debian riscv64 binaries: Konsole, Dolphin, Kate, System Settings, Firefox and more run unmodified, through a riscv64 → WebAssembly JIT I wrote.
• Wayland: a small compositor written in JavaScript runs in the page.
• GPU, sound and video: OpenGL goes to WebGL2/WebGPU through virgl, sound goes through a kernel sound card to PulseAudio and the page's audio output, and video decodes on your real GPU through WebCodecs (VA-API).
• apt-get install works, through a relay limited to package mirrors (Debian, PyPI, npm, GitHub, crates.io). It isn't an open proxy.

What works:

• Plasma 6 with Breeze and Breeze Dark, Global Themes (even Catppuccin)
• Kickoff and Milou search, Klipper, notifications, system tray, most widgets
• Konsole, Dolphin, Kate, System Settings
• Copy and paste with your real machine, files in and out
• Sound

Rough edges, honestly:

• It needs a fast CPU per core (Apple M1+ or a recent Intel/AMD), 16 GB of RAM is comfortable, and it's Chrome-family only for now.
• The first boot downloads the parts of the disk it needs, which is slower; later boots are cached.
• Emulated apps (Firefox, compiles) are much slower than native.
• Some widgets still don't render (anything that relies on Qt Quick ShaderEffects, since the software renderer doesn't draw them).

This is an unofficial hobby project, im not affiliated with KDE e.V. Huge thanks to the KDE developers, since Plasma turned out remarkably portable, and to Joel Severin for linux-wasm, which everything sits on.
I'd love feedback, especially from anyone who knows Plasma's internals. Things like which widgets or apps you'd want to see working, or what breaks on your machine.

The biggest thing keeping me from KDE is gnome's overview. The combination of:

1. Seeing all active windows and being able to select them with the mouse
2. Being able to start typing a program name and it automatically opens or focuses the existing window
3. All of this being a press of the meta button

This is a really great flow for me and I just haven't found anything that fully recreates it.

The fullscreen 'Application Dashboard' only lets you start programs by typing the name
KRunner mostly completes part 2, but doesnt complete part 1 and part 3 is a pain in the butt
I haven't found any other configurations, widgets, programs, etc that offer the full recreation

Any recommendations?

Edit: My fault, overview was disabled. So fucking sorry to yall. Thanks for helping me move from gnome, it feels like a husk sometimes

Hi KDE community!

I've been working on an open-source Linux driver for the Goodix USB fingerprint reader "27c6:5125", found in some Huawei MateBook laptops.

After extensive development and testing, fingerprint authentication is now working on my Fedora 44 KDE system, including:

- Fingerprint enrollment through KDE System Settings

- Plasma Login Manager authentication

- KScreenLocker fingerprint unlocking

- sudo and PolicyKit authentication

- Password fallback

The driver integrates with Fedora's existing fprintd/PAM authentication stack rather than replacing KDE's authentication mechanisms.

At the Plasma login screen, submitting an empty password field selects fingerprint authentication. The reader then takes approximately one second to become ready.

The latest release, v2.1.0, introduces a fixed 21-sample enrollment process. During qualification on my device, 97 out of 100 valid matcher probes produced positive matching scores, providing a day-to-day recognition experience close to Windows Hello.

The project also preserves factory firmware and supports Windows/Linux pairing coexistence without firmware flashing.

Current compatibility:

- Fedora 44 KDE x86_64

- Goodix USB "27c6:5125"

- Firmware "GF_ST411SEC_APP_12509"

- SELinux Enforcing

Testing has so far been limited to one physical reader. Other configurations have not yet been validated.

One known limitation: fingerprint login does not automatically unlock a password-encrypted KWallet.

The project builds on existing community work, particularly Rockytkg's Goodix implementation, with full acknowledgements in the repository.

GitHub: https://github.com/sorguido/goodix-27c6-5125

I'd be interested in feedback from KDE users with this specific fingerprint reader, especially anyone willing to test it on additional hardware.

Contributions and technical feedback are welcome!

Dolphin will not show .webp covers in .mkv container as thumbnails, png and jpeg work fine.
I am using ffmpegthumbs as ffmpegthumbailer showed the perforation left and right like when showing generated thumbnail but with the cover underneath and obscured. (only for non webp)
On both i had dolphin configured to show video thumbnails. Do I need another/different package? I had tried "kio" something before but aslo did'nt work.

Operating System: Fedora Linux 44

KDE Plasma Version: 6.7.5

KDE Frameworks Version: 6.30.0

Qt Version: 6.11.2

Kernel Version: 7.2.9-200.fc44.x86_64 (64-bit)

Graphics Platform: Wayland

Plasma 6 removed the old window tabbing, and I couldn't find any community-scripts that worked on plasma 6 that did what I needed. I wanted my windows to stay where they are, just grouped logically with one Alt+Tab entry instead of having multiple desktops and workarounds.

So I wrote kwin-window-groups. It's a single self-contained KWin script, no dependencies.

What it does:

• Meta+Space twice to group windows (first press picks the window, second picks the target).
• Meta+Alt+Space to ungroup.
• Grouped windows collapse into one Alt+Tab entry (shows whichever member you used last)
• Alt+Tabbing into a group brings all its windows forward, then they're released — clicking between them is just normal KWin.
• Never moves or resizes your windows. Positions are sacred.

What it doesn't do: no visual tab bar, no stacking, groups don't survive logout. It's intentionally minimal.

Tested on KWin 6.7 (Wayland). If you've been missing the old tabbing behavior, this might be what you're looking for.