Version: unspecified (using KDE 4.6.4) OS: Linux The keyboard shortcut to activate the Search and Launch containment in the plasma-netbook workspace does not get stored once the system restarts or logs out. Without that, there is keyboard shortcut to focus directly in the search box of the containment. Makes it harder to use because you have to cycle through alt+tab combination or involve 2 clicks to get to the search box of the containment Reproducible: Always Steps to Reproduce: 1) Right click in Search and Launch (SAL) containment. Select Configure Search and Launch 2) Go to the keyboard shortcut option and select a non-conflicting keyboard combination (e.g. Meta+S) 3) Press Ok. Go in to any application, say dolphin and press the Meta+S combination and focus will be directed to SAL containment's search box. 4) Now close all applications and either logout or restart and go into any application and press Meta+S, the keyboard shortcut is unassigned and SAL is not activated Actual Results: Keyboard shortcut gets unassigned Expected Results: Keyboard shortcut must be stored A wish to the developers is that make a permanent keyboard combination to activate the SAL containment so that it makes the application more useful. For instance the Meta key activates the activites in Gnome 3 and search bar in Ubuntu Unity in 11.04. Makes it that much more useful.
this problem still exist in 4.7.0
Confirming for 4.7.00 on Ubuntu Oneiric (11.10).
Another report: https://bugs.kde.org/show_bug.cgi?id=266113
But other shortcuts are getting saved .. like I tried to assign Mete+E for Dolphin and it's saved permanently but not search and launch. Without the shortcut getting saved, makes the environment "mousy". Any patches?
*** Bug 266113 has been marked as a duplicate of this bug. ***
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham