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. Read the wiki pages
http://code.google.com/p/multiseat-wizard-bicefalo/wiki/Manual and
http://code.google.com/p/multiseat-wizard-bicefalo/wiki/Hardware
What is the expected output? What do you see instead?
On page http://code.google.com/p/multiseat-wizard-bicefalo/wiki/Manual
"be patience": should be "be patient".
"In order to shut down a multiseat computer. Close all seats sessions and press
physical power off buttom (only one click). Computer will shut down normally."
should be
"In order to shut down a multiseat computer, close all seat sessions and press
the physical power off buttom (only one click). The computer will shut down."
On page http://code.google.com/p/multiseat-wizard-bicefalo/wiki/Hardware
"Does my computer work ok with multiseat?" should be "Will my computer support
multiseat?"
"You must run so programs as seats you are going to set up." should be "You
must run as many programs as seats you are going to set up."
Moreover the sentence "Run in your computer several sessions of programs that
you are going to use in your multiseat system." is unclear:
does it mean different user accounts, the same program being opened in each
user session at the same time, or does it mean one user using the application
in different independant processes?
What version of the product are you using? On what operating system?
We are not using the product yet. Our operating systems are Ubuntu 12.04
x86_64, and Fedora 17.
Please provide any additional information below.
Thank you for releasing multiseat-wizard-bicefalo.
Original issue reported on code.google.com by [email protected] on 22 Sep 2012 at 5:29
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 22 Sep 2012 at 5:29The text was updated successfully, but these errors were encountered: