Indeed, this issue had been fixed in revision rev#67796.
For now, the workaround is to add at least one environment variable using the debugging options dialog.