Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xephyr help !! isolating keyboard #351

Closed
velcrine opened this issue May 9, 2021 · 4 comments
Closed

Xephyr help !! isolating keyboard #351

velcrine opened this issue May 9, 2021 · 4 comments
Labels

Comments

@velcrine
Copy link

velcrine commented May 9, 2021

Hello mviereck sir, U are legend of Xserver. I need one help.

in x11Docker script, what argument can I attach to Xephyr so that I can start migrating the script to allow exclusive/isolated/non-sharing input devices access to each Xephyr x session.
Earlier we were able to use evdev, but as now the support is gone, what can I do sir.
Help is very much appreciated

@mviereck
Copy link
Owner

mviereck commented May 9, 2021

I am not sure if I understand your question.
Input devices are mouse or keyboard. The currently active Xephyr window gets mouse and keyboard events, inactive Xephyr windows don't. So what do you want to isolate more than that?

@velcrine
Copy link
Author

Thanks mviereck for quick response.
By isolation, I meant a multiseat kind of setup. Where keyboard and mouse for one person are attached to just one window / monitor. His keyboard can not enter my workera, and can't give any input. However, I was able to provide that using older version of Xephyr that had evdev support. But I am stuck with audio now. How can I make sure, audio from one docker image, reaches to a particular audio device( head phones). So that audio from multiple docker containers dont mix up, and reach to seperate audio devices.
Thanks

@mviereck
Copy link
Owner

How can I make sure, audio from one docker image, reaches to a particular audio device( head phones). So that audio from multiple docker containers dont mix up, and reach to seperate audio devices.

I am not sure about this. I am not familiar with this kind of setup.
Basically I see two ways:

  • x11docker option --alsa shares entire /dev/snd. If you have multiple audio devices (one for each user) you could share only the desired one to a container instead of using --alsa. Something like x11docker --xephyr -- --device /dev/snd/hwC1D0 -- image for one user and a different device for another user. However, I don't know which device files are exactly needed inside of /dev/snd.
  • x11docker option --pulseaudio connects the container to pulseaudio server on host. pulseaudio should be configurable to distribute sound input and output according to containers and users. However, setting this up might be a mess, and maybe users could be able to change the config within their container to listen to the aothers.

@velcrine
Copy link
Author

Thanks mviereck. That has given me info enough.
I am very grateful for x11docker project and its dedication for community. I am a developer in golang. Tell me in case I can be of any help in any project of yours, that doesn't use shell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants