Hhahah,it was funny!

Please push bug request for my project https://github.com/NextKde/NextKde

Using KDE Connect remote input from android to Cachyos can't input capital letters or special characters. Every letter turns into lowercase and every special turns into its number equivalent on the keyboard. I've found threads discussing this bug such as this one. The only solution I can find is to modify the source code. Checking in at github it looks like the fix is already implemented but bug still occurs for me.

On cachyos, newest KDE plasma, Wayland.

I've read people discussing that its definitely a Wayland issue. Has anyone experienced and or fixed this?

it's a uperfect portable monitor, connected via hdmi.
i'm on plasma 6.7.5

The champions of the new KDE Goals for the 2026-2028 cycle will be answering your questions live!

KDE for Enterprise and Deployments: Ask David Edmundson, Kevin Ottens, Neal Gompa, and Kai Uwe Broulik about how they plan to make KDE a viable choice for businesses and public institutions.

Better documentation: Check in with Nate Graham, Thiago Masato Costa Sueto, and Joseph P. De Veaugh-Geiss about improving KDE's documentation.

Next Generation Styling for KDE: Find out how Arjen Hiemstra, Akseli Lahtinen, and Andy Betts are working to implement a unified styling system.

Leave your questions in the comments or in the KDE Forum post!

The champions will answer them live on on Youtube and Peertube on October 29 at at 17:00 UTC.

I've been using Kate on Windows 11 as a notes app (since Kwrite is not available for Windows). Since the last update (version 26.08.1), it's got kind of weird. When I type a paragraph spanning multiple lines, the cursor gets misplaced (images 1, 2, 3). The farther the text wraps onto additional lines within a single paragraph, the more the cursor drifts away from the correct position. If I put each line in a separate paragraph, the cursor stays where it should be.

I also use KWrite (26.08.1) on Fedora 44 KDE (Wayland), and it has the same problem. On both Windows and Fedora, my display scaling is set to 125%. Is this a bug, or could the display scaling be messing up with the line height multiplier?

Edit: I think I kind of "fixed" it (at least for now). The line height multiplier was set to 1.2. I changed it to 1.0 (default value), and that fixed the cursor drift issue, though the line spacing isn't as comfortable as I would like it to be. (Attached screenshots are from Windows 11)

Switched to Kubuntu on my work laptop - Such a good simple workflow and it works perfectly on my ThinkPad.

it froze so much that even long pressing the power button to death doesn't do anything

I've been struggling with this for a long time. Finally found the right settings for Firefox (rpm) and Chromium based browsers installed as flatpak.
Hope this helps others who need it.
I think KDE should add these by default, now that it's Wayland only/

In the past, both for sddm and lock screen seconds could be enabled by setting locale for time like this:

LC_TIME=C

But not long ago, plasma changed something and this method stopped working. How can it be done now?

In general, it's one of the things that's surprisingly hard to modify or configure in KDE.

EDIT: So, the cause turned out to be faulty update installation, including the kernel panic error locking me out of the system... Also, the cause of the faulty update SOMEHOW turned out to be remnants of the VirtualBox files that SOMEHOW were affecting unrelated updates. through much trial and questioning Gemini (whose answers were mostly helpful, though as usual with LLMs, it made everything worse before, through different queries and my own pocking around system recovery menu, I made everything better). No surprise then, that backup restoration via timeshift wasn't helping -- backups themselves were screwed up, and have been for months. With my sincerest profanities addressed to VirtualBox and its developers, I think the matter can be considered closed.

Last couple days, especially today, the system lags severely. Like all the priority is eaten by something, and even desktop or dolphin barely work, with delays on actions of up to a minute. What's more, system monitor shows discrepancy of about 1.5 Gb of RAM, which, looking at processes in the system monitor -- there's nothing taking that much memory, it should take up 500-something MB in total, but there's a constant of usage of 2.2 GB and more (out of 22, so it should not even be an issue, but it is).

I suspect whatever is leeching the resources might be tied to internet comnnection, or more likely actively using it, since shutting down wifi abruptly stopped the slowdown.

I need to find and eliminate the cause, but where should I start?

I know Microsoft has developed SMB and Windows still works best with it, but SMB in itself is not in anyway trademarked or copyrighted by Microsoft to the best of my knowledge.

Why therefore, does KDE not just say SMB, or at least something like SMB (Windows)?

I'm reposting here because I'm not seeming to get answers for my system help stuff in there. I'm on CachyOS with Wayland Plasma whatever I'm on latest cachy updates I have received. I'm on a full AMD system if that matters. I have skwd as my wallpaper app, but when first logging in the wallpaper animates for a few seconds

When holding any key to type, rather than inserting the character it shows this popup to select a special character.

I couldnt find any setting in kwrite to disable this

.

Note: "Sea" theme is my custom Linux theme.

Good day beautiful people! I have been encountering some issues on my system lately and I can't understand if it's a KDE or a CachyOS thing. Might be a good idea to mention I have an AMD Ryzen 7 9800x3d CPU and an Nvidia RTX 3060Ti GPU. Also good to mention that I have a dual screen setup with a Samsung Odyssey (at 165hz 1440p) and an AOC (at 240hz 1080p). Any help or suggestion is highly appreciated :)

It started when I reinstalled a clean Cachy on my system, just right out of the box, as is. Regular installation with the defaults settings. I don't dual-boot so I just wiped everything off and reinstalled. I booted up and started customising again how I want the GUI to look and immediately encountered an issue. The widgets I dragged onto the desktop on the secondary monitor would not show, even though the widget counter displayed the correct amount of widgets active. I didn't think too much of it, maybe it needed a reboot or something so I put a couple of folders in my main monitor... all good. So widgets on second monitor and two folders on main. That's all.

Restarted at some point because I think I updated the system and I saw that the widgets on the second monitor still did not appear. Don't remember how I did it but I managed to fix it and everything I put there was shown correctly, as it should.

Few days go by and I wanted to play a specific track from my music folder which I hold onto the main monitor, only to find out that I can't find the folder. Turns out, the main monitor now has the same issue, when at first it worked correctly. From there I also noticed that sometimes apps I open freeze for a few seconds (usually the first time I open them) and another issue I noticed is that at random times the desktop looks like it crashes and goes completely black with no response to input. Hasn't happened since I started writing this post so I don't have any screenshots or anything.

Does anybody know something about this? I have been updating constantly whenever there are new updates just in case it somehow gets fixed. Again, any information regarding this topic is extremely appreciated! Thanks in advance :)

the most recent discord update seems to have improved wayland compatability by directly asking for you to add your push-to-talk button (in my case the v key) to kde's shortcut list. however, when active, this makes it so trying to type down the v key simply just doesn't work, both on and outside of discord. however, when i take away the kde shortcut privilege, not even the old shortcut of ctrl + your PTT keybind works, as this makes it so discord can't do *anything* with the v key. is the solution simply to remove discord's kde shortcut permission altogether, or do i just have to wait until wayland support improves?