Comment 2 for bug 1064110

I did it in a sub directory of my home, to be more precise ~/Projects/test

Executing the commands in your message in the same directory creates the file, adds execution permission and then launches gedit as expected.

In fact, after quickly failed, my first test was to make the file executable (chmod +x example/bin/example) and it worked.

What's more, the backtrace in my report fails on "subprocess.call(['./' + project_name], cwd='bin/', env=env)", trying to execute it. The permission change should have happened already at that point, and didn't fail.

This is what would have happened if it didn't even try the chmod part.