Bug 77310

When I boot the system up docked with the lid closed and an external monitor connected, systemd is recognizing this and works fine. The issue starts when the system is suspended un-docked and no external monitor and then resumed when docked. 

The system is started un-docked and without an external monitor connected. The system boots fine as that the lid is open. After working for a couple of hours, I close the lid and the system is automatically suspending and remains suspended over night. The next morning I take the system to the office where I have a docking station with an external monitor connected. I put the laptop in the docking station and press the power button on the docking station to resume the system. I do not open the lid !!

The system resumes and the external monitor shows the screensaver/desktop. After about 3 minutes the system suddenly suspends again. Pressing the power button again, resumes the system, but directly goes to suspend state again after about 30 seconds. 

In order for me to work with the system I need either to reboot the system or to open the lid. Even if I open the lid no screen is shown there as that the external monitor is attached. 

I suspect that systemd is reading the system state during boot-up and does not refresh the system state upon resuming which causes that the external monitor is not detected and therefore a suspend is initiated as that the lid is closed. 

I haven't tried the other way around to boot the system with an external monitor and then to suspend it and resume it without an external monitor as that the powerbutton is not reachable without opening the lid. But I expect that systemd will make the same mistake and assumes that an external monitor is connected.