Summary: | "focus searchbar" shortcut not remembered | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Ilya M. Cassina <imc> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | adawit, flying-sheep, rjohnson |
Priority: | NOR | ||
Version: | 4.2.4 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ilya M. Cassina
2009-07-15 03:05:55 UTC
This is also occurring with the trunk build as well for me and the Kubuntu packages for 4.3.1 in Karmic. I can confirm this issue in packages < 4.3.1 and in Trunk. Thanks! This isn't a Konqueror bug, this is a konq-plugins bug from KDE Extragear. confirmed, up to vanilla kubuntu karmic (In reply to comment #0) > Version: 4.2.4 (using KDE 4.2.4) > Compiler: gcc 4.2.4 > OS: Linux > Installed from: Gentoo Packages > > When configuring a custom shortcut for "focus searchbar" in Settings -> > Configure Shortcuts... --> (Konqueror) "Focus searchbar" the new shortcut will > work as expected until konqueror is closed. > > Upon running konqueror again the shortcut is reset back to default (Ctrl+S). > > Inspecting $HOME/.kde/share/apps/konqueror/konqueror.rc, under the The shortcut belongs to the searchbar plugin so it would not be saved in konqueror.rc. Instead it is saved under $HOME/.kde/share/apps/konqueror/kpartplugins/searchbar.rc. > <ActionProperties> container I can see all the other custom shortcut I set but > there is no trace of "focus searchbar" shortcut here. > > I think konqueror forgets to write that shortcut to its configuration file. > > If someone can point me to the "internal name" of "focus searchbar" I can try > to write the shortcut manually in the configuration file to see if it can at > least read it correctly. I cannot reproduce this in KDE 4.7. Even when I close and restart konqueror my searches are rembered properly, including any alternate shortcut I setup. If this problem is still an issue in the latest version of KDE, feel free to reopen this ticket. |