Comment 4 for bug 1347788

I just marked this as affecting me as well. However, I had to add one other step to reproduce the bug using the instructions above. As the bug title says, the problem only happens when the working directory (not necessarily the one on which find is being run) is unreadable or not executable by the current user. So, I had to add "chmod u-r ./2" before the line "cd 2". The find command then fails with

find: pred.c:1932: launch: Assertion `starting_desc >= 0' failed.
Aborted (core dumped)

As a real-world example of this bug, this can happen when you are logged-in as root, and in /root and "su" to another user. You are therefore left in /root but without having read/execute permissions to it. find with -exec therefore fails, even if you are searching another directory. This came up while using Puppet, which included a 'find' command. Of course, switching to another directory solved the problem.