sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

** Summary changed:

- X-1.0rc2: Ubuntu: other users can't run sikuli-ide after first user did it
+ X-1.0rc2: Ubuntu: other users can't run sikuli-ide after first user did it --- workaround

** Description changed:

+ **** the workaround from comment #4
+ 
+ Run this before starting sikuli from the command line...
+ 
+ mkdir libs
+ 
+ After starting Sikuli IDE, you should see some files in libs instead of
+ /tmp/tmplib
+ 
+ -----------------------------------
+ 
  In Sikuli X 1.0rc2 on Ubuntu Lucid 64 bit and 32 bit systems, users logging in after a user who has run sikuli-ide and who try to run it also get error messages like:
  [error] Can't load native lib JXGrabKey
  java.io.FileNotFoundException: /tmp/tmplib/libJXGrabKey.so (Permission denied)
  
  This is caused by Sikuli writing cache files below /tmp/tmplib that
  subsequent users don't have permission to access. Sikuli should either
  clean this up on exit or create separate cache directories for each
  username running it.

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

Title:
  X-1.0rc2: Ubuntu: other users can't run sikuli-ide after first user
  did it --- workaround

Status in Sikuli:
  New

Bug description:
  **** the workaround from comment #4

  Run this before starting sikuli from the command line...

  mkdir libs

  After starting Sikuli IDE, you should see some files in libs instead
  of /tmp/tmplib

  -----------------------------------

  In Sikuli X 1.0rc2 on Ubuntu Lucid 64 bit and 32 bit systems, users logging in after a user who has run sikuli-ide and who try to run it also get error messages like:
  [error] Can't load native lib JXGrabKey
  java.io.FileNotFoundException: /tmp/tmplib/libJXGrabKey.so (Permission denied)

  This is caused by Sikuli writing cache files below /tmp/tmplib that
  subsequent users don't have permission to access. Sikuli should either
  clean this up on exit or create separate cache directories for each
  username running it.