i3 keybindings stop working at random

bootzin · 2016-11-07 01:16:18

And no, I'm not in any weird mode that doesn't respond to a single key (the only modes I have is the default, resize, and a custom power management, which exits on enter/esc)
But yeah, at some random times all keybindings top working, I can't even open a terminal or rofi or browser or anything, not even switch workspaces with my keyboard (I can switch if I click on them though). Volume keys and basically any other keybinding I have stop working (even the ones that don't use the mod key e.g. middle mouse button killing a window).
I use i3blocks, if it makes any difference, and a non-us keyboard layout (I use exec --no-startup-id setxkbmap to get my layout right)
Doing i3-msg restart doesn't fix it
My bar updates normally, though, so I guess i3.config is still executing, and terminal works normally
Only fix I could find was restarting the computer or logging out and back in again
Do you have any idea of what could be causing this?

Last edited by bootzin (2016-11-07 01:46:55)

seth · 2016-11-07 13:25:53

> basically any other keybinding I have
I'd say the most interesting ones are those beyond "basically" - some bindings still do work?

bootzin · 2016-11-07 14:27:07

Not really, I couldn't find not even a single keybinding that worked, all other commands seemed to work though
Could it be because I use bindsym instead of bindcode?

Steinberg2010 · 2016-11-07 14:33:01

Can you post the relevant section of your config file? (Your i3 config)

Last edited by Steinberg2010 (2016-11-07 14:55:27)

seth · 2016-11-07 15:05:08

Code would cover layout changes.
What's more stunning is that even restarting i3wm doesn't "fix" it.

Install xdotool and log grabs before and after this happens and also after restarting i3:

xdotool key "XF86LogGrabInfo"

Writes into the Xorg log.

bryan.paradis · 2016-11-07 15:50:59

Recently I had a problem with my x session where the keyboard stopped working. I am not sure what triggers it. Just to confirm you had to restart X right? I would expect the problem is at that layer. I am running a 2012 Macbook Pro.

bootzin · 2016-11-07 16:21:04

Yeah, I actually either had to completely reboot my system or log out and in again for it to work

Here's my i3 config:

set $mod Mod4
#set $alt Mod1

#Workspace names
set $tag1 ""
set $tag2 ""
set $tag3 ""
set $tag4 ""
set $tag5 ""
set $tag6 ""
set $tag7 ""
set $tag8 "?"
set $tag9 "?"
set $tag10 ""

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
#font pango:monospace 30

# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
#font pango:DejaVu Sans Mono 15
font pango:Just Old Fashion,FontAwesome,icons 11

# Before i3 v4.8, we used to recommend this one as the default:
# font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
# The font above is very space-efficient, that is, it looks good, sharp and
# clear in small sizes. However, its unicode glyph coverage is limited, the old
# X core fonts rendering does not support right-to-left and this being a bitmap
# font, it doesn’t scale on retina/hidpi displays.

#Default Keyboard Layout
exec --no-startup-id setxkbmap br

# Use Mouse+$mod to drag floating windows to their wanted position
floating_modifier $mod

# start a terminal
bindsym $mod+Return exec i3-sensible-terminal

# kill focused window
bindsym $mod+Shift+q kill

# start dmenu (a program launcher)

bindsym $mod+d exec rofi -show run -lines 3 -eh 2 -width 100 -padding 300 -opacity "85" -bw 0 -bc "$bg-color" -bg "$bg-color" -fg "$text-color" -hlbg "$bg-color" -hlfg "#9575cd" -font "Just Old Fashion 18"

# There also is the (new) i3-dmenu-desktop which only displays applications
# shipping a .desktop file. It is a wrapper around dmenu, so you need that
# installed.
# bindsym $mod+d exec --no-startup-id i3-dmenu-desktop

# change focus
bindsym $mod+j focus left
bindsym $mod+k focus down
bindsym $mod+l focus up
bindsym $mod+ccedilla focus right

# alternatively, you can use the cursor keys:
bindsym $mod+Left focus left
bindsym $mod+Down focus down
bindsym $mod+Up focus up
bindsym $mod+Right focus right

# move focused window
bindsym $mod+Shift+j move left
bindsym $mod+Shift+k move down
bindsym $mod+Shift+l move up
bindsym $mod+Shift+ccedilla move right

# alternatively, you can use the cursor keys:
bindsym $mod+Shift+Left move left
bindsym $mod+Shift+Down move down
bindsym $mod+Shift+Up move up
bindsym $mod+Shift+Right move right

# split in horizontal orientation
bindsym $mod+h split h

# split in vertical orientation
bindsym $mod+v split v

# enter fullscreen mode for the focused container
bindsym $mod+f fullscreen toggle

# change container layout (stacked, tabbed, toggle split)
bindsym $mod+s layout stacking
bindsym $mod+w layout tabbed
bindsym $mod+e layout toggle split

# toggle tiling / floating
bindsym $mod+Shift+space floating toggle

# change focus between tiling / floating windows
bindsym $mod+space focus mode_toggle

# focus the parent container
bindsym $mod+a focus parent

# focus the child container
#bindsym $mod+d focus child

# switch to workspace
bindsym $mod+1 workspace $tag1
bindsym $mod+2 workspace $tag2
bindsym $mod+3 workspace $tag3
bindsym $mod+4 workspace $tag4
bindsym $mod+5 workspace $tag5
bindsym $mod+6 workspace $tag6
bindsym $mod+7 workspace $tag7
bindsym $mod+8 workspace $tag8
bindsym $mod+9 workspace $tag9
bindsym $mod+0 workspace $tag10

# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace $tag1
bindsym $mod+Shift+2 move container to workspace $tag2
bindsym $mod+Shift+3 move container to workspace $tag3
bindsym $mod+Shift+4 move container to workspace $tag4
bindsym $mod+Shift+5 move container to workspace $tag5
bindsym $mod+Shift+6 move container to workspace $tag6
bindsym $mod+Shift+7 move container to workspace $tag7
bindsym $mod+Shift+8 move container to workspace $tag8
bindsym $mod+Shift+9 move container to workspace $tag9
bindsym $mod+Shift+0 move container to workspace $tag10

# reload the configuration file
bindsym $mod+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym $mod+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec "i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -b 'Yes, exit i3' 'i3-msg exit'"

# resize window (you can also use the mouse for that)
mode "resize" {
        # These bindings trigger as soon as you enter the resize mode

        # Pressing left will shrink the window’s width.
        # Pressing right will grow the window’s width.
        # Pressing up will shrink the window’s height.
        # Pressing down will grow the window’s height.
        bindsym j resize shrink width 10 px or 10 ppt
        bindsym k resize grow height 10 px or 10 ppt
        bindsym l resize shrink height 10 px or 10 ppt
        bindsym semicolon resize grow width 10 px or 10 ppt

        # same bindings, but for the arrow keys
        bindsym Left resize shrink width 10 px or 10 ppt
        bindsym Down resize grow height 10 px or 10 ppt
        bindsym Up resize shrink height 10 px or 10 ppt
        bindsym Right resize grow width 10 px or 10 ppt

        # back to normal: Enter or Escape
        bindsym Return mode "default"
        bindsym Escape mode "default"
}

bindsym $mod+r mode "resize"

# Start i3bar to display a workspace bar (plus the system information i3status
# finds out, if available)
bar {
        status_command i3blocks -c ~/.i3/i3blocks.conf
	font pango:Just Old Fashion, FontAwesome,icons 18 
	colors {
        	background #000000
	        statusline #ffffff
	        separator #000000
	
	        focused_workspace  #000000 #000000 #ffffff
	        active_workspace   #000000 #000000 #ffffff
	        inactive_workspace #000000 #000000 #888888
        	urgent_workspace   #000000 #900000 #ffffff
	        binding_mode       #2f343a #900000 #ffffff
    	}
	position top
}

#Persistent Wallpaper
exec --no-startup-id nitrogen --restore

#Transparency & fade fx
exec --no-startup-id compton -f

# Multimedia Control
# increase volume
bindsym XF86AudioRaiseVolume exec amixer -q set Master 2%+ unmute
# decrease volume
bindsym XF86AudioLowerVolume exec amixer -q set Master 2%- unmute
# toggle mute volume
bindsym XF86AudioMute exec amixer -q -D pulse set Master toggle
# pause / play / next / previous
bindsym XF86AudioPlay exec playerctl play-pause
bindsym XF86AudioNext exec playerctl next
bindsym XF86AudioPrev exec playerctl previous

#Power Management
set $Locker sh ~/.i3/i3lock.sh 

set $mode_system System  : S |  : r |  : s |  : h |  : l |  : e
mode "$mode_system" {
    bindsym l exec --no-startup-id $Locker, mode "default"
    #bindsym l exec --no-startup-id sh ~/.i3/i3lock.sh, mode "default"
    bindsym e exec --no-startup-id i3-msg exit, mode "default"
    bindsym s exec --no-startup-id $Locker && systemctl suspend, mode "default"
    bindsym h exec --no-startup-id $Locker && hibernate -F ~/etc/hibernate/tuxonice.conf, mode "default"
    bindsym r exec --no-startup-id systemctl reboot, mode "default"
    bindsym Shift+s exec --no-startup-id systemctl poweroff -i, mode "default"  

    # back to normal: Enter or Escape
    bindsym Return mode "default"
    bindsym Escape mode "default"
}

bindsym XF86PowerOff mode "$mode_system"

#Hide Window Borders
#new_window none

#Always open certain windows on certain workspaces
assign [class="Franz"] $tag1

#Startup programs
exec --no-startup-id franz-bin


#System Colors - Edit later
# class                 border  backgr. text    indicator child_border
client.focused          #4c7899 #285577 #ffffff #2e9ef4   #285577
client.focused_inactive #333333 #5f676a #ffffff #484e50   #5f676a
client.unfocused        #333333 #222222 #888888 #292d2e   #222222
client.urgent           #2f343a #900000 #ffffff #900000   #900000
client.placeholder      #000000 #0c0c0c #ffffff #000000   #0c0c0c

client.background       #ffffff

#Workspace back-and-forth
#workspace_auto_back_and_forth yes

#Custom keybindings
#Printscreen
bindsym Print exec scrot '%Y-%m-%d-%T_$wx$h_scrot.png' -e 'mv $f ~/Pictures/screenshots/'

Also, I've installed xdotools, as soon as I get the error again I'll make those logs and post them here

Last edited by bootzin (2016-11-11 13:13:48)

bryan.paradis · 2016-11-07 16:26:38

Anything in journal, dmesg or your normal Xorg log for now?

bootzin · 2016-11-07 16:53:48

There is a bunch of (unreadable?) files in my journal directory, not sure how to open thgem though, common text editors show only a bunch of random symbols

http://pastebin.com/PNVRETKi - This is my Xorg 0 log
http://pastebin.com/BHirf5gS - This is my Xorg 1 log

EDIT:
dmesg has a huge amount of info on it, not sure what exactly should I look for

Last edited by bootzin (2016-11-07 16:55:52)

bryan.paradis · 2016-11-07 16:56:57

Next time your keyboard stops working try holding down each key press for more than a second. If the keypress then works it is because the slow-keys feature has been turned on in X.

To turn it off install xkbset from aur and use the commands below:

Check if slow-keys is on

xkbset q | grep "Slow-Keys ="

Turn off slow keys

xkbset -sl

Turn on slow keys

xkbset sl

Disable all accessibility features

xkbset -a

Hopefully this is your issue as well.

Edit: This can only happen if something sets the accessibility features on in the first place unless something turns on slow keys itself?

[bryan@bp-mbp-arch ~]$ xkbset q | grep "Accessibility Features (AccessX) ="
Accessibility Features (AccessX) = Off

Last edited by bryan.paradis (2016-11-07 17:05:54)

ewaller · 2016-11-07 16:57:08

bootzin wrote:

There is a bunch of (unreadable?) files in my journal directory, not sure how to open thgem though, common text editors show only a bunch of random symbols

*sigh*

journalctl

Last edited by ewaller (2016-11-07 16:59:48)

seth · 2016-11-07 17:10:42

Slow keys would impact all input, not only shortcuts.

bryan.paradis · 2016-11-07 17:16:22

seth wrote:

Slow keys would impact all input, not only shortcuts.

Good point. Maybe bootzin could clarify his original post if keyboard input is impacted other than i3 shortcuts?

bootzin · 2016-11-07 17:49:51

Keyboard input is normal, I even tried to keep the keys pressed or frenetically press them to see if anything happened, lol

Regarding my journal, I have over 50k lines of log, stopped looking afterwards, most of them is because of a "loop to fast", but that's from 3 days ago, and I fixed the issue
Other than that there are a bunch of messages that say "stopping sound service" "stopping target default" and stopping a lot of other things, as well as a "Ungeistered Authentication Agent" from polkit

There is also a few failed Input/output gdm-x-session
All of these are close (ms) to the time where the message "Reached target Shutdown" "Starting Exit of the session" appeared, which makes me think that it could have been a moment where I've restarted my computer

But again, I really don't know what should I look for in all of these lines.. Maybe try grep'ing a certain keyword?

EDIT:
I also have a whole lot of "Unrecoverable failuer in required component org.gnome.Shell.desktop"

Last edited by bootzin (2016-11-07 17:59:54)

jasonwryan · 2016-11-07 17:55:06

Maybe try reading the man page or the wiki page rather than waiting for someone here to tell you what to do...

bootzin · 2016-11-07 18:08:50

While I agree that I should (and will) read the man page and the wiki entry for these, if simply reading manuals and tutorials solved all problems there would be no need for technical assistance, teachers nor a Newbie Corner within this forum. I'm only asking for some help or guidance here on a subjet that's not an easy "you mispelled bindsym in your config file" kind of problem, and I'd deeply appreciate if you could instead of critiscising this kind of action, at least point me toward a guide or some sort of direction

EDIT:
Searching through the journal I was able to find a point where my system crashed and I had to reboot it, but the first message before I got a line with "COMMAND= /path/to/reboot" was "Mounted FUSE control File System", so I don't think whatever the problem was has been logged in here

Last edited by bootzin (2016-11-07 19:45:07)

ewaller · 2016-11-07 18:34:20

bootzin, Unfortunately all we can base our responses upon are your posts. You seem to be a reasonably well versed user, but then we encounter some major "what the hells". It is puzzling that someone who has made significant modifications to the i3wm gets tripped up by the systemd journal. Okay, perhaps you have migrated from a distribution that still uses the System 5 init system. Fair enough, but that the journal is stored in binary files might have been a clue. Couple that with your use of BBS quote tags in lieu of BBS code tags around large passages of configuration files and we are stuck in the position of not knowing how to respond to you. We want to go the technical route, OTOH we are left questioning whether that is appropriate.

I have never seen nor heard about this sort of problem. I don't think others here have seen it either. This is going to put the impetus on you to dredge the information we need; we are not interested in teaching how to run the dredge.

I know you are frustrated, but work with us. And, if someone suggests that you read something, don't fight it.

bootzin · 2016-11-07 19:44:31

Thanks for the response, ewaller.
I'll admit I'm not well versed. I've just installed Arch (A week or so) and this is my first time ever with the linux environment. I know this is not the recommended distro for a complete begginer, I have been warned several times, and I have been warned that i3 was not the environment to start either. But still, I decided to do so, and I thought I knew better, I thought I knew what was coming. Well, I was wrong, terribly wrong. But that doesn't mean I'm demotivated or anything, that simply means that I'll have a lot (you know this better than me) to research. And I'm fine with that. I'm loving to learn more and more about this, but still, you guys know a ton lot more than I do.

I made my researches and fiddled around when trying to solve this problem, and it wasn't the first time I did so. But all my researches turned out to posts like "Yeah, I also have this sort of problem" or "Are you sure you're not stuck in any alternative mode (like resizing?)" And those didn't quite help. So I turned to you. Expecting some technical language I'd probably never have heard about. Expecting you guys to suggest some commands and places to search that I'd never think of. And I'd never think of those because until now I didn't even know they exist. And then I'd try to learn more about those commands and what (and how) exactly would they do (As I said I would with the journal).

So don't get me wrong if I get a little bit aggressive or defensive for being frustrated. I'm just trying to say that I've tried a whole bunch of stuff before I got here, and I know this isn't a trivial problem. I'm sorry if it seemed harsher than I intended it to be.

jasonwryan · 2016-11-07 20:02:35

bootzin wrote:

I use i3blocks, if it makes any difference, and a non-us keyboard layout (I use exec --no-startup-id setxkbmap to get my layout right)

This seems the likeliest issue. Set your keyboard correctly (see the wiki) and don't use someone else's config. Start with vanilla i3 and add things as you need them and understand what you are doing.
Jumping in and making your setup as complex as possible just leads to theses sorts of hopeless threads where there are too many moving parts for you, or the people wiling to help you, to make any sense of.

bootzin · 2016-11-07 21:14:07

I'm not using someone else's config
The wiki said to use localectl to set the keyboard layout, but mine wasn't being made persistent (After a reboot it would reset to us layout), so I figured it could be solved with that line of code. This may, however, be the issue, so I'll try to get it fixed and see if there's any change. I don't think this is the problem though, as it is set as exec and not exec_always, so it should only execute once I boot the system

jasonwryan wrote:

Start with vanilla i3 and add things as you need them and understand what you are doing.

This is precisely what I'm doing. Not only with i3, but with urxvt, i3blocks, zsh shell, vim, weechat pretty much every program that I'm installing. I'm not just copy pasting random bits and pieces of code from around the web and expecting everything to work.

seth · 2016-11-07 21:27:56

localectl should generate /etc/X11/xorg.conf.d/00-keyboard.conf and that should survive reboots.
If the file is there but the layout not applied, there's something overriding the layout when starting X (gdm?) - it may override it later.

The oddest part however is that the breakage survives a restart of i3 and require a restart of X11 - ensure to check on the grab conditions around it and also try whether you get reasonable input to xev (for the shortcuts and when this happens)
I will blindly blame GDM (which uses wayland by default, thus a completely different and maybe conflicting input mechanism) and would suggest to avoid that, start only to multi-user.target and startx from there.
(But this is really just a guess)

bootzin · 2016-11-07 23:41:16

Yeah, that file was never created, so I just tried to create an empty file in that directory and rerun localectl, that seems to have fixed the issue, I just reboot the system and my keyboard layout seems to be correct this time, without the need of that line in i3 config.

I do use gdm for logging in (I used to use cinnamon before, so I installed it and didn't remove it after I switched to i3). Maybe that is the issue, I'll have a look at it
Regarding xev, I also tried that and I seem to get every normal input out of it

bootzin · 2016-11-09 20:43:16

So, after a day or two without nothing happening, I had this problem again
I used xdotools before and after I restarted i3, I'll post the output here

http://pastebin.com/s52DtTFR

EDIT1:
I think these lines may be of relevance, but they don't seem to point any sort of problems on the system
This was before reset:
[ 27351.623] Printing all registered grabs of client pid 768 i3 (This is at around 38% of the log file)
[ 27351.629] Printing all registered grabs of client pid 768 i3 (This is at 68%)
[ 27351.629] Printing all registered grabs of client pid 791 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.768

After reset:
[ 27361.431] Printing all registered grabs of client pid 768 i3 -a --restart /run/user/1000/i3/restart-state.768
[ 27361.431] Printing all registered grabs of client pid 6745 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.768

I've searched the log file for "i3", there is a lot of repeating instances of the first 2 lines before the restart (Which makes me presume it is the initialization of i3 and i3bar themselves), and 2 instances of the restart line (Which I think is due to the restart command I used)

I may be wrong, but I don't think there is any problem in this log, any other suggestions?

EDIT2:
I fixed the keyboard layout initialization problem, yet, i3 keybindings stopped working again, so it wasn't the problem

Could this be happening due to some sort of memory leak that may be happening in the system? Which then causes an internal process of either i3 or X to stop working and consequently, the keybindings?

EDIT3:
After going through the journal I've found somthing that may be of relevance, I have mulltiple instances of this message

"MESSAGE" : "ERROR bar_poll_exited:125: [cmus] loop too fast"

[cmus] is a custom block for i3blocks that is responsible for displaying the music being played on i3bar. This message seems to point that the interval for this block is too small, hence, the loop too fast. FYI, the interval is set to repeat

Now, my question is, if I go on the detailed (normal output) journalctl, I've found that this error comes from /usr/lib/gdm/gdm-x-session. So, does this means that this error is coming from gdm, or is it from i3blocks itself?

I'll try to comment those pieces of code and see what happens with my journal

EDIT4:
Commenting those pieces of code and restarting i3 did not fix the issue, but that error dissappeared from my log. Im getting a different error now:
"MESSAGE" : "[ 36982.18 ] error 3 BadWindow request 20 minor 0 serial 57102399: \"BadWindow
As well as an error with network manager
"MESSAGE" : "<info> [1478733184.4907] device (wlp8s0): set-hw-addr: set MAC address to 42:BC:85:63:35
"MESSAGE" : "IPv6: ADDRCONF(NETDEV_UP): wlp8s0: link is not ready",
"MESSAGE" : "wlp8s0: Reject scan trigger since one is already pending",

The first error agains has its origin on a executable in gdm x session, while the second one has its origin on the NM executable itself

I'm uploading the journal file from the last 15 minutes and in the json-pretty output format
http://pastebin.com/C4WnShEj

Last edited by bootzin (2016-11-09 23:30:24)

seth · 2016-11-10 07:44:10

The Xorg log does not explain the failing shortcuts. About the same combos are grabbed and there's no present active grab covering things.
i3 should get the input events - do shortcuts remain to work when you simply restart i3 (w/o any reason, just to check whether it still grabs the proper/expected symbols)

bootzin · 2016-11-11 13:07:44

seth wrote:

do shortcuts remain to work when you simply restart i3 (w/o any reason, just to check whether it still grabs the proper/expected symbols)

Yes, all of them, I just tried it both a few times in a row and with varied delays between them.

On a second note, I tried starting only from multi-user.target and starting x from there, but the system would seemingly fail to boot, but also wouldn't give me any sort of error message nor allow me to do any sort of input, it would just stay freezed in place except for a flashing cursor. What I'm trying now, though, is to disable Wayland from the gdm custom.conf file, as I've read there are some problems regarding Wayland and Nvidia drivers (Which I currently have). Hopefully, this will fix the issue.

Last edited by bootzin (2016-11-11 13:10:48)

Arch Linux

#1 2016-11-07 01:16:18

i3 keybindings stop working at random

#2 2016-11-07 13:25:53

Re: i3 keybindings stop working at random

#3 2016-11-07 14:27:07

Re: i3 keybindings stop working at random

#4 2016-11-07 14:33:01

Re: i3 keybindings stop working at random

#5 2016-11-07 15:05:08

Re: i3 keybindings stop working at random

#6 2016-11-07 15:50:59

Re: i3 keybindings stop working at random

#7 2016-11-07 16:21:04

Re: i3 keybindings stop working at random

#8 2016-11-07 16:26:38

Re: i3 keybindings stop working at random

#9 2016-11-07 16:53:48

Re: i3 keybindings stop working at random

#10 2016-11-07 16:56:57

Re: i3 keybindings stop working at random

#11 2016-11-07 16:57:08

Re: i3 keybindings stop working at random

#12 2016-11-07 17:10:42

Re: i3 keybindings stop working at random

#13 2016-11-07 17:16:22

Re: i3 keybindings stop working at random

#14 2016-11-07 17:49:51

Re: i3 keybindings stop working at random

#15 2016-11-07 17:55:06

Re: i3 keybindings stop working at random

#16 2016-11-07 18:08:50

Re: i3 keybindings stop working at random

#17 2016-11-07 18:34:20

Re: i3 keybindings stop working at random

#18 2016-11-07 19:44:31

Re: i3 keybindings stop working at random

#19 2016-11-07 20:02:35

Re: i3 keybindings stop working at random

#20 2016-11-07 21:14:07

Re: i3 keybindings stop working at random

#21 2016-11-07 21:27:56

Re: i3 keybindings stop working at random

#22 2016-11-07 23:41:16

Re: i3 keybindings stop working at random

#23 2016-11-09 20:43:16

Re: i3 keybindings stop working at random

#24 2016-11-10 07:44:10

Re: i3 keybindings stop working at random

#25 2016-11-11 13:07:44

Re: i3 keybindings stop working at random

Board footer