[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Assignee|alexander.loh...@gmx.de |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Assignee|k...@privat.broulik.de |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=432975| --- Comment #59 from Nate Graham --- For me, at this point it seems to be 100% fixed except for the very first invocation after login, where I still get a lost keystroke if I type very very quickly. https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1230 doesn't fix that, which tells me that it's not the DBus panel size querying that's a remaining bottleneck. We could chase further performance improvements, or we could just auto-start KRunner at login. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #58 from Doug --- I believe the idea of not having it load immediately was to keep resource use down for default installs. But maybe there could be a simple checkbox "enable KRunner at startup" or something similar. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #57 from Szőts Ákos --- Yes, what I always do in all my KDE installs is to autostart "/usr/bin/krunner --daemon". This causes KRunner to be loaded during KDE start-up and not to wait for it until the first time it's needed. I think it'd be nice to include it into default KDE installs, too. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 John van Spaandonk changed: What|Removed |Added CC||j...@van-spaandonk.nl --- Comment #56 from John van Spaandonk --- This occurs especially when I press the windows key and start typing, directly after I logged on. It it the case that the krunner app must load from disk the first time it is run? If this is so then perhaps it is possible to always load the krunner part on startup to prevent this. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Artur Raczyński changed: What|Removed |Added CC||artur.raczyn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Podagric changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #55 from Podagric --- maybe this will help https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1230 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #54 from Nate Graham --- That is a very interesting observation. The difference between those settings is that the "Top" mode has to calculate its position every invocation using KWindowSystem APIs that take into account the Plasma Panel position and thickness. Perhaps these are heavyweight APIs that need to be made lighter. Or perhaps the position can be cashed and updated only if any of the conditions that affect them (screen resolution/scaling, panel position/thickness) get changed. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Till Schäfer changed: What|Removed |Added Version|5.19.5 |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #53 from Till Schäfer --- I can confirm the workaround. Plasma does not feel sluggish here, but the difference for krunner is still remarkable. I have not been able to type something before krunner pops up, when using the center position. Before, the bug appeared regularly to me. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Dimo Fedortchenko changed: What|Removed |Added CC||d...@angelhill.net --- Comment #52 from Dimo Fedortchenko --- I still have this issue in KDE 5.22.3, but I have discovered a very interesting "workaround" that completely solves the issue. In the KRunner settings, if I change the Krunner Position on Screen to "top", it takes at least 3-5 seconds to open up no matter the enabled plugins. However, changing it to "Center" opens Krunner immediately even with a bunch of plugins. I have a Ryzen 9 3900x running in this case Fedora 34 (slowness has been around since I started in Fedora 31). However, on my machine I have discovered that my plasma bar is also very slow, like clicking the Volume icon is extremely slow and laggy, and my plasma bar is at the top of the screen, not sure if the slowness of the plasma bar causes krunner to also be slow when it opens at the top (where the plasma bar is). Or maybe it's completely unrelated, but in any case, if you're having KRunner open slowly, try to change it's placement to the Center of the screen, it solved the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Michael K. changed: What|Removed |Added CC||f4tm...@web.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #51 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/66 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Szőts Ákos changed: What|Removed |Added CC||szots...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 andreas.sturmlech...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=432975 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #50 from ariasuni --- Seems to work well on KDE Neon. It runs in a VM, work perfectly when under no load, I tried to launch an upgrade at the same time and it still manages to be fast half of the time (I’m not sure how it translates in real use but that’s definitely a huge improvement). It seems the dbus-send trick has been reverted: https://invent.kde.org/plasma/plasma-workspace/-/commit/d544e7657fc756505670c0bfdfb6062a23f8798d And that DBus activation is instead handled directly by kglobalaccel framework: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/609 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #49 from Nate Graham --- Can you please file a new bug report with that? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 andreas.sturmlech...@gmail.com changed: What|Removed |Added See Also||https://bugs.gentoo.org/sho ||w_bug.cgi?id=767478 CC||andreas.sturmlechner@gmail. ||com --- Comment #48 from andreas.sturmlech...@gmail.com --- (In reply to David Redondo from comment #41) > Git commit 0e575a20ef36532b5b40a40ea30f915976942477 by David Redondo. > Committed on 11/09/2020 at 12:23. > Pushed by davidre into branch 'master'. > > Activate KRunner instead of running the binary This is just to register a regression caused by this commit, where krunner is starting applications with cwd "/" instead of "~", confirmed on several systems to be fixed after reverting 0e575a20. See also downstream bug: https://bugs.gentoo.org/767478 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Marzal changed: What|Removed |Added CC||taba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #47 from phd --- Proof-of-concept for the above (using wmctrl): krunner/krunner.desktop: ... Exec=wmctrl -ai `wmctrl -lxG | grep 'plasmashell' | grep -E -- '-1 +0 +0 ' | cut -d' ' -f1`; dbus-send --type=method_call --dest=org.kde.krunner /App org.kde.krunner.App.display In fact using such a light and independent program like wmctrl to focus the desktop might be beneficial for speed. I'm not sure if requesting PlasmaShell to focus itself will always be fast. After all what we want is to simply tell X11/Wayland to move the focus to the desktop's window and send all the future input there. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #46 from phd --- Or, even better, add focusDesktop() to Plasma and simply modify krunner/krunner.desktop: Exec=dbus-send --type=method_call --dest=org.kde.plasmashell /PlasmaShell org.kde.plasmashell.PlasmaShell.focusDesktop; dbus-send --type=method_call --dest=org.kde.krunner /App org.kde.krunner.App.display so that KRunner can still be opened even when Plasma is not running. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #45 from phd --- > Can the Alt+F2 shortcut do two things: > 1. immediately focus the desktop (so that we can relay on [1] from here) > 2. then show/execute KRunner (with the above in place it doesn't need to be > that fast)? Probably we could do that like this: Alt+F2 calls this new PlasmaShell's method: dbus-send --type=method_call --dest=org.kde.plasmashell /PlasmaShell org.kde.plasmashell.PlasmaShell.displayKRunner which does two things: 1. immediately focuses the desktop 2. then calls (using Qt/C++ DBUS API): dbus-send --type=method_call --dest=org.kde.krunner /App org.kde.krunner.App.display -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #44 from ariasuni --- Yes, I was talking about the situation where I invoke KRunner with Alt-F2. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #43 from phd --- Can the Alt+F2 shortcut do two things: 1. immediately focus the desktop (so that we can relay on [1] from here) 2. then show/execute KRunner (with the above in place it doesn't need to be that fast)? [1] "aggregate text for KRunner in DesktopView" https://invent.kde.org/plasma/plasma-workspace/commit/003e30a64e976e66c02d3aa8b06301710a231889 @ariasuni You mean the Alt+F2 invocation, not the desktop typing? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 ariasuni changed: What|Removed |Added Version|5.17.5 |5.19.5 --- Comment #42 from ariasuni --- With the above commit, it’s very very hard to miss more than one letter. I easily miss the first letter though, so it’s not a definitive fix. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #41 from David Redondo --- Git commit 0e575a20ef36532b5b40a40ea30f915976942477 by David Redondo. Committed on 11/09/2020 at 12:23. Pushed by davidre into branch 'master'. Activate KRunner instead of running the binary Currently when we invoke KRunner and it is already running we will start binary, KDBusService will check if it is already registered and then call org.freedesktop.Application.Activate. Cutting the middle out should improve the time that it takes to show KRunner and make it less likely that key strokes are lost. If KRunner is not running we, can rely on dbus activiation to start KRunner. Unfortunately we cannnot call Activate with dbus-send because it doesn't support it's argument type. Instead we can just use the existing display method. M +1-2krunner/CMakeLists.txt R +2-2krunner/krunner.desktop [from: krunner/krunner.desktop.cmake - 094% similarity] https://invent.kde.org/plasma/plasma-workspace/commit/0e575a20ef36532b5b40a40ea30f915976942477 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #40 from Nate Graham --- Git commit 003e30a64e976e66c02d3aa8b06301710a231889 by Nate Graham, on behalf of Piotr Henryk Dabrowski. Committed on 09/09/2020 at 18:54. Pushed by ngraham into branch 'master'. aggregate text for KRunner in DesktopView Aggregate text for KRunner in DesktopView to prevent eating fast-typed characters. partial solution: resolved for DesktopView, not resolved for running KRunner from shortcut Test Plan: When DesktopView is focused, typed characters show KRunner query. All fast-typed characters should now appear correctly in KRunner window, instead of only first typed character. M +35 -12 shell/desktopview.cpp M +2-0shell/desktopview.h https://invent.kde.org/plasma/plasma-workspace/commit/003e30a64e976e66c02d3aa8b06301710a231889 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 stefanpro...@kolabnow.com changed: What|Removed |Added CC||stefanpro...@kolabnow.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #39 from Alexander Lohnau --- On related not when discussing the issue on reddit people reported that using the KRunner plasmoid called "Search" works really good as a workaround. Maybe someone finds this useful :) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Oussema Bouaneni changed: What|Removed |Added CC||the.neophytes.l...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Edward Donovan changed: What|Removed |Added CC||kde-b...@numble.net -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Alexander Lohnau changed: What|Removed |Added CC||notux...@gmail.com --- Comment #38 from Alexander Lohnau --- *** Bug 401696 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Alexander Lohnau changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #37 from Alexander Lohnau --- *** Bug 374660 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Alexander Lohnau changed: What|Removed |Added CC||me...@gruntech.org --- Comment #36 from Alexander Lohnau --- *** Bug 377054 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #35 from Alexander Lohnau --- (In reply to Patrick Silva from comment #34) > Case 1 is also reroducible on neon unstable. Weird, I don't have any of these issues on one of my setups. And the other (very recent KDE Neon Unstable install with latest updates) I only have Case2, Case1 was fixed for me with the latest change. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #34 from Patrick Silva --- (In reply to Alexander Lohnau from comment #29) > It seems like we are mixing two cases here: > > 1) KRunner is invoked by Alt+Space and we immediately start typing > 2) We are on the Desktop and type really fast (don't wait for KRunner to > show up or invoke it manually). Case 1 is also reroducible on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #33 from phd --- >>https://phabricator.kde.org/D26718 >I guess I should submit this to GitLab now, right? https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/148 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #32 from Alexander Lohnau --- Yes please :-) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #31 from phd --- >https://phabricator.kde.org/D26718 I guess I should submit this to GitLab now, right? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #30 from phd --- There is a patch ready for using KRunner from the Desktop View: https://phabricator.kde.org/D26718 As for Alt+Space/Alt+F2, there is no solution so far other than autostarting KRunner in advance. But maybe for this shortcut we could: 1. run KRunner 2. focus Plasma Destktop View and rely on the solution above? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #29 from Alexander Lohnau --- It seems like we are mixing two cases here: 1) KRunner is invoked by Alt+Space and we immediately start typing 2) We are on the Desktop and type really fast (don't wait for KRunner to show up or invoke it manually). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #28 from Nate Graham --- Darn. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #27 from Patrick Silva --- This issue persists on my neon unstable too. The first character typed when desktop is focused and krunner isn't running in background doesn't appear in the search field. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #26 from Doug --- Sorry, I meant to say I'm getting "B"- stupid typo on my part! But I went back to check on this again, and found that it's a bit more complicated. If I type "Hello" quickly, or at least normal speed, I get "ello". If I type "H" and wait for the text box to appear, it will appear with an "H" in it, after which I can add the "ello". I checked this several times, stopping "krunner" between each attempt, and it is consistent. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #25 from Nate Graham --- It's supposed to be A, so I'm happy to hear that it's working. :) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #24 from Doug --- I've disabled the PIM Contact Search module that was causing krunner to crash per Bug 423003, but the behavior of krunner seems the same as before. I'm on Neon Developer's Edition 5.19.80, updated as of 7/9/20. Just to be clear, when I have focus on the desktop and krunner has not been started, is the desired behavior of krunner: A) typing "Hello" should invoke krunner and send "Hello" to the text box or B) typing "Hello" should invoke krunner, and send "ello" to the text box I'm getting A, but if it's supposed to be B then I guess it is working, though it would seem a papercut if not a bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #23 from Doug --- I've installed KDE Neon Developer's Edition in a VM. After updating and restarting, krunner crashes immediately upon trying to invoke it by typing on the desktop. I can submit the crash report and backtrace this weekend sometime, but I just wanted to let you guys know I'm still here! Doug On Tue, Jun 30, 2020 at 12:47 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=416145 > > --- Comment #22 from Nate Graham --- > If you don't want to cmopile krunner from source (for that, see > https://community.kde.org/Get_Involved/development#Plasma) you could maybe > install KDE Neon Unstable edition in a VM after a few days and test in > there. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #22 from Nate Graham --- If you don't want to cmopile krunner from source (for that, see https://community.kde.org/Get_Involved/development#Plasma) you could maybe install KDE Neon Unstable edition in a VM after a few days and test in there. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #21 from Doug --- I'm sorry, I am guessing this is a patch you want me to apply? I am not a developer, and do not know how to do this. If it's something you can walk me through without taking too much of your time, I'm game- but I'd understand if not. On Mon, Jun 29, 2020 at 3:34 PM Alexander Lohnau wrote: > https://bugs.kde.org/show_bug.cgi?id=416145 > > --- Comment #20 from Alexander Lohnau --- > Whoops > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #20 from Alexander Lohnau --- Whoops -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #19 from Nate Graham --- ...rather, https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/92/diffs?commit_id=6fcc54a5e4784587fc5cdc9cabc0fd67f2731c3d. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #18 from Alexander Lohnau --- Could you please check if it got fixed/improved by https://invent.kde.org/ngraham/plasma-workspace? @ngraham already reported that this seems to improve the issue. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #17 from Doug --- I'm still having this issue as well. On Fri, Jun 12, 2020 at 8:48 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=416145 > > --- Comment #16 from Nate Graham --- > Still an issue for me. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #16 from Nate Graham --- Still an issue for me. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Alex changed: What|Removed |Added CC||alexander.loh...@gmx.de --- Comment #15 from Alex --- Is this still an issue? For me it works properly on On KDE Neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #14 from ariasuni --- I don’t use the “Software Center” runner. Interestingly, I don’t see a difference between enabling it or not today, though at the time of the test my system was under more load than right now. Anyway, it’s not fixed for me after all, there is still delay even when disabling all the runners. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #13 from Nate Graham --- Hmm, the unit converter runner shouldn't be that heavy. If you really want to improve this, disable the "Software Center" runner. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #12 from ariasuni --- Disabling the unit converter fixes the problem for me, so maybe this is an issue with some runners. I’m not sure if the issue is from kdeplasma-addons (where there’s krunner_converter) or from frameworks-kunitconversion, though. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 ariasuni changed: What|Removed |Added CC||pe...@hack-libre.org --- Comment #11 from ariasuni --- Hi, I still have this issue in Plasma 5.18.4.1. I’m not sure I’m running a version with the improvements of David Edmundson, though. I think that this issue is important because it can give the impression that Plasma is slow or buggy. Regularly, *even when KRunner is already started*, the first letter I type after using the keyboard shortcut is entered in the wrong place (aka in my browser or my code editor), on a powerful laptop. It’s very annoying because I may not have noticed I typed a letter in the wrong place, thinking the letter was just «lost», because when invoking Krunner I’m already thinking of the next task and I don’t remember where my cursor/focus was. So starting KRunner ahead of time is not a working workaround for me, because my issue is the time an already opened Krunner take to capture input. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Keywords||usability Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #8 from David Edmundson --- Git commit 1c48e351c646212c539392a361a93606274b9211 by David Edmundson. Committed on 03/04/2020 at 11:32. Pushed by davidedmundson into branch 'master'. [krunner] Avoid reparsing the config load on start Reviewers: #plasma, apol Reviewed By: apol Subscribers: apol, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28365 M +10 -5krunner/view.cpp M +1-1krunner/view.h https://commits.kde.org/plasma-workspace/1c48e351c646212c539392a361a93606274b9211 --- Comment #9 from David Edmundson --- Git commit 6dc04ef0adec2e96f81766d5d2b5b2483f1ad145 by David Edmundson. Committed on 03/04/2020 at 11:33. Pushed by davidedmundson into branch 'master'. [krunner] Avoid a uneeded pointless config parse Summary: We are krunner, our default config will be krunnerrc, we can load the instance we've already loaded in the QPT instead of doing it again. Reviewers: #plasma, apol, broulik Reviewed By: #plasma, apol, broulik Subscribers: apol, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28368 M +1-1krunner/view.cpp https://commits.kde.org/plasma-workspace/6dc04ef0adec2e96f81766d5d2b5b2483f1ad145 --- Comment #10 from David Edmundson --- Git commit e2d372d3dfd14ea3210a9e1f5755883bd2578c18 by David Edmundson. Committed on 03/04/2020 at 11:32. Pushed by davidedmundson into branch 'master'. [krunner] Don't set the position three times in a row Summary: loadConfig calls setFreeFloating. setFreeFloating calls setLocation Reviewers: #plasma, apol Reviewed By: apol Subscribers: pereira.alex, ngraham, broulik, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28366 M +0-7krunner/view.cpp https://commits.kde.org/plasma-workspace/e2d372d3dfd14ea3210a9e1f5755883bd2578c18 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #8 from David Edmundson --- Git commit 1c48e351c646212c539392a361a93606274b9211 by David Edmundson. Committed on 03/04/2020 at 11:32. Pushed by davidedmundson into branch 'master'. [krunner] Avoid reparsing the config load on start Reviewers: #plasma, apol Reviewed By: apol Subscribers: apol, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28365 M +10 -5krunner/view.cpp M +1-1krunner/view.h https://commits.kde.org/plasma-workspace/1c48e351c646212c539392a361a93606274b9211 --- Comment #9 from David Edmundson --- Git commit 6dc04ef0adec2e96f81766d5d2b5b2483f1ad145 by David Edmundson. Committed on 03/04/2020 at 11:33. Pushed by davidedmundson into branch 'master'. [krunner] Avoid a uneeded pointless config parse Summary: We are krunner, our default config will be krunnerrc, we can load the instance we've already loaded in the QPT instead of doing it again. Reviewers: #plasma, apol, broulik Reviewed By: #plasma, apol, broulik Subscribers: apol, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28368 M +1-1krunner/view.cpp https://commits.kde.org/plasma-workspace/6dc04ef0adec2e96f81766d5d2b5b2483f1ad145 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #8 from David Edmundson --- Git commit 1c48e351c646212c539392a361a93606274b9211 by David Edmundson. Committed on 03/04/2020 at 11:32. Pushed by davidedmundson into branch 'master'. [krunner] Avoid reparsing the config load on start Reviewers: #plasma, apol Reviewed By: apol Subscribers: apol, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28365 M +10 -5krunner/view.cpp M +1-1krunner/view.h https://commits.kde.org/plasma-workspace/1c48e351c646212c539392a361a93606274b9211 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #7 from David Edmundson --- There are some other steps we can do. To get input we just need a window with focus. We don't need it loaded with the QML. We can swap this to be - create window - show() (but invisible and empty) - load QML (and libplasma and all the heavy parts) - show and position input won't get dispatched till the event loop runs, at which point we'll have our text field. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 David Edmundson changed: What|Removed |Added CC||mcmailf...@protonmail.com --- Comment #6 from David Edmundson --- *** Bug 413420 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 --- Comment #5 from phd --- https://phabricator.kde.org/D26718 was modified to resolve this issue for DesktopView only. @leftcrane For running KRunner from shortcut: you may workaround this by autostarting the KRunner service: `krunner --daemon` -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #4 from Nate Graham --- *** Bug 416776 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 phd changed: What|Removed |Added CC||p...@phd.re --- Comment #3 from phd --- Since this issue was annoying me for some time now, I have just submitted a pull request to fix it (and one more): https://phabricator.kde.org/D26718 @Kai Uwe Broulik I haven't noticed this bug report earlier, and now I see you are assigned to it. Do you have a different solution already? Would you mind checking mine? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Doug changed: What|Removed |Added CC||dougjsha...@gmail.com --- Comment #2 from Doug --- If I invoke krunner by typing on the desktop it won't accept the first letter typed the first time it is invoked- but other letters will come through even when they were typed before the input dialogue box appears. For example, if I type "shut down" really fast before the box pops up it will appear as "hut down". When krunner is invoked again during the same session it will work correctly. This is in KDE Neon 5.17.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Nate Graham changed: What|Removed |Added Summary|Krunner doesn't immediately |Krunner doesn't immediately |intercept keystrokes, |intercept keystrokes, |leading the user to |leading the user to |accidentally type text into |accidentally type text into |whatever app is open. |whatever app is open CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Yeah, can confirm. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open.
https://bugs.kde.org/show_bug.cgi?id=416145 leftcrane changed: What|Removed |Added Component|filesearch |general Assignee|baloo-bugs-n...@kde.org |k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
