Version: (using Devel) OS: Linux Installed from: Compiled sources Unless I unassign the Esc key from the "Stop" button in konqueror, I cannot use it in the search bar to close it, the way it works in Kate for example. I get a message like "Exc key is assigned twice. Go to the shortcut settings to change it. Won't take action" The funny thing is, in the shortcut settings, I only see the 'Stop' action having the Esc key assigned to it, not the search bar close button. Now if I unassign the Esc button from the Konqueror 'Stop' action, Esc will close the search bar. And the even more funny thing: After reassigning the Escape key to the 'Stop' action, Escape works in both the search bar (if it is visible/has focus?) AND it works to stop loading a page. So for me the problem seems to be fixed (I hope restarting konqueror doesn't bring me back to square one, though), but it should be working this way without unassigning and then reassigning the action.
I'm using KDE 4.1.85 (KDE 4.2 Beta2) on Kubuntu, installed as described at http://www.kubuntu.org/news/kde-4.2-beta-2 .
That being said: It's great to have the search bar in konqueror - finally! Thanks, guys, this is probably the biggest usability improvement of konqueror in the last years.
Does it happen only when you've a splitted view?
I guess you're talking about that Ctrl-Shift-L or Ctrl-Shift-T thing, right? When I had the problem, I didn't have split views. And now the problem is really gone, after re-assigning the key binding. So I cannot reproduce it any more.
FYI: I just got the same thing in kiten: "The key sequence 'Esc' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered." Unassigning and re-assigning didn't fix the problem in that case.
On revision 900106, the bug is still valid: when konqueror is splitted (ctrl+shift+...) CTRL+F (and "ESC" for closing the search bar) doesn't work. I still have this error message: «The key sequence 'Ctrl+F' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered.»
In bug 176206 there's a testcase for the broken ctrl++. That one doesn't trigger but the linked page http://www.linuxjournal.com/article/6334 does (4.2-beta2).
This may be related to bug 180108 (Ctrl+F ambiguous on the first time loading multiple times , too)
*** This bug has been marked as a duplicate of bug 177332 ***