You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Installed the latest multiseat-wizard on Ubuntu 12.04.1 64bit
2. Applied the 64bit Xephyr from previous Issue
3. System has:
- the latest integrated Intel CPU/GPU (i7-3770 CPU)
- two monitors (DP:2560x1600, HDMI::1920xx1200]
- two standard USB mice and keyboards
4. Installation of wizard seemed to go well. Selected 2 seats. Assigned both
monitors, mice and keyboards. After skipping assigning any additional USB
ports, a small 'The End' pop-up window appeared after a few moments. Had to
manually closed the program afterwards. Not sure if this is normal.
What is the expected output? What do you see instead?
Multiseat accounts were created. Entering the multiseat account, each monitor
displays a black&white terminal style login shell:
- Seat1, Escritorio Xephyr 1
- Seat2, Escritorio Xephyr 2
However both mice and keyboards are completely unresponsive. No cursor is
visible on either screen. Typing on either keyboard produces nothing. System
has to be power cycled to exit.
What version of the product are you using? On what operating system?
Multiseat-wizard was latest from svn as of Sept 25, 2012. System has Ubuntu
12.04.1 64bit OS.
Please provide any additional information below.
I recorded the output of the multiseat wizard from its terminal where it was
run. I've attached this log (multiseat_output.log). I do see this message
printed a few times:
# For some reason I was unable to set the following in xorg.conf
# We need to turn off power management of the main X server because
# it doesn't see either of the keyboards and the mice so it will
# enter power-saving mode after 10 minutes
export DISPLAY=:0.0
xset s off
xset dpms 0 0 0
xset -dpms
Appreciate any insight on this situation. Thank you.
Original issue reported on code.google.com by [email protected] on 26 Sep 2012 at 7:41
Original issue reported on code.google.com by
[email protected]
on 26 Sep 2012 at 7:41Attachments:
The text was updated successfully, but these errors were encountered: