Comment 110 for bug 1252121

I have to agree with Philipp, I also, and perhaps somewhat naively, believed it would just be a case of comparing what has changed in newer version with the previous version that didn't have any problem and working out what is causing this problem. Or maybe just reverting to an earlier version of systemd-shim until the problem can be resolved? I'd be happy to test things, I'd even be happy to look over some code and do a spot the difference if that is any good?

I've never had this problem before in any version of Ubuntu that I have used (that I can remember) right back to Warty, so this must be something simple that has recently been changed, right?