Bug 1224215 - Krunner randomly forces you to backspace-remove text to clear out text
Summary: Krunner randomly forces you to backspace-remove text to clear out text
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-14 13:47 UTC by Joed L
Modified: 2024-06-03 16:06 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joed L 2024-05-14 13:47:16 UTC
Krunner randomly forces you to backspace-remove text to clear out text

Submitted here too: 
https://bugs.kde.org/show_bug.cgi?id=485375

SUMMARY

I have to manually hit backspace to remove text from krunner. 

expected behavior: it should just clear out text or have it highlighted to allow for "write over" so that the new text I enter wipes out old text.  

Hard to reproduce, not sure what triggers it because it doesn't happen all the time...but I think its when I highlight text. 

1. Highlight some random text from web browser
2. Call krunner 
3. Observe behavior
4. esc and call krunner again, and NOW it highlights all the text for overwrite....which should be intended behavior initially.  

DEMO of the problem:

Hard to explain, so here is a vid:
 https://youtu.be/0WtkuhZGlEs
Comment 1 Joed L 2024-06-03 16:06:11 UTC
Confirmed. 

Bug but of a different kind. 

krunner doesn't "respect" the keyboard shortcut override when assigned "ctl+ Space" krunner launcher ....

it tries to keep the original keyboard shortcut (clipboard contents copy) along w/ the launcher. Hence why it drops the cursor at the end without it being highlighted. 

Shared w/ upstream.
Comment 2 Joed L 2024-06-03 16:06:35 UTC
Closing as won't fix, since the bug is so small, and it can live as a known issue upstream.