I ran into this bug today. It took me nearly an hour to find out the problem. I never installed a copy of Xsession or removed the executable bit on it. Something in Debian created the situation.
Could we have a post-inst script that ensures the file is executable? I'm quite sure the average user it not going to solve this if they run into it. At minimum, something should write a warning to the lightdm log file.
