The typeahead feature in the search box on the Accounts page appears to have the same problem as the access policy editor did in bug 1017496. The search itself still works, but this should be a straightforward fix, similar to that used for bug 1017496.
Also, as in the bug 1017496, this problem only appears when the Beaker web UI is mounted somewhere other than at the root of the web server (e.g. at the default "/bkr").
The user search field on /users is not a new typeahead, it's an old TG autocomplete widget, so not related to the problem in 1017496 (the patch for that bug fixed all typeahead URLs centrally). This is actually just another case of double application of the TG url() function. The problem exists on all admin pages and has been there since the search field was added in commit d9346bff in Beaker 0.5.40 (2010).
http://gerrit.beaker-project.org/2620
verified on my testing vm(beaker-0.15.3-0.git.5.46f86da)-->pass steps: 1. check all the search box under 'Admin' menu. 2. type ahead in the search box. 3. check the dropdown list. Actual results: same as expected results. Expected results: display drop-down list containing the input value, and no error in logs.
This change is included in the Beaker 0.15.3 maintenance release: http://beaker-project.org/docs/whats-new/release-0.15.html#beaker-0-15-3