Blame VirtualBox-5.2.6-xclient.patch

32e434
diff -up VirtualBox-5.2.6/src/VBox/Additions/x11/Installer/98vboxadd-xclient~ VirtualBox-5.2.6/src/VBox/Additions/x11/Installer/98vboxadd-xclient
32e434
--- VirtualBox-5.2.6/src/VBox/Additions/x11/Installer/98vboxadd-xclient~	2018-01-15 15:49:57.000000000 +0100
32e434
+++ VirtualBox-5.2.6/src/VBox/Additions/x11/Installer/98vboxadd-xclient	2018-02-07 12:13:51.578170786 +0100
32e434
@@ -21,13 +21,9 @@ for i in $HOME/.vboxclient-*.pid; do
32e434
     test -w $i || rm -f $i
32e434
 done
32e434
 
32e434
-if ! test -c /dev/vboxguest 2>/dev/null; then
32e434
-   # Do not start if the kernel module is not present.
32e434
-   notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."
32e434
-elif test -z "${SSH_CONNECTION}"; then
32e434
-   # This script can also be triggered by a connection over SSH, which is not
32e434
-   # what we had in mind, so we do not start VBoxClient in that case.  We do
32e434
-   # not use "exit" here as this script is "source"d, not executed.
32e434
+# Do not start if the kernel module is not present; or if this script is
32e434
+# triggered by a connection over SSH.
32e434
+if [ -c /dev/vboxguest -a -z "${SSH_CONNECTION}" ]; then
32e434
   /usr/bin/VBoxClient --clipboard
32e434
   /usr/bin/VBoxClient --checkhostversion
32e434
   /usr/bin/VBoxClient --display