Score:0

App launchers do not work

no flag

I am looking for an app launcher comparable to Quicksilver (which I use on MacOS) for Ubuntu 22.04.2 LTS, but none of the tested work properly.

So far I tried Kupfer, Ulauncher, Albert and Synapse, but all of the mentioned seem to have a problem with the hotkey-setting. On Albert and Ulauncher pressing the hotkey works occasionally and only while using certain programs (for example Firefox). Kupfer does't even let me change the hotkey. Synapse doesn't work either. It seems that there is a conflict with default shortcuts used by some programs for certain actions. Nevertheless when I change the hotkey to a specific combination that is only used by the app launcher there I no reaction either.

Using Quicksilver there never was a comparable problem. Even when a hotkey-setting conflicted with a default shortcut Quicksilver would show up.

Since using an app launcher like Quicksilver is vital for me this is really depressing and I will probably go back to MacOS, if there is no solution to the problem.

Any idea how to fix this?

Thanks!

waltinator avatar
it flag
How are we supposed to know what "comparable to Quicksilver (on MacOS)" means?
us flag
Please describe which feature of Quicksilver you are trying to reproduce.
Ugh...buntu avatar
no flag
Basically the launch of the program itself. When I use the hotkey the program doesn't show up, nothing happens.
Ugh...buntu avatar
no flag
At this stage any app launcher would do it for me. I need the simple function of pressing the hotkey, tell the prpgram what to do and confirming the task (open a prpgram or website). Even this basic function doesn't work with Kupfer and the other launchers I tried.
Score:1
cn flag

The issues with the many launchers you tried is likely related to the fact that Ubuntu 22.04 runs on Wayland, a newer display system replacing the classical X11 system.

Wayland does not (yet) support that applications set a global shortcut key. To use these launchers on Wayland, you should instead set a shortcut keys through the system of the desktop, which triggers a command to reveal/hide the launcher - if the launcher provides such command line interface. For example, for Ubuntu desktop in "Settings-Shortcut keys", you then set a shortcut key to the command albert toggle. Minor issues may remain, though, such as the launcher not hiding when it looses focus, etc.

Alternatively, I can recommend you to try an excellent launcher implemented as a Gnome Shell extension: Switcher by dlandau.

Some background.

  • Shortcut keys ("hotkeys") in Linux are either global or application specific. Global means they trigger the same action from within any application, application specific is where they only work within the application. Global shortcuts will take priority, i.e., eventually mask an application specific function assigned to the same shortcut key. Global shortcut keys can be set only once. Subsequent attempts will fail.
  • The main issue is because Wayland implements tight security models. One of the consequences is that global application specific shortcuts are not (yet) possible: a system wide shortcut set by an application therefore is recognized only when you are working in an application that run on Xorg through a Wayland "gateway", XWayland. That is why Albert and Ulauncher work in some programs, others not. With the command wmctrl -l you can tell whether you have applications running on XWayland. Native Wayland programs will not appear in the list.
Ugh...buntu avatar
no flag
The workaround you suggested seems to work so far. But I think I will give Switcher a try as well. Thank you very much!
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.