Blame VirtualBox-5.2.10-xclient.patch

12e911
--- ./src/VBox/Additions/x11/Installer/98vboxadd-xclient.orig	2020-06-06 06:20:12.079227656 +0100
12e911
+++ ./src/VBox/Additions/x11/Installer/98vboxadd-xclient	2020-06-06 06:26:55.886940895 +0100
12e911
@@ -21,15 +21,9 @@ for i in $HOME/.vboxclient-*.pid; do
Hans de Goede 32e434
     test -w $i || rm -f $i
Hans de Goede 32e434
 done
Hans de Goede 32e434
 
Hans de Goede 32e434
-if ! test -c /dev/vboxguest 2>/dev/null; then
Hans de Goede 32e434
-   # Do not start if the kernel module is not present.
8643fd
-   # Execute notify-send in the back-ground to avoid racing with sddm,
8643fd
-   # as notify-send may wait for sddm to start while it waits for us to exit.
8643fd
-   notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting." &
Hans de Goede 32e434
-elif test -z "${SSH_CONNECTION}"; then
Hans de Goede 32e434
-   # This script can also be triggered by a connection over SSH, which is not
Hans de Goede 32e434
-   # what we had in mind, so we do not start VBoxClient in that case.  We do
Hans de Goede 32e434
-   # not use "exit" here as this script is "source"d, not executed.
Hans de Goede 32e434
+# Do not start if the kernel module is not present; or if this script is
Hans de Goede 32e434
+# triggered by a connection over SSH.
Hans de Goede 32e434
+if [ -c /dev/vboxguest -a -z "${SSH_CONNECTION}" ]; then
Hans de Goede 32e434
   /usr/bin/VBoxClient --clipboard
Hans de Goede 32e434
   /usr/bin/VBoxClient --checkhostversion
5c7cc3
   /usr/bin/VBoxClient --seamless