[Pkg-virtualbox-devel] Bug#880594: virtualbox-guest-x11: 98vboxadd-xclient calls notify-send before Plasma is started, causing SDDM to hang

[Leszek Lesner]

Hi, 

> what is the approach you are suggesting?
> this?
> git diff
> diff --git a/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> b/src/VBox/Additions/x11/Installer/98vboxadd-xclient index
> 985e9e7ab..8187a3fe4 100755
> --- a/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> +++ b/src/VBox/Additions/x11/Installer/98vboxadd-xclient
> @@ -23,7 +23,7 @@ done
> 
>  if ! test -c /dev/vboxguest 2>/dev/null; then
>  
>     # Do not start if the kernel module is not present.
> 
> -   notify-send "VBoxClient: the VirtualBox kernel service is not running. 
> Exiting." +   notify-send "VBoxClient: the VirtualBox kernel service is not
> running.  Exiting." &> 
>  elif test -z "${SSH_CONNECTION}"; then
>  
>     # This script can also be triggered by a connection over SSH, which is
>     not
>     # what we had in mind, so we do not start VBoxClient in that case.  We
>     do

This diff looks reasonable. It is used on Netrunner and Neptune Distros 
successfully.

> I fail to see notify-send calls in the code that might give such troubles,
> specically because they are ran in error conditions that will unlikely be
> part of Debian use-cases (e.g. /dev/vboxguest exists always in Debian
> context

The /dev/vboxguest device only exists if you boot on virtualbox. 
So for example having a live system with KDE Plasma and virtualbox-guest-{x11, 
utils,dkms} so that it boots on virtualbox and real machines will work pretty 
fine on virtualbox but causes the delay on "real" hardware as it will trigger 
the notify-send code. 


Greetings
Leszek
-- 
ZevenOS / Neptune Team
https://neptuneos.com
Leszek Lesner <leszek at zevenos.com>