Comment 6 for bug 1355711

After some digging it seems that gnome-session that we ship is the same as the one that is shipped with trusty and vivid.
Same base version, same debian patches.

I'm starting to think that this may not be the cause of the issue.
It occurred to me that we might want to write a simple cli app that would log the signal it receives when the session is closed.
If things are going well, it should receive SIGTERM signal and close itself.

If the cli app receives the SIGKILL signal then something is going wrong.

That experience could be redone with a gtk app.

Tom pointed out that it may be related to a systemd service.
After all
On freya, ps -aux | grep systemd returns :

root 349 0.0 0.0 51728 1976 ? Ss 09:47 0:00 /lib/systemd/systemd-udevd --daemon
root 863 0.0 0.0 43452 1852 ? Ss 09:47 0:00 /lib/systemd/systemd-logind
cran 13392 0.0 0.0 14284 932 pts/7 S+ 15:59 0:00 grep --color=auto systemd