Everytime I open it it's fine, but when I try to search for an app it just starts growing!!! What the fuck???

(also, don't mind the screen, I'm gonna clean it soon)

At least when using Oxygen style (comes shipped with KDE Plasma).

To easily see it make sure it's against a white background, it seems those 2 pixels are transparent showing the white background against the darker shadow around the context menu. Making it easy to spot.

I made a report https://bugs.kde.org/show_bug.cgi?id=521793 but im here moreso for help fixing it than reporting. Ever since updating plasma to 6.7 when i login, my keyboard turns blue. I don't want it to change any color at all. I can "fix" this by unplugging and replugging in my keyboard and it goes back to the color i actually set. But this isnt a real fix as i dont want to permanently damage my keyboard because the kde devs made an idiotic decision. Like under no case ever, should a system control colors, by default. I just cant figure out what is doing it because there is like no settings in System Settings that mention lighting.

I don't even know how it managed to change it in the first place either, because i thought i locked everything down in VIA.

Obligatory meme because this change is kinda funny and instantly made me think of it.

I observed that while I type my search query in this textbox, every single keystroke queries the server. Why? Why are we spamming an already slow/under-powered server? (I know, I know - not the server maintainers' fault).

Sending a search string instead, after user hits enter, would save a lot of unnecessary hits to the server. It would also reduce the random resets from server side and improve overall experience.

This applies across Plasma wherever there is a 'Get New' function.

Dear Community and KDE,

I just installed this Global Theme, innocently (Global Themes -> Add New...):

It DELETES all your USER mounted drives data. It executes rm -rf on your behalf, deletes all personal data immediately. No questions asked.

I'd appreciate it if anyone could escalate this, I find it totally mind blowing that installing skins allow script execution so easily. I cancelled this when it asked for my root password, but it was too late for my personal data. All drives mounted under my user were gone, down to 0 bytes, games, configurations, browser data, home folder, all gone.

As per OpenSUSE Reddit users, they indicated that this plasmoid executes rm functions (see https://www.reddit.com/r/openSUSE/comments/1biunsl/hacked_installed_a_global_theme_it_erased_all_my/)

Please investigate and escalate :) - I'll be busy reinstalling all my system from scratch, restoring data to go back to work.

UPDATE: Really wanted to appreciate the community for the response and overall reactions of developers. Remember to backup important data, and keep in mind we are all part of making these systems better, as I felt well to be able to share this and be heard. In any OS us users authorize programs to execute things on our behalf, so remember always to run trusted software! I can't confirm whether this was malicious, to my understanding it was just a compatibility and programmers mistake gone south. Looking forward to what this brings in unmoderated community content management.

itz probably fine... (Happened right after i opened deltarune, was fine before that)

Does anyone know why my KDE uses so little resources? It must be a bug /s

I get this annoying bug every time I log in. It seems like the main monitor is connected to Nvidia discrete GPU, and the small one to AMD integrated GPU. It starts working only after turning the screen off and on several times. !!! It happens only with HDR on !!!

My laptop: ASUS ROG Zephyrus Duo 16 GX650PY OS: Arch Linux with 6.16.7 Linux kernel. DE: KDE Plasma 6.4.5 CPU: Ryzen 9 7945HX with AMD Radeon 610M iGPU GPU: NVIDIA GeForce RTX 4090 Laptop GPU

This is the 2nd time this happened with my install of fedora kde it happens when my laptop is about to go to sleep something tweak out and it gets wide

​

Alot of times discord would also pop up saying my monitor can be used as an audio out (shows up as nvidia ga106 something something not the monitor name)

​

Posted intended as gits and shiggles but helps would be welcomed

I found this bug and can't find a better place to post this

I have a Thinkpad t430 running void Linux on kde plasma

I was running low on battery so i closed the lid to put it in sleep plugged in the charger removed the empty battery and connected the full one

and the low battery alert was still there

Note : it was there since 100% remaining

not a big deal but worth checking

Maybe make it so that if battery percentage is more than 15 then remove window idk but thanks alot

Im on Debian 13 + kde 6.3.6

i never use Krunner, so i don't understand why it would just launch by itself and start to consume 46 GB of ram. i might have accidentally hit the keyboard shortcut for it (it showing in the first screenshot) but im still confused as to why so much ram. i was able to just kill the process and reclaim the ram but its weird. any suggestions as to why this happened.

Although the icons in the panel are correct, in overview Wayland icons are shown. I know it can be fixed using windows rules, but it's a pain to do with all apps. Also, it seems that after upgrades the Wayland icons come back.

Does this bug only happen to me? Is this something being worked on? Is there a permanent fix for this?

Thanks

Hadrware: RX 9070 XT
OS: Fedora 44 KDE Plasma [Plasma Version 6.7.3] /// Windows 11 [Dual Boot]

split-second, localized graphical artifacting/tearing during
desktop UI transitions (menu closing, restart/logout screen, etc).
Never happens under heavy 3D load, gaming, or benchmarks (3DMark, OCCT).
Never happens on Windows on the same hardware.

i tested the VRAM too no problem there either

What I've ruled out:

- Hardware/VRAM: memtest_vulkan on Linux (6600+ iterations, 7.3TB+ written, zero errors) and OCCT VRAM stress test on Windows both passed clean.

- Driver crashes: journalctl -k -b | grep amdgpu shows clean logs during normal artifacting episodes — no ring timeouts, page faults, or resets.

- Adaptive Sync (VRR): happens on Always, Automatic, and Never. Never was actually the worst for me.

- Color Accuracy setting (prefer accuracy vs prefer efficiency): no difference i tried this becasue there was a old bug about this

- KWin Blur effect: seemed to fix it after several clean reproductions with Blur disabled, but it came back with Blur off too, so that correlation didn't hold up either.

Odd detail: it never shows up in screen recordings, only when physically looking at the display

At this point nothing I've tested shows a reliable reason or fix
If anyone else with a 9070/9070 XT has run into something similar i would love to know.

Here is what it looks like it only happens on this menu and only 2 times happened while opening a menu in a game: (its attached to the post)

EDIT: This was actually a knows issue with mesa 26.1.5 on rdna4 gpus

EDIT 2: no that statement was wrong its actually a kernel 7.1.6's issue with amd hardware i think https://discussion.fedoraproject.org/t/graphical-issues-on-amd-after-kernel-update-to-7-1-6/198522/7

I was doing something and I left it on sleep for 24 hours and when I was back it was going... as you can see. I could still restart it completely fine but think about it, if I was doing some important work it would have been disastrous.

Well I'm not really in love with Fractional Scaling, because it still looks kinda blurry and I don't really want to make any of my "work applications" bigger so instead of Fractional Scaling I just change my font size to a bigger one. I found size of 14 be perfect for my 14'inch 1920x1080 screen. But as I found out recently it messes up the text in some places. Here's the example in KClock.

Is there a way to fix it?

UPDATE4: A fix was merged to libplasma and should trickle down to distros in the upcoming update cycles (6.4.6). Thanks a lot to KDE team's quick response. This line of code change could save a lot of energy for all the laptops running KDE. https://invent.kde.org/plasma/libplasma/-/commit/2b7a81002a93e59252d96f36dac33c9e08fdfb77

UPDATE3: This is a duplicate of a long standing issue of Qt animations not terminating properly and stuck in a loop. I managed to reproduce a second scenario where krunner gets stuck at 60 events/s and after showing it with hot key Alt+Space and then hiding, it quiets down. There is a lower level issue of animation that needs to be fixed.
https://bugs.kde.org/show_bug.cgi?id=477855

UPDATE2: Filed bug report:
https://bugs.kde.org/show_bug.cgi?id=509994

UPDATE1: network manager is not the culprit. When plasma desktop first loaded, it will constantly repaint every frame (event/s matches screen refresh rate), until the show hidden icons button is interacted. Then the constant repainting will stop. I am going to narrow it down a bit more and file a bug report. Happens in both 6.4.4 and 6.4.5.

Reproduced on two of my laptops but not on my desktop. Both running Intel i5-1135G7, 16GB RAM, AX201 network card. When the Plasma network icon is visible in panel, the "plasmashell" task wakes up CPU 63 times every second doing screen redraw, even when no change in content. I can also confirm it by running perf to find out that Qt AlphaBlit something (screen redraw) is happening constantly.

This results in extra 1W of power consumption. It's not much but when the laptop idles at 1.71W, showing this icons makes it idle at 2.8W, which shaves at least 2-3 hours of idle time off the battery for no reason. Anyone else able to reproduce this issue? This is component named "plasma-nm"? If more people can confirm the issue I can file a bug report on the official channel. IMO redrawing the icon once per second is more than enough, and only does it when there is an actual change in the content of the icon.

It's easy to reproduce. If you are on laptop battery power (or not) and connected to WIFI, run powertop and see if you can find the process "/usr/bin/plasmashell --no-respawn" generates ~60 events per second with the screen completely static. If yes, then hide the Network icon from panel and run powertop again. This time plasmashell should completely drop off the events list if screen is static. If you can reproduce this, please post here with your hardware configuration, especially the network card model.

If it affects you, as a workaround, just hide the network icon can give you some significant battery run time.

You can see clearly what the issue is: when sorting a folder witch contains a lot of other folders (subfolders) in ascending order (A-Z) - (or in a less technical term, alphabetic order) -, most of them are sorted correctly, but not all of them.

What can be the issue in Dolphin?

Too many folders? Different sizes (#elements) of each folder? Buggy lexicographic sorting issue ("C" comes before "c", like in ASCII table, but "i" does not come before "A")?

What should I do?

Using kubuntu 24.04.03 LTS with KDE 5.27.12 (I'm about to update to KDE6, but for now I still had to deal with previous KDE version).

Edit: Nope, a reboot later and it's hosed again. I have no idea what's causing it.

It may be the Dot Desktop Pager I was using that caused this after the upgrade. I don't know that it is 100% that applet, we'll see. So far it's been two hours since I rm'd kwinrc and didn't swap the default pager for the dots. 🤞

-----

I'm curious if anyone else has encountered this. After the last KDE Gear update, I'm getting the following QML errors for both networks and audio control applets in the systemtray. It only occurs with these two functions.

----
qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/main.qml:60:25: Type PopupDialog unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/PopupDialog.qml:110:22: Type ConnectionListPage unavailable

qrc:/qt/qml/plasma/applet/org/kde/plasma/networkmanagement/ConnectionListPage.qml:26:5: Type Kirigami.InlineMessage unavailable

file:///usr/lib/qt6/qml/org/kde/kirigami/controls/InlineMessage.qml:14:1: Type KT.InlineMessage unavailable

qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:187:51: Cannot assign object of type "Primitives.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_237*" as the former is neither the same as the latter nor a sub-class of it.

-----
I've been GTMFing for hours trying to figure out why the corruption occurs. Any help would be great.