sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

** Summary changed:

- [1.1.1] Multiple IDE sessions should be possible for special situations (for experts only) --- fixed 1.1.2 2017-10-17
+ [request 1.1.x] Multiple IDE sessions should be possible for special situations (for experts only) --- fixed 1.1.2 2017-10-17

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1724192

Title:
  [request 1.1.x] Multiple IDE sessions should be possible for special
  situations (for experts only) --- fixed 1.1.2 2017-10-17

Status in Sikuli:
  Fix Committed

Bug description:
  ------- implemented solution 
  (experimental - you should know what you are doing)

  add an option -m to the command line start command for the IDE
  ------------------------------------------------------------------
  We are running Sikuli on a Debian Linux VM from xrdp connected thin client machines, that all have local keyboards and monitors, but share the same Linux environment

  We could without problem launch the Sikuli 1.0rc3 IDE on multiple remote thin clients.
  When launching the Sikuli 1.1.1 IDE, Sikuli now creates a generic but user-owned lock file in /tmp, effectively blocking all other users from launching the Sikuli IDE on their own

  Is there a way to make is possible to run multiple IDE instances by
  multiple users on multiple remote thin clients ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1724192/+subscriptions