It seems very unlikely to me that the processing script has the wrong file permissions  (which is what your problem looks like to me). Simple solution if that is the case:-
chmod +x processing

A few tips for a newbie linux/processing user:-
The console is your friend, but you can add processing to your menu or create a desktop launcher.

To determinine whether your linux box can run OPENGL
glxinfo|grep renderer
glxinfo|grep vendor

of course you need to find out what the result means to you, but the result you don't  want is a generic (software emulated opengl?) driver eg vendor Mesa when you wanted Tungsten Graphics etc.

To troubleshoot rogue java processes:-
pgrep java
To kill all of them:-
pkill java (doesn't always work)
or kill 2222 (say 2222 was the rogue java process running)
or be tough and do (as root if necessary)
kill -s KILL 2222

If the window freezes (say when running a misbehaving opengl applet):-

Use 'Alt F2....F4' to move to another virtual desktop, and run a console from there.

Another useful way of checking your graphics set up is to
dmesg| grep drm (particularly with recent kernels)

martin_p wrote on Mar 29^th, 2010, 11:02pm:


Another useful one is:
glxinfo | grep "direct rendering"


martin_p wrote on Mar 29^th, 2010, 11:02pm:


A note of caution, pkill will kill all process related to java, whether they're processing or not. So if you're running any other java-based program while executing 'pkill java', they will all be killed. Use 'pgrep java -l' to find out how many process you will kill if you run 'pkill java'.