Possibly this may help people who cares about correct colors and are for some reason forced to use 6.8 wayland only release.

Situation: As you may know situation with colors on wayland is quite unfortunate. And those issues are fundamental and design level, so not only related to one particular implementation. One issue is you will have either incorrect colors or your monitor output is restricted to small color space (because there is almost no apps that use the color protocol). Even their own plasma image viewer doesn't support it. (Krita6 is an exception, it supports the protocol but only if you execute it with the right env variable)

Workaround: It seems that someone has developed proxy app which is able to tell wayland what color space the real application output is encoded. So you can for example use Gimp and set the monitor profile in gimp preferences to some wide gamut c. space e.g. rec2020 with gama 2.2 to avoid clipping the gamut. Execute gimp via cm-shim (cm-shim -s rec2020_g22 run gimp) to tell wayland what the app output is and have both correct colors and be not restricted to something small like srgb when your monitor supports more. (if you profiled the display and using the profile in plasma settings)

Source:

https://github.com/dedenholm/wayland-cm-shim/

https://discuss.pixls.us/t/cm-shim-lets-any-application-talk-to-waylands-color-management-protocol

I restored the system to a snapshot with KDE 6.7.5, and everything is working perfectly again. I marked this as a "Question" because I don't know if it's a bug or something I'm doing wrong, I'm not an expert on these kinds of issues. Is anyone else experiencing this?

I did the update with Shelly, and I'm sharing some details about the system in case it's helpful.

Thank u.

Operating System: CachyOS Linux

KDE Plasma Version: 6.7.5

KDE Frameworks Version: 6.31.0

Qt Version: 6.12.0

Kernel Version: 7.2.9-2-cachyos (64-bit)

Graphics Platform: Wayland

Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor

Memory: 32 GiB of RAM (31.3 GiB usable)

Graphics Processor: NVIDIA GeForce RTX 2060

Hi, was just wondering the community's concessus on content submitted to the KDE store which has been generated with AI?

I've made a Plasma theme, a plasmoid, and a kwin extension with the help of AI. I've made them for personal use. I'm very happy with them. I have no coding knowledge or understanding how these things work (well vague knowledge for the Plasma theme), so I obviously haven't audited the code. I just know that they work and accomplish what I desire.

Do you think content like this is acceptable to publish on KDE Store with a note that they were made via AI, or should I just keep them for myself?

Right, so updated today and ran in to an issue, since it was KDE stuff that changed, assuming it is that what caused this issue. Anyone know how to fix this or anyone else running in same issue (or am i just unlucky).

I understand i am to blame for running multiple monitors on linux, but was fine until today.

KDE 6.8, wayland, idk what else would be relevant? Arch with zen kernel.

I want to switch to KDE plasma (I'm currently using GNOME) but I really like GNOME's ecosystem (and don't like KDE's one). So is there a way to install pure KDE plasma DE without all it's apps like Dolphin or KDE-connect

The new KDE update just doesn't seem right, the boot time has become slower, the sddm is slow asf too, it used to log into system immediately before, now it just waits there, also DE itself takes longer to load than before, it used to be so quick I couldn't even take a look at the splash screen properly. Also, when the machine wakes up from sleep, on entering password, the DE instantly used to show the screen, now it shows a black screen for a split second, like why man? We didn't need that at all... The new UI for sddm also doesn't seem great, the removed the ALT key navigation for "Desktop sessions" tab, now you have to press tabs to navigate towards instead of "ALT + D"ing it. NOT HAPPY AT ALL!!!

Disclaimer: this program was written with AI agents.

https://github.com/YaBulochka/appvol

I made this because I needed to control the volume of individual apps from the keyboard. It seemed like a pretty good idea, so here it is: appvol!

I used to get by with a hacky bash script bound to a hotkey that adjusted Spotify, but it had its problems and couldn't be scaled to more programs.

Plasma's volume applet and pavucontrol do per-app volume too, but with the mouse. appvol is for the keyboard.

What it does

- Change the volume of an app straight from the keyboard, without losing focus.

- Control the volume of whichever window you are currently focused on.

- Profiles: a profile controls a group of chosen apps, or ALL apps except the ones you exclude.

- Auto mode: the keys cycle through the focused window and every app that is currently playing audio.

- Native integration with Plasma Shortcuts and the Plasma OSD, plus a Qt GUI for profiles and settings.

Where it's useful for me

You’re sitting there playing, really getting into the vibe, and you just want to crank

the music volume way up—no need to Alt-Tab or jump over to a second monitor;

you just hit a hotkey, and—BOOM—it’s louder, or you can turn it back down. It’s fantastic.

In games while I'm in a voice chat: with two key presses I can make the game

louder or mute Discord completely, and then unmute it the same way. Or say

you're in a really tense clutch in CS2: one hotkey mutes EVERYTHING except CS2.

Packages

The program is split into two packages:

1. `appvol`: the CLI and the daemon
2. `appvol-gui`: the interface for profiles and other settings

Available for Arch (`.pkg.tar.zst`), Debian-based (`.deb`) and Fedora-based (`.rpm`), plus an install script for any other distribution (as long as its dependencies are met).

Status and limits

- Tested on Arch, KDE Plasma 6.7/6.8 (Wayland) only. Plasma 5 is not supported.

- KDE only for now. I may port it to other desktops in the future.

- Bug reports from other setups (distro, Plasma version, `appvol list` output) are very welcome, and so is any feedback.

I hope someone finds it useful :)

"FreeDawn" is my new sound theme for Linux/KDE. It's available now on the KDE store

https://www.opendesktop.org/p/2379312/

This took me a few months since I made everything from scratch using synthesizers, I put quite a bit of effort in it so I hope someone out there likes it.

The default sound theme in KDE is already pretty great, but I did notice it can be a bit loud at times so I tried to tone things down.

It has a very "vanilla" sound style, I tried to compose sounds that convey the meaning of the action as best as I could.

It's "Free Under CC0" so re-use it as you like for whatever!

A sticky note widget with my name on it appeared on my desktop. i did not do that i swear to god.what the hell is/was that?!

With KDE 6.8, i initially had round corners with the Steam app. Restarted the PC this morning, and they are not round now. What's going on? I'm on CachyOS.

Hello!

As an openSUSE KDE onuser, I always struggled to find a simple, native-feeling sticky notes application. Most available options are built with GNOME/GTK in mind or feel out of place on Plasma.

So, I wrote my own sticky notes app optimized for Plasma desktop users.

You can check out the source code, installation steps, and releases here:
https://github.com/danielearrighi/kde-sticky-notes

Feel free to try it out, leave feedback, or report any issues. Hope you find it useful!

Ciao

Tried out the new feature in Plasma 6.8, and everything looks so much more consistent now.

I even noticed that it works for turning OFF shadows for CSD windows with forced shadows, not just vice versa. Great work!

DISCLAIMER: This fix worked for me; it might not work for you. Try at your own risk. I won't be responsible if your computer stops working.

Symptoms: After installing Plasma 6.8 and rebooting, your login screen switches back to SDDM instead of the regular KDE Plasma login screen.

Possible fix: I found that the plasmalogin.service was disabled and not running, while the sddm.service was enabled and running. I stopped and disabled the sddm.service via systemctl:

systemctl stop sddm.service
systemctl disable sddm.service

I then enabled the plasmalogin.service:
systemctl enable plasmalogin.service

Note: After starting plasmalogin.service, my computer locked and then did not unlock, despite entering my password. I rebooted and all was well. You might want to just reboot instead, to start plasmalogin.service that way.

(Optional) start plasmalogin.service:
systemctl start plasmalogin.service

Hopefully that made some sense. And more hopefully, your login screen didn't change when you installed Plasma 6.8. :)

I updated to Plasma 6.8 and my notifications went from nicely being on my 2nd monitor , to being very rudely on my main monitor. I can't find any setting to change it back , only change the position of the notification on the main monitor , which is unacceptable for me. How do I fix this ?

In a previous version of Dolphin all windows/tabs were saved in .config/session as separate files that would then reopen when KDE launches. However now it seems that only the most recent window is saved in the file dolphin_dolphin_dolphin.

Is this by design that only a single window may be saved as a part of the session? Is there a way to restore the previous functionality? Or is this something already addressed by a newer version of Dolphin than what is in SteamOS? (25.04.3 as of this writing)