From 296eaf36443d47ba0c40e59aaab5155aa12e2690 Mon Sep 17 00:00:00 2001 From: Simon Rettberg Date: Mon, 21 Sep 2020 16:10:47 +0200 Subject: [remote-access] Disable ZaphodHead on intel This can cause the X session to become unresponsive under certain, currently unknown circumstances. It seems to involve VMware 15.5.x vs. 15.1.x previously, and happens after the xscreensaver tried to start once (and fails). This hasn't been reproduced everywere and remains a mystery, but until this feature works reliably, we have to forgo the warning messages on the physically connected screen and let it enter standby instead. --- .../remote-access/data/opt/openslx/scripts/systemd-remote_x_config | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'core/modules/remote-access') diff --git a/core/modules/remote-access/data/opt/openslx/scripts/systemd-remote_x_config b/core/modules/remote-access/data/opt/openslx/scripts/systemd-remote_x_config index d172dda9..fd2a708c 100755 --- a/core/modules/remote-access/data/opt/openslx/scripts/systemd-remote_x_config +++ b/core/modules/remote-access/data/opt/openslx/scripts/systemd-remote_x_config @@ -32,6 +32,12 @@ cat > /etc/lightdm/qt-lightdm-greeter.conf.d/13-loginrpc.conf <