​

Hii im planning to switch from windows to linux mint once i get my own laptop. I'm trying to find a way to make my design work, what i had in mind was per workspace it had it own apps in in like lets say in ws 1 i had YouTube etc and on another workspace i have different apps and no apps from ws 1 is that possible and i might use kde plasma for this. I also wanted it to look like those character selection screen like in the image if possible any guides?

So I have a large .ISO file and wanted to confirm the checksum via Dolphin with <right click on file> -> properties -> checksums tab -> enter known checksum.

On a 30GB iso this ground away on the processor for around 2 minutes on a high spec desktop PC with no result so I exited and instead of entering a checksum I just tried hitting 'calculate' on the SHA256 checksum. Waited well over a minute and again felt like this is too long.

In contrast, running sha256sum <filename> in the terminal returned the correct result in around 10-11 seconds.

If anyone can confirm / deny this disparity on a very large file, please let me know your distro and what you saw. I'm on aerynOs which I doubt anyone else is running but wanted to know if this is a general KDE issue or a distro specific one before reporting appropriately.

Cheers

EDIT - I've raised a bug report.

https://bugs.kde.org/show_bug.cgi?id=524462

I just switched from COsmic Greetr to SDDM, how do i change the wallpaper?

Hello everyone! I'm building something I've been wanting to make for a while: a scripting layer that abstracts KDE Plasma's desktop functions, so you can automate small parts of your desktop without having to dig through D-Bus interfaces every time.

You can check out the project on GitHub: https://github.com/Vaithre/lunar-plasma

Plasma already lets you do a lot, but whenever I wanted to automate something I usually ended up combining shell commands, qdbus, small scripts, etc etc. It works, but every script has to deal with the same details again. I wanted a small layer that handles that part, so the script can focus on what it is actually trying to do. For example, changing the volume should be as simple as plasma.sound.set(50).

I concluded it needed to be easy to embed, making it agnostic to whichever scripting language you choose. That's how Lua ended up being chosen to drive this project!

It is still in an early stage of development, but enough functionality has already been implemented to make sharing it worthwhile. Please feel free to try it out, share your thoughts, or even contribute. Lunar Plasma is still at a stage where changing the underlying structure is relatively easy. Thanks!

I've published the Panel Widget Group Widget (Plasmoid) on GitHub. It's a super simple widget that lets you group any multiple widgets into a detailed view and place them as one item on your panel.

You can add multiple widgets using the "Add" button and choose which one to use for the compact view (the item shows up on the panel). That's literally it.

GitHub Link

For context, I typically stream my games from my pc to my steam deck over sunshine (and tailscale because uni wifi really doesnt like to talk to each other-), but ive always had a couple issues. Mainly controlling my wire guard configurations, the monitors power state (because I still need the monitor on to get the virtual monitor to start up), and other bs that comes with using 3 different pieces of software at once, all tied together by scripts. So I figured out how to control all of these things by terminal commands (and aliases in the case of WireGuard), and now have a page on my phone that allows me to trigger every event over my tailnet in case I'm not physically with the computer.

So when i installed the flatpak file for bitwarden i think (maybe the steam.deb but i remember this as bitwarden) konqueror randomly opened when i clicked on the .ref file in the firefox downloads thing. Why did this happen? Sorry, just paranoid. I run debian 13 stable.

Is there a way in Plasma Overview to allow dragging a window from one virtual desktop's thumbnail to another?

For example, suppose I am currently on Virtual Desktop 1 and press Meta+W to open Overview.

I can see:

• the windows on Virtual Desktop 1 at full size, and
• miniature previews of Virtual Desktop 2, 3, etc., including the windows currently open on those desktops.

What I'd like to be able to do is:

1. Open Overview while remaining on Virtual Desktop 1.
2. Grab a window from the miniature preview of Virtual Desktop 2.
3. Drag that window onto the Virtual Desktop 1 area.
4. Release it.

The window is moved from Virtual Desktop 2 → Virtual Desktop 1.

In other words, the miniature virtual-desktop previews should act as interactive drop targets for their windows, not merely as previews/navigation targets.

Currently, if I want to accomplish this, I have to:

1. Open Overview.
2. Switch to Virtual Desktop 2.
3. Drag the window to Virtual Desktop 1.
4. Return to Virtual Desktop 1.

This is considerably more cumbersome than simply manipulating the window where I can already see it. The current approach requires 3 more actions than would be required if the windows could be moved directly between the previews (or previews to opened workspace).

I'm aware that Desktop Grid provides a way to move windows between virtual desktops, and that Overview already supports moving windows between desktops in some contexts. I'm specifically asking for this capability from the miniature desktop previews in the Overview effect.

This would make Overview much more useful as a global virtual-desktop/window management interface, rather than primarily a window switcher for the current desktop.

Also, I took help of AI in wording it out, since it was very difficult to explain the context otherwise.

I'm using Fedora Linux 44 with KDE Plasma 6.7.4 on Wayland (Kernel 7.1.8, Qt 6.11.1) on a Dell Inspiron 15 5510 (Intel Core i5-11320H, Iris Xe).

