#Krunner froze my entire #KDE Plasma desktop just from writing up a 'long', simple math equation while I was calculating some of my expenses lol. My desktop is completely unresponsive now and I couldn't do anything about it, not even Caps Lock on my keyboard respond. All I can see is my applet that monitors RAM usage last reported to be at 97%.

I'm sure about half of it is probably #Firefox, but I'm also certain the rest was caused by Krunner since I wasn't really doing anything else - as much as I love KDE Plasma, time and time again I'm getting closer and closer to upgrading to 64GB of RAM, which sounds hellllla ridiculous for a regular ol' desktop and not a homelab server.

Forreal tho, as much as I despise #macOS, how is it that my #MacBook Air M1 can fly with pretty much the same workflow with just 8GB of RAM and never encounter any types of freezes, at most it just feels sluggish (which is just a regular macOS thing), meanwhile this much more powerful machine with 32GB of RAM just freaking... dies from doing simple math calculations on Spotlight?

Ok, the way the search/launcher menu on #KDE #Plasma highlights an item in random as you're typing a search query (instead of highlighting the top item) so that it often opens a random file instead of the most likely match drives me NUTS.

I should just use #KRunner more often, as it doesn't seem to have that quirk.

I wonder if #Plasma6 fixes that.

OK, got X11 back up & running on #KDE6 this morning. Just gotta figure out this silly #krunner issue with:

The name org.kde.krunner was not provided by any .service files