[Patch] Enter doesn't launch applications in gnome-shell zeitgeistsearch extension
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Extensions |
New
|
Undecided
|
Unassigned |
Bug Description
When using the ZeitgeistSearch gnome-shell extension, there is a silent error that occurs in activateResult for the App- and Settings- AsyncSearchProv
I'm also working on gnome bug 662341 which is related, whereby adding results asynchronously means that they are never selected first in the list, so you can't simply start typing an application and press Enter to start it. By default, all the asynchronous providers return an empty list as initialResults, and gnome-shell doesn't update the selection when new results are added, meaning the search buttons (such as Wikipedia) are always selected by default. I don't know whether that's best handled in the extension or in gnome-shell, so please let me know if I should file a new bug here instead.
If there's any other information I can provide, or tests I can run, please let me know...
Thanks a lot buddy. Good job :) will patch it :)
On Fri, Oct 21, 2011 at 1:15 AM, Mike Auty <email address hidden>wrote:
> ** Patch added: "Patch to include aliasing imports.misc.Params as Params" /bugs.launchpad .net/bugs/ 879146/ +attachment/ 2563650/ +files/ zeitgeistsearch .patch /bugs.launchpad .net/bugs/ 879146 iders. This is due to a call to Params, which hasn't /bugs.launchpad .net/zeitgeist- extensions/ +bug/879146/ +subscriptions
>
> https:/
>
> --
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
> https:/
>
> Title:
> [Patch] Enter doesn't launch applications in gnome-shell
> zeitgeistsearch extension
>
> Status in Zeitgeist Extensions:
> New
>
> Bug description:
> When using the ZeitgeistSearch gnome-shell extension, there is a
> silent error that occurs in activateResult for the App- and Settings-
> AsyncSearchProv
> been defined. I've attached a patch which solves this particular
> problem by defining Params at the top of the file.
>
> I'm also working on gnome bug 662341 which is related, whereby adding
> results asynchronously means that they are never selected first in the
> list, so you can't simply start typing an application and press Enter
> to start it. By default, all the asynchronous providers return an
> empty list as initialResults, and gnome-shell doesn't update the
> selection when new results are added, meaning the search buttons (such
> as Wikipedia) are always selected by default. I don't know whether
> that's best handled in the extension or in gnome-shell, so please let
> me know if I should file a new bug here instead.
>
> If there's any other information I can provide, or tests I can run,
> please let me know...
>
> To manage notifications about this bug go to:
> https:/
>