Re: [i3] Multiple Xscreens without Xinerama/XrandR
- From: Lukas Sabota <ltsmooth42@xxxxxxxxx>
- To: "Discussions/Questions about the i3 window manager" <i3-discuss@xxxxxxxxxxxxx>
- Date: Fri, 27 Apr 2012 13:20:45 -0400
On Thu, Apr 26, 2012 at 4:35 PM, Lukas Sabota <ltsmooth42@xxxxxxxxx> wrote:
Quoting Lukas Sabota (2012-04-26 20:21:42)
However, I would much rather have separate X screens with Xinerama
disabled,
each running their own i3 instance. In an attempt to try this, I
configured i3
to spawn on each of my DISPLAYs (:0.0 :0.1 :0.2) in my ".xinitrc" file.
This
sucessfully spawned i3 instances on each of my X screens -- however I am
experiencing input problems. Keyboard shortcuts only seem to work on a
single
i3 instance. The other two i3 instances that are spawned are unusable
since
one i3 instance catches all of the keyboard events.
Are you using the latest version of i3? If not, upgrade. If that doesn’t
help,
please come to IRC so that we can debug the problem more interactively.
Mailing
lists are tedious.
Hello Michael,
I am using i3-wm 4.2-1 along with xorg 1.12.1 on Arch Linux. I'm idling
in the channel atm (prg318) . Hopefully between the two of us and others
in IRC we can diagnose the issue!
Hello,
Michael was nice enough to help me diagnose this issue in IRC and find a
suitable workaround for the issue. Just to clarify the issue:
After starting i3 on three separate x screens (no xinerama), all keyboard
commands (mod+enter etc) will only trigger events on ONE of the 3 xscreens
regardless of where the cursor was.
A suitable workaround is to use the "swarp" utility. After moving the
cursor to another xscreen/i3 session using "swarp", the screen can be used
perusual (the screen where the cursor is located will handle the keyboard
events). For example, after running "startx" my keyboard focus will only
direct to screen :0.0. After running the following command, keyboard input
will be accept on :0.1 when the cursor is located on that screen:
DISPLAY=:0.1 swarp 50 50
I plan to work some "swarp" commands into my xinitrc so that after
"startx", input is handled properly. I hope this may be found useful for
someone in the future with a similar configuration as mine.
Thanks again Michael for taking the time to assist me in diagnosing this
issue!
Best Regards,
Lukas Sabota
Other related posts: