[yavde-ansible] Error: retrieving gpg key timed out

dw@hdvdr:~/yavdr-ansible$ sudo -H ./install-yavdr.sh
Get:1 http://ppa.launchpad.net/ansible/ansible-2.7/ubuntu bionic InRelease [15.9 kB]                   
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]                            
Hit:3 http://gb.archive.ubuntu.com/ubuntu bionic InRelease                                             
Hit:4 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease                                     
Get:5 http://ppa.launchpad.net/ansible/ansible-2.7/ubuntu bionic/main amd64 Packages [544 B]           
Get:6 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]                         
Get:7 http://ppa.launchpad.net/ansible/ansible-2.7/ubuntu bionic/main i386 Packages [544 B]            
Get:8 http://ppa.launchpad.net/ansible/ansible-2.7/ubuntu bionic/main Translation-en [344 B]         
Fetched 181 kB in 1s (195 kB/s)                                               
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
software-properties-common is already the newest version (0.96.24.32.7).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Error: retrieving gpg key timed out.

TASK [yavdr-desktop : enable and start yavdr-xorg for the vdr user] **************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service yavdr-xorg: A dependency job for yavdr-xorg.service failed. See 'journalctl -xe' for details.\n"}

RUNNING HANDLER [Trigger Udev] ***************************************************************************************************************************************************************

RUNNING HANDLER [Restart Samba] **************************************************************************************************************************************************************

RUNNING HANDLER [Restart NFS Kernel Server] **************************************************************************************************************************************************

RUNNING HANDLER [Restart VDR] ****************************************************************************************************************************************************************
        to retry, use: --limit @/home/dw/yavdr-ansible/yavdr07.retry

PLAY RECAP ***********************************************************************************************************************************************************************************
localhost                  : ok=121  changed=91   unreachable=0    failed=1   

dw@hdvdr:~/yavdr-ansible$ journalctl -xe
                              NVRM: reconfigure your kernel without the conflicting
                              NVRM: driver(s)), then try loading the NVIDIA kernel module
                              NVRM: again.
May 01 13:30:25 hdvdr kernel: NVRM: No NVIDIA graphics adapter probed!
May 01 13:30:25 hdvdr kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 240
May 01 13:30:25 hdvdr systemd-udevd[22778]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1.
May 01 13:30:25 hdvdr kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
May 01 13:30:25 hdvdr kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 01 13:30:25 hdvdr kernel: NVRM: This can occur when a driver such as: 
                              NVRM: nouveau, rivafb, nvidiafb or rivatv 
                              NVRM: was loaded and obtained ownership of the NVIDIA device(s).
May 01 13:30:25 hdvdr kernel: NVRM: Try unloading the conflicting kernel module (and/or
                              NVRM: reconfigure your kernel without the conflicting
                              NVRM: driver(s)), then try loading the NVIDIA kernel module
                              NVRM: again.
May 01 13:30:25 hdvdr kernel: NVRM: No NVIDIA graphics adapter probed!
May 01 13:30:25 hdvdr kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 240
May 01 13:30:25 hdvdr kernel: PKCS#7 signature not signed with a trusted key
May 01 13:30:25 hdvdr kernel: PKCS#7 signature not signed with a trusted key
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nv_kthread_q_flush (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nv_kthread_q_schedule_q_item (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nv_kthread_q_item_init (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nv_kthread_q_stop (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0)
May 01 13:30:25 hdvdr kernel: nvidia_modeset: Unknown symbol nv_kthread_q_init (err 0)
May 01 13:30:25 hdvdr nvidia-persistenced[23085]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 111 has read and write permis
May 01 13:30:25 hdvdr nvidia-persistenced[23085]: PID file unlocked.
May 01 13:30:25 hdvdr nvidia-persistenced[23085]: PID file closed.
May 01 13:30:25 hdvdr nvidia-persistenced[23085]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
May 01 13:30:25 hdvdr nvidia-persistenced[23085]: Shutdown (23085)
May 01 13:30:25 hdvdr systemd[1]: nvidia-persistenced.service: Main process exited, code=exited, status=1/FAILURE
May 01 13:30:25 hdvdr systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
May 01 13:30:25 hdvdr systemd-udevd[22778]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1.
May 01 13:30:26 hdvdr kernel: PKCS#7 signature not signed with a trusted key
May 01 13:30:26 hdvdr kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
May 01 13:30:26 hdvdr kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 01 13:30:26 hdvdr kernel: NVRM: This can occur when a driver such as: 
                              NVRM: nouveau, rivafb, nvidiafb or rivatv 
                              NVRM: was loaded and obtained ownership of the NVIDIA device(s).
May 01 13:30:26 hdvdr kernel: NVRM: Try unloading the conflicting kernel module (and/or
                              NVRM: reconfigure your kernel without the conflicting
                              NVRM: driver(s)), then try loading the NVIDIA kernel module
                              NVRM: again.
May 01 13:30:26 hdvdr kernel: NVRM: No NVIDIA graphics adapter probed!
May 01 13:30:26 hdvdr kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 240
May 01 13:30:26 hdvdr systemd-udevd[22778]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1.
May 01 13:30:26 hdvdr kernel: PKCS#7 signature not signed with a trusted key
May 01 13:30:26 hdvdr kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
May 01 13:30:26 hdvdr kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 01 13:30:26 hdvdr kernel: NVRM: This can occur when a driver such as: 
lines 1398-1449/1691 86%