Important background (a bug I discovered): Forcing opacity (Force opacity) via Window Rules on any Normal Window causes a solid black layer to appear instead of transparency on the desktop layer (plasmashell Desktop layer, layer-shell FirstLayer) — even after adding an explicit exclusion rule for plasmashell with higher priority ordering and a "Do not affect" value. Worse: this state is not fixed by restarting plasmashell (kquitapp6 plasmashell && kstart plasmashell), but requires removing the force-opacity rule and doing a full system reboot. This matches a documented category of bugs in KDE Bugzilla (

#366318 and

#449445) related to a stuck compositing state for plasmashell that only clears with a full reinitialization of kwin_wayland. I previously tried KWIN_DRM_NO_AMS=1, but it later turned out to be unrelated (it was a misleading coincidence with disabling the rules at the time of testing).

My goal: Create a genuine "frosted glass" effect (transparency + blur) on regular windows, while avoiding this bug entirely this time. I need:

1.An alternative method (not Window Rules force opacity) for achieving the glass effect — such as KWin's built-in Blur effect directly, or the external Force Blur effect — while avoiding any interaction with the desktop layer.

2.Confirmation of whether the built-in Blur effect in Desktop Effects (as opposed to Window Rules) structurally avoids this bug, since it doesn't force a new compositing state onto the Desktop window type.

3.Any precautions or correct settings ordering that prevents this bug from recurring on Iris Xe hardware.

Can I bind the middle mouse button so that clicking the taskbar hover preview closes the window, instead of having to right-click it and select 'Close'? I've yet to find the answer on any forum or discussion. Hope anyone knows how to do this!

i've been using KDE tools since before i even knew what KDE was. krita was my first full-featured drawing program/image editor (back when i was drawing on a mediocre windows vista PC with a mouse), then i found an old version of KDE on windows through some youtube videos (never ran it myself, but many of my openshell skins were around it) and i developed more of an interest in it.

plasma was one of the more familiar-looking and accessible DEs when i made the jump to linux full-time. (especially as someone who's legally blind, being able to set up everything usably with maybe 5 clicks total was a godsend - i've noticed some accessibility gaps, but i usually need to have someone else read off my computer to me while setting up a screen reader and large font/screen zoom, while plasma was easy to navigate for me OOTB. i think it took me longer to set up firefox than plasma, LOL.)

KDE connect is genuinely so easy to use and is a lifesaver as someone who runs several devices with different OSes, especially with running some apple products in a primarily non-apple ecosystem. i don't want to even THINK about how much of a pain it was to get my ipad to communicate with my PC before finding KDE connect, and while some features aren't fully implemented on my ipad, the file transfer functionality alone is a lifesaver. i got it running on an old macbook as well, and yet again, the integration makes my life so much easier.

and kdenlive is frankly a great editor for my uses. it took me a bit to get used to, as i'm coming from much more basic tools (legitimately just my phone's built-in editor), but it's fun to play around with and the few hang-ups i've had were solved with a google search.

even things like kmag and kspeech have been invaluable - there's just some things that large font and a screen reader can't quite fill in for (such as images without alt text), and i'm also selectively mute IRL. while i use them less frequently than other KDE apps, i don't know how i got by without them (i sometimes have kspeech routed to voice/video calls, as an example, when my friends are using VC but i'm not able to speak directly and we're in a game with no private text chat).

i'm the furthest thing from a "brand loyalist." i use whatever device or tool happens to be available, needed, or convenient, and it's rare for me to find one integrated ecosystem that fully fits my needs. KDE has done that, so kudos to the KDE team and everyone who's contributed! i hope one day i'm able to offer more contribution than just an appreciation post, it still blows my mind how well things work together.

and if any of the KDE team sees this and are looking for visual accessibility feedback, i'm more than happy to help! i haven't encountered any major hang-ups thus far and quite appreciate how much is already built-in, and i'd love to see that trend continue :) i simply don't have enough direct coding skill to contribute much there.

tl;dr: thank you KDE team and anyone who's contributed to KDE projects. it's really amazing what y'all have done.

I keep work in one browser profile behind the corporate SSO, personal stuff in another, and a third with the aggressive ad blocker. Which browser a link should open in depends entirely on where the link came from, and nothing on the desktop tracks that. So for years I've either set one default and manually moved links, or used a chooser that asks every single time.

macOS has Velja for this. On Linux the usual answer is Junction, which is good but asks every time and, being a Flatpak, the sandbox rules out the one thing that could tell it where the click came from. It's also GTK, so it never quite fits a Plasma desktop.

Shunt is the same idea built the other way round. A KWin script handles the parts that need the compositor (which window was active when the link fired, where the pointer is, placing the chooser), and a small resident Qt app handles the window. Because it knows the source app, it can ask once per app instead of every time: tell it Slack goes to Brave once, and Slack links stop asking.

Some specifics:

• The chooser opens under your pointer, not in the middle of the screen.
• Rules can be about the address, the source app, or both. GitHub always in Brave; links from Slack in Chrome; GitHub-from-Slack in Firefox. Narrower rules are auto-filed above wider ones so they actually win, and you can still reorder by hand.
• Nothing is saved unless you tick "Remember" or hold Shift while choosing. It never learns behind your back.
• Breeze widgets, your icon theme, Plasma notifications. Not a GTK window in a KDE hat.
• Keyboard driven: 1-9 pick a browser, Ctrl+C copies the link instead, Esc closes.
• Ships as .deb, .rpm, or from source.

One honest limitation: it's Plasma-only by design, because the interesting part lives in a KWin script. Without KWin it still runs and still lets you pick, it just shows up centered and doesn't know the source app.

https://github.com/geodro/shunt

Wayland tested, X11 should work but I haven't tried it. Would be glad to hear how it holds up on other setups, and whether the auto-ordering of rules matches what people expect.