search

albertlauncher / albert

A fast and flexible keyboard launcher
https://albertlauncher.github.io
Other
7.22k stars 303 forks source link

When Cmd key assigned as hotkey, albert will not launch automatically on next start (tested on Fedora and FreeBSD) #900

Closed viktormadarasz closed 3 years ago

viktormadarasz commented 4 years ago

Hi

I have Albert on both my Fedora Box and on my FreeBSD box

I have an issue regarding launching ( or launch auto on login) when the Cmd/Command/Windows key is assigned as hotkey to albert.

My DE is Xfce on both machines

My Albert version is: 0.16.1

As a workaround what I have to do on each reboot as to load albert with any other hotkey assigned f.e albert -k v and once loaded I change the hotkey to Cmd/Command/Windows key and the app works fine.

Is there any particular reason why albert does not load the next time / next reboot when the assigned hotkey is Cmd/Windows/Command key?

jmckinny commented 4 years ago

I also ran into the same problem using Arch on Xfce. I can set the launch shortcut to the windows/super key but on reboot Albert crashes. It gives this error: 2:51:54 [FATAL:default] Failed to set hotkey to ៀ. -- [(null)] Only when I go into the configuration file and manually change it does it start again.

RedBearAK commented 4 years ago

I have run into this, and I am fairly sure the solution was to open the Keyboard settings, go to the Application Shortcuts tab, and remove a shortcut for xfce4-popup-whiskermenu that was using Ctrl+Space. But this was conflicting for me because I use Kinto (https://github.com/rbreaves/kinto) to remap Ctrl to the Cmd key, and then I was assigning Cmd+Space (which would actually be Ctrl+Space) to Albert, to mimic the shortcut in macOS for Spotlight.

If you're saying you are assigning just the Cmd key alone to activating Albert, I would recommend against that just on general principle. I'd recommend Cmd+Space instead. But the solution to the conflict should be similar either way. Either in Keyboard --> Application Shortcuts or in Window Manager --> Keyboard, something in XFCE is claiming the shortcut you're trying to use before Albert can bind to it on startup.

It might not seem like there should be a conflicting keyboard shortcut in use, but I have seen the same symptoms of being able to assign the shortcut successfully while logged into XFCE only to have it crash Albert after logging out and back in.

I ran into a lot of this while jumping back and forth between XFCE and IceWM trying to troubleshoot some issues with Kinto.

If you're on a Mac or just enjoy the Mac style keyboard shortcuts, check out Kinto at the link above.

mattwithoos commented 3 years ago

There's a fix that is unfortunately sitting in pending for almost a year :(

https://github.com/albertlauncher/albert/pull/861

ManuelSchneid3r commented 3 years ago

Please read https://superuser.com/questions/1583616/key-xy-could-not-be-registered

I have an issue regarding launching ( or launch auto on login) when the Cmd/Command/Windows key is assigned as hotkey to albert.

How can you set that? The UI should mask these options and force you to use modifiers. Also asking @jmckinny.

I will close this issue since it adresses an issue which is excluded by design.