screen session destroyed when physical screen switched away

[Michael Poole]

If I start a screen session and log out, the session persists. If I start a screen session and use my KVM to switch my main monitor to another computer, leaving this computer temporarily headless, my screen session gets destroyed. (This computer and the monitor both hook up to the KVM switch with DisplayPort.)

At least, that is some part of the condition for my screen session getting abruptly closed. Switching the KVM for a short period of time seems insufficient, but it has happened several times when I left my monitor switched to the other computer for longer periods. When my screen session gets destroyed, I also have to log back in to gdm, rather than just unlock my Wayland session.

Please revert this steaming mess of dreck known as systemd.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 07:31:02 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-29 (604 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency root=UUID=bec263be-4d36-43ae-b0ea-9ec5f97e59d7 ro quiet splash crashkernel=384M-:128M vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-10-21 (125 days ago)
dmi.bios.date: 11/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8P67 PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd11/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.systemd.logind.conf: 2017-11-18T15:57:06.638862

[Dan Streetman (ddstreet)]

please reopen if this is still an issue