SUPER + RETURN not working due to misconfiguration

[zdehasek]

System details

Omarchy v3.1.5

What's wrong?

After update to latest version SUPER + RETURN did not invoke new terminal.

the problem was in file ./.config/hypr/bindings.conf whre was --dir instead if --working-directory directive

❌ Wrong

bindd = SUPER, RETURN, Terminal, exec, $terminal --dir="$(omarchy-cmd-terminal-cwd)"

✅ Good

bindd = SUPER, RETURN, Terminal, exec, $terminal --working-directory="$(omarchy-cmd-terminal-cwd)"

Dunno how to fix for all, maybe with migration ? Will be happy to make a fix if someone point me to the right direction

[zdehasek]

Ok, so someone changed it in the last release https://github.com/basecamp/omarchy/blob/7f9ee95e1ae5d327d8cb2cb5b58415f58147e535/migrations/1762121828.sh#L44

But why its apparenlty wokring for someone but not for me?

[kzagoris]

For me, the migration has created

bindd = SUPER, RETURN, Terminal, exec, $terminal --working-directory $(omarchy-cmd-terminal-cwd)

Thus, causing the shortcut not to work.

[minton]

Same. I also had to change $terminal = uwsm app -- $TERMINAL to $terminal = uwsm-app -- xdg-terminal-exec.

[dharmavagabond]

In the last update, xdg-terminal-exec was introduced, therefore, the command should be: $terminal --dir="$(omarchy-cmd-terminal-cwd)", where $terminal's value must be: uwsm-app -- xdg-terminal-exec.

Now, something vital for xdg-terminal-exec is having the file ~/.config/xdg-terminals.list, which the migration creates, however, it is only created for kitty, alacritty and ghostty, if you are using wezterm, for example, you would have to manually add the name of the terminal's desktop entry at the beginning of the file. E.g. wezterm.desktop.

[fredrickrob]

I just changed the command as stated above and it worked for me. However, I did not change the terminal value from what was already in the file:

$terminal = uwsm app -- $TERMINAL

Will that cause any problems going forward? Right now everything seems to be working fine.

[zdehasek]

I am still using alacritty

[ryanrhughes]

If an omarchy-update run fails part way, it can leave you in a state where you have new files referencing xdg-terminal-exec from this new addition but you don't have the package installed since the update didn't finish cleanly.

The easiest way to resolve this is to start a terminal via Walker and run omarchy-update and / or fix whatever issue is blocking it.

Alternatively, pacman -Sy xdg-terminal-exec will install just that package but do still ensure you finish running omarchy-update cleanly for the migrations.

If Walker is dead and you can't launch terminal, switch to TTY2 with ctrl + alt + 2, login, and use the same command above to install xdg-terminal-exec

If omarchy-update has ran and completed all migrations successfully, check your bindings file to ensure you have:

$terminal = uwsm-app -- xdg-terminal-exec
bindd = SUPER, RETURN, Terminal, exec, $terminal --dir="$(omarchy-cmd-terminal-cwd)"

If your bindings have changed or moved, it's possible the migration didn't change these appropriately.

Going forward, this will use xdg-terminal-exec as your $TERMINAL value and $terminal in Hyprland which allows for a lot more flexibility with solid fallbacks. You can change your terminal without restarting by using Omarchy Menu > Install > Terminal alone. xdg-terminal-exec will also intelligently fallback to a different terminal in the event that your preferred one isn't available due to accidental uninstall or some other reason.

[zdehasek]

So for some reason the xdg-terminal-exec package was NOT installed on my system. Ok.
Is there any safe and recommended way how to re-run all migrations ? I assume that migrations are idempotent

[ferrao]

In my case, I use ghostty and xdg-terminal-exec was installed and had no errors with the update, but I still have this problem, as my bindings.conf still shows:

$terminal = uwsm app -- ghostty

And I had to change it by hand to:

$terminal = uwsm app -- xdg-terminal-exec

[rafadpedrosa]

TLDR;
Because of my keyboard layout I had to use BACKSPACE instead of RETURN.

--

Hi guys, I would like to also share my case given that it might help others. I installed xev to double check the input and I found that was not RETURN.

I changed my bindings to:

bindd = SUPER, BACKSPACE, Terminal, exec,uwsm-app -- xdg-terminal-exec --dir=$(omarchy-cmd-terminal-cwd)

[n4sser77]

thanks, this was a lifesaver

[n4sser77]

also just found out that the return key is just another name for the enter key