From b6ab529b5f91bffc2717e54ac030d758a71033b3 Mon Sep 17 00:00:00 2001 From: Simon Rettberg Date: Wed, 5 Aug 2020 15:03:19 +0200 Subject: [remote-access] Only use ZaphodHead xorg config for intel This does nothing at best with other drivers, but with vmware it actually causes a segfault in the xserver. --- .../data/opt/openslx/scripts/systemd-remote_x_config | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (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 bf498ec0..d172dda9 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 @@ -25,9 +25,6 @@ case "$driver" in vmwgfx) driver="vmware" ;; esac -# Enable the dual-screen setup -sed "s/%DRIVER%/$driver/g" "/opt/openslx/remote-access/xorg.conf" > "/etc/X11/xorg.conf.d/16-remote-access.conf" - # Enable LoingRPC of greeter mkdir -p /etc/lightdm/qt-lightdm-greeter.conf.d cat > /etc/lightdm/qt-lightdm-greeter.conf.d/13-loginrpc.conf < /etc/lightdm/qt-lightdm-greeter.conf.d/13-loginrpc.conf < "/etc/X11/xorg.conf.d/16-remote-access.conf" + # Force :0.0 usage cat > /etc/X11/Xsession.d/00-force-screen0 <