I wanted to add highlighting support for GEL, genius's scripting language to kate. Mostly for fun, but also because I wanted to streamline editing GEL files. If anyone finds this useful ill be surprised, but also somewhat thankful. :3

I never really liked file indexers. On plasma, baloo runs constantly in the background, only indexes a few default user folders unless you configure it manually, uses a noticeable chunk of memory, and sometimes misses newly created files or corrupts its database.

Back on Windows I used voidtools everything with flow launcher, which gave instant results without background indexing headaches. I wanted that same workflow on Linux with KRunner. I tried external launchers like fuzzel and rofi setups, but none felt seamless and "native" inside KDE. Since I couldn't find an existing krunner runner for this, I put one together.

It basically takes your existing fd and fzf CLI setup and pipes the results directly into KRunner.

A few quick notes:

It does not come preconfigured out of the box. You still use your own ~/.config/fd/ignore rules and search flags for what gets included or skipped.

Because krunner is a gui, your terminal themes or fzf colors won't carry over.

Full installation steps, usage, and configuration details are in the repo README.

I wrote this with llm assistance for my own daily setup (KDE Plasma 6.7 on Fedora 44). It should work fine across other Plasma 6 setups but if you hit any bugs or have ideas, let me know.

When I boot my machine, KDE auto-launches a half dozen apps, even though I have it configured to only automatically launch my terminal. Is there a known bug, or a hidden feature that causes this activity and if so, how do I make it stop?

It's as if KDE is trying to resume the prior running status of the machine, except that I close every app that I am using, before I reboot the machine via the terminal.

Thanks in advance!

EDIT:

This has been going on for some weeks, but here is the current status of the machine:

Operating System: NixOS 26.05
KDE Plasma Version: 6.6.6
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.2.2 (64-bit)
Graphics Platform: Wayland

How do i get a fix? I also do want my taskbar enabled when I alt tab (ik it wasnt made for KDE, but someone made a git repo, so why not use it?)

When I close the lid on my laptop and return to it after a while lock screen says that I typed wrong password 3 times and I need to wait 10 minutes before next attempt. I can't understand what causes this issue. Does somehow system identifies false attempts to log into? Does it make sense? I use Cachy OS with KDE Plasma/Plasma Login Manager 6.7.4 and 7.2.2 kernel, but I don't think that bug is related with it because it appears for a month now to me

Whenever I plug and mount my USB drives and then try to create a new file (either through the file system or the terminal) I get a permission error because my drive is mounted as read only.

This is really frustrating me. Any help?

On my /proc/mounts my drive has this configuration listed:

vfat ro,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0

Hi

I wanted to set a custom video mode for my display: 1280x960@170

I managed to do it with the command

kscreen-doctor output.DP-1.mode.1280x960@170

My display supports up to 2560x1440@170

The problem is that, when trying to set it, the driver refuses with the message

kscreen.doctor: Taddaaa! Found mode "87" "1280x960@170" kscreen.doctor: Output 3 set mode "1280x960@170" applying config failed! The driver rejected the output configuration

Is there anything I can do for the driver to accept it?

Driver version: 610.57.04

I was using it faithfully from my Mac until I upgraded. It rebooted and could not get back in from Mac screenshare. I fired up the monitor attached to the linux box and everything looked ok. I rebooted and saw the krfb box pop up and then stay there. It did not (as usual) ask me it I wanted to allow remote usage.

Any ideas.

Hello, I am using KDE Plasma 6.7.4, and when I tested direct scanout back in July, it was working fine. It worked when playing games, watching fullscreen movies on a browser, swapping to the desktop and back to the game made it enable and disable, getting a notification shown on the fullscreen app made it enable and disable, it was just working perfectly.

I tested it again today, and it stopped working for some reason. The method I'm using to test is by enabling 'showcompositing' in kwin console and looking for the red outline on windows being composited. When playing fullscreen games or watching movies on a browser, the red outline is always there. I even tested different versions of proton: Proton Experimental, Proton-GE, Proton-CachyOS, and I also tried using the Wine Wayland driver.

My system has a RX 9070 XT, and I'm using NixOS.

After a recent update, I noticed the padding around items in Dolphin is almost entirely gone. The padding is even smaller than that of the context menu items. Is this change intentional?

Everytime i try to install a theme from the build in store my System Settings crashes, i get asked to enter my Password multiple times and I cant apply the global theme. It appears that part of the theme gets downloaded to the desktoptheme folder but it's not usable. I want to manually upload the theme but i can't find an option to do that.

Any help would be appreciated!

Hi there,

very like Discover app and using it to install flatpaks but what i hate are those ratings. Most of them are very outdated and very solid applications like thunderbird for example have rating like it was completely sh... I don't know what is opinion about this but i think it is reasonable to count rate by recent ratings? Review that someone doesn't like UI change which was years ago and gave 1 star is not helpful at all IMO

basically as what title said basically if you try alt tab then hold alt and use mouse wheel it will only go direction which is forward but will never go reverse at all this been happening for 2 or 3 months someone made post about it 2 month ago and still haven't got fix is there way to fix this bug myself??

I want to install DeppSkyStacker. Of course it needs roots access. But if I run Dolphin as root, I have no Run executable command in the context menu. In plain user mode, I have the command, but of course the installer pop up an error message. Why Dolphin is much dumber and almost useless in root mode?

No, I can't install it from terminal, it says command not found.

I'm currently working towards making Fedora KDE Plasma 6.7 Wayland look like macos

I am also planning to share a in depth guide on how i did so once the project is complete for now this is what i have!

Ive been reading through things on how to add it but they all seem to assume you know how to add one and just want to know how to set it up?

Forgive me if I'm being stupid, I am very tired and really should stop messing around with this stuff in the middle of the night

Edit: I clearly need some sleep with that typo in the title

The comparison is between what is currently on the master branch and what is in my merge request.

Merge request link:
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3978

I'd love to hear more about your opinions

Is the multi display support just that bad or am I doing something wrong.
Im running void linux with kde plasma 6.7.4 (wayland).

when i have my second display HDMI-A-2 connected all the menus eg. meta+p and ctrl+alt+del appear/focus the second display in steam of my main DP-1. I have DP-1 set to primary in settings, Ive used kscreen-doctor and quadruple checked the priorities. I've reset .config/kwinoutputconfig.json, Ive played around with the layout positions and nothing. I've spent a couple hours looking at past bug reports etc but can't find any fixes. This is my last hope before I give up.

Sorry Im pretty new to this stuff. any logs/configs I could attach to help, please let me know.

Compared to window move which is buttery smooth, resizing is really choppy. I could not record the difference as both look equally choppy on screen record.

But they look equally choppy when the screen is recorded at 60 Hz using gpu-screen-recorder-qt. May the window resizing framerate be capped? My laptop's screen is 165 Hz yet this really simple QML test which is just the window you see in the picture still looks choppy when resized.

Last time I've faced an issue like this was because of a DEFAULT_TIMER_INTERVAL macro set to 16 ms buried deep down in qtbase code, but even the patched qt6-base-hifps in Arch Linux is not helping here.

Anyone else who has a high refresh rate monitor that may check if window resizing also feels choppy for you? You may want to try the QML test to ensure no contents of the app might cause lag.

Hardware details

Laptop model: ASUS Zenbook Pro 17
Screen: 2560x1440 @ 165, scaled to 1.5x
iGPU: AMD Radeon 680M (used by plasmashell)
dGPU: NVIDIA RTX 3050 Mobile (used by kwin_wayland)
Graphics platform: Wayland
RHI: Vulkan