Comment 2 for bug 1964615

Switching launchpad-buildd to a systemd service hasn't made this go away, unfortunately. On the other hand, I do seem to be able to reproduce this every time on dogfood (or at least six out of my last six builds), so I might be able to make headway there since I can SSH into those builders. I didn't make much progress figuring it out tonight, but I need sleep, so maybe I'll spot something with fresh eyes.

My next plan is to upload a package with a "sleep $lots" in its build process, which would allow me to get in and see exactly which bit of the process tree is setting these environment variables. I think it may be libpam_systemd via schroot, but I'm not certain.