Arch Linux

captainbanaynays

Member

Registered: 2022-09-05

Posts: 15

Fresh install of i3 -- Mod1+d not working

Similar to https://bbs.archlinux.org/viewtopic.php?id=242251 except unlike what @slole says in #5, I cannot get any command to work with Mod1+d. Other commands like Mod1+Return for terminal, Mod1+Shift+q for kill work fine. Output of

locale -a

as that seems to be the source of similar issues for other users:

C
C.UTF-8
en_US.utf8
POSIX

Most of the rest of the post isn't relevant if running any command (using

bindsym Mod1+d exec xterm

as a test command).

Mod1+d isn't bound to anything else at the moment. xterm runs fine from the terminal. Been scratching by head for a few hours now, at this point I think I've exhausted all existing forum posts similar to this issue with no success.

EDIT: the "prepend a sleep command" and "add quotes after the exec" suggestions cannot be relevant as nothing works with Mod1+d. xterm and rofi both work fine running from the terminal.

Last edited by captainbanaynays (2022-09-05 05:19:13)

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,453

Re: Fresh install of i3 -- Mod1+d not working

Is something 'eating' that keypress before it makes it to i3? Check https://wiki.archlinux.org/title/Keyboard_input.

captainbanaynays

Member

Registered: 2022-09-05

Posts: 15

Re: Fresh install of i3 -- Mod1+d not working

SOLVED. I don't think this has been brought up as much as it should be but the i3 docs incorrectly list the directory that it reads config from as ~/.i3/config when the default config has been located at ~/.config/i3/config for some time. i3wm.org still lists this as an optional place to put a config file in compliance with XDG.

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,648

Re: Fresh install of i3 -- Mod1+d not working

So how did you solve it? https://wiki.archlinux.org/title/Genera … way_street

captainbanaynays

Member

Registered: 2022-09-05

Posts: 15

Re: Fresh install of i3 -- Mod1+d not working

i3 reads config changes in ~/.config/i3/config, not ~/.i3/config. Going through and doing my setup in that directory instead solved the problem. Symlinking the two directories would also work.