This bug is still annoying for at least i3lock users (see http://bugs.i3wm.org/report/ticket/953).
Is there any chance to get that fixed or should it be fixed at some other place instead?
This bug is still annoying for at least i3lock users (see http:// bugs.i3wm. org/report/ ticket/ 953).
Is there any chance to get that fixed or should it be fixed at some other place instead?