Thanks for testing.
Tried again, after using onyx to rebuild LaunchServices as was suggested in another
thread, and the result is the same. You did save as and application, I presume?
The app does run, I see it in ActivityMonitor, and I have to kill it there to stop it.
But it still does nothing. Tried many times.
Thanks, all the permissions are as you say.
But after login into my clean lion account, and back into
the SL upgrade account, now it suddenly works.
The upgrade was made on a clone of my MacBook Pro account, which
is still running SL. I wonder if that could have something to do with it.
I don't think it is solved forever, and I will report here if the problem comes back.
I believe that I have solved this.
The problem did not go away by itself. After rebooting Automator apps either worked, or they did not work.
This was true for all automator-made apps, not just the one described above. Nothing do to with Desktop
or creating a folder there. Sometimes there was no problem after three successive reboots, then it came
back again. All automator-made apps were blocked on my account, but not on a second user account.
The origin of the problem is, apparently, that I used two Automator-made apps as a startup item on login.
This has always worked fine under Snow Leopard, but it seems that lion cannot handle that. I suspect some
kind of timing problem. The apps do seem to start a lot faster in lion, and perhaps they somehow get
into each others way and then block anything else.
Now I have combined the two apps into a single one, and the problem has not come back.
In that sense I consider it solved, but I would still like to know what is really going on.