this post was submitted on 03 Jul 2024
9 points (100.0% liked)

KDE & Plasma users

2797 readers
5 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE's software runs on GNU/Linux, BSD and other operating systems, including Windows.

founded 4 years ago
MODERATORS
 

Hey friends!

Basically, here is my problem. I open the launcher menu (or KRunner) and start typing. Let's say I type "firefox", and hit Enter.

The launcher menu is very slow. It often opens "Files" instead, because that pops up after I type the first two letters.

Basically this means I need to wait a second for the launcher to finish searching, show me firefox, and then press enter.

This is frankly infuriating. Every other launcher on any other desktop or WM does not have this issue.

I have experienced this on two different machines running both Plasma 5 and 6, on different distros, both are beefy machines.

I'm sure there is a way to avoid it, does anybody know?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 4 months ago (1 children)

The new cache-to-RAM improvements in Plasma 6.1 will help a lot.

Then, for plasma search, you can configure the placement of the results in systemsettings. This is also Plasma 6 only afaik

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

I don't actually care about speed to be honest, more the correctness. Should have phrased my question differently oops

[–] [email protected] 2 points 4 months ago (1 children)

What do you mean by correctness?

[–] [email protected] 3 points 4 months ago (1 children)

Well if I type "discord" then "discover" is an incorrect result, imo.

[–] [email protected] 2 points 4 months ago (1 children)

Is this an actual example?

Here the search is so quick, that on "dis" is already has results. But then the delay to search again is too high.

[–] [email protected] 1 points 4 months ago

Yes, actual example.

I followed the advice of another user and disabled some of the search options and its super fast now and should probably fix my issue. I still went ahead and reported this as a bug though