https://bugs.kde.org/show_bug.cgi?id=518422

            Bug ID: 518422
           Summary: KRunner executes action before it has fully matched
                    user input
    Classification: Plasma
           Product: plasmashell
      Version First 6.5.6
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: 1.0

SUMMARY

Krunner is a bit slow in matching what you type to actions it should perform.
Because it does not block activating the action until it has done the matching,
this results in frequent unwanted actions, when you use krunner with a
keyboard.

Example: You want to activate the sleek TODO manager. So you type:

ALT-F2 (get krunner)
sleek
Enter

And as a result your system goes to sleep.

This is because when you type sleek, krunner performs the matching letter by
letter. At "slee" the top match is "Power - sleep (suspend to RAM)". When you
press "Enter", sleek ignores the fact that it still has not even looked at the
"k" and happily puts your system to sleep.

If there are other keys "on flight" before "ENTER", sleek should **wait** to
process those before executing anything. It is dangerous to do otherwise.
Sleeping is a sufficiently innocuous thing, but far worse thing may happen in
other situations


STEPS TO REPRODUCE

See description

OBSERVED RESULT

See description

EXPECTED RESULT

See description

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.6
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.18.18-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4750HQ CPU @ 2.00GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: Intel® Iris® Pro Graphics P5200
Manufacturer: Notebook
Product Name: W740SU

ADDITIONAL INFORMATION

Observed on 6.5 and so indicated this as the first version in which I can
reproduce the issue. I think it is still present in 6.6. and that it was
present before 6.5. Note that this is not issue
https://bugs.kde.org/show_bug.cgi?id=173213 (It is perfectly OK to guess if
there are no other keys in flight before the ENTER, but it is not if there
are!)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to