diff options
| author | Simon Rettberg | 2020-09-21 16:10:47 +0200 |
|---|---|---|
| committer | Simon Rettberg | 2020-09-21 16:10:47 +0200 |
| commit | 296eaf36443d47ba0c40e59aaab5155aa12e2690 (patch) | |
| tree | a0102bb036207d9332a59477dfa909a1524744be /core/modules/remote-access | |
| parent | [run-virt] openslx.exe: Fix: Restore WINNT4.0 compatibility (diff) | |
| download | mltk-296eaf36443d47ba0c40e59aaab5155aa12e2690.tar.gz mltk-296eaf36443d47ba0c40e59aaab5155aa12e2690.tar.xz mltk-296eaf36443d47ba0c40e59aaab5155aa12e2690.zip | |
[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.
Diffstat (limited to 'core/modules/remote-access')
| -rwxr-xr-x | core/modules/remote-access/data/opt/openslx/scripts/systemd-remote_x_config | 6 |
1 files changed, 6 insertions, 0 deletions
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 <<END rpc-port = 7551 END +# Currently the zaphod head solution on intel can create a mysterious +# problem where the cursor turns into an X and everything stops working +# disable any warnings and just let the screen enter standby +exit 0 + +# DISABLED BELOW [ "$driver" = "intel" ] || exit 0 # Currently only intel supports zaphod head split # Enable the dual-screen setup |