After adding a search engine, using it searches for "undefined" every time. Reproducible: Always Steps to Reproduce: 1. navigate to a search engine page (e.g., 'https://www.google.com') 2. tab into the search box, per dwb documentation 3. press 'gs' to add the search engine to the local list 4. type a keyword to be used to invoke it 5. press 'o' followed by the keyword followed by something to search for (this is all the standard procedure, per dwb documentation) Actual Results: Google searches for "undefined". The search string clearly shows 'q=undefined'. Expected Results: Google should have searched for <something to search for> I found reference to this at the URL above. The author is aware of the bug but isn't sure when a fix will be released. The author provided a patch, which I have attached with paths modified to work with the typical 'epatch' line in a modified ebuild: epatch "${FILESDIR}"/${P}-fix-add-search-engine.patch
Created attachment 327900 [details, diff] Patch to fix 'add search engine' bug.
Can you submit this upstream?
Ah sorry, didn't read your whole first comment. :)
Fixed in -r1.