1
0
forked from pool/virtualbox
virtualbox/VirtualBox-5.2.10-xclient.patch

24 lines
1.2 KiB
Diff
Raw Normal View History

Index: VirtualBox-7.0.4/src/VBox/Additions/x11/Installer/98vboxadd-xclient
===================================================================
--- VirtualBox-7.0.4.orig/src/VBox/Additions/x11/Installer/98vboxadd-xclient
+++ VirtualBox-7.0.4/src/VBox/Additions/x11/Installer/98vboxadd-xclient
Accepting request 1036720 from home:lwfinger:branches:Virtualization added file "set_noexec_stack.patch" to remove executable stack in yasm-compiled routines addwd file "fix_v7_build.patch" added file "VBoxDDR0.r0" deleted file "/vb-6.1.16-modal-dialog-parent.patch" VirtualBox 7.0.2 (released October 20 2022) This is a maintenance release. The following items were fixed and/or added: Known issue: VMs having more than one vCPU configured will not work properly on macOS Catalina due to an unknown memory corruption issue. Either lower the number of vCPUs to 1 or upgrade to BigSur or later where the issue does not occur Main: Fixed issue when VBoxSVC could become unresponsive if Extension Pack was not installed (bug #21167) Linux Guest Additions: Introduced initial support for kernel 6.1 Linux Guest Additions: Fixed issue when VBoxClient seamless service caused a crash of some X11 applications (bug #21132) GUI: Fixed a glitch in the log viewer which was causing wrong log file to be saved (bug #21156) VirtualBox 7.0.0 (released October 10 2022) This is a major update. The following major new features were added: Virtual machines can be fully encrypted now, including the VM config logs and saved states (CLI only for now) OCI: Cloud virtual machines can be added to Virtual Machine Manager and controlled as local VMs OCI: Cloud networks can now be configured via Network Manager tool same way as it is done for Host-only and NAT networks GUI: Added a new utility similar to "top" or "resource monitor" which lists peformance statistics (CPU usage, RAM usage, disk I/O rate, etc.) of running guests GUI: Reworked the new vm wizard to integrate the unattended guest OS installation and to have a more streamlined work flow GUI: Added a new help viewer widget which enables the user manual to be navigated and searched GUI: Adding new notification center unifying most of running progresses and error reporting around the GUI GUI: Improved theme support on all platforms. Linux and macOS use native engine while for Windows host it is separately implemented. GUI: Large icon update. Audio recording: Now using Vorbis as the default audio format for WebM containers. Opus is no longer being used. Audio: Added "default" host driver type to make it possible to move VMs (appliances) between different platforms without the need of changing the audio driver explicitly. When the "default" driver is selected, the best audio backend option for a platform will be used. This is the default for newly created VMs. Guest Control: Implemented initial support for automatic updating of Guest Additions for Linux guests Guest Control: Implemented ability to wait for and/or reboot the guest when updating Guest Additions via VBoxManage VBoxManage: Added Guest Control "waitrunlevel" sub-command to make it possible to wait for a guest to reach a certain run level Linux Guest Additions: Reworked guest screen re-size functionality, added basic integration with some of guest Desktop Environments Devices: Implemented new 3D support based on DirectX 11 (and DXVK on non Windows hosts) Devices: Added virtual IOMMU devices (Intel and AMD variant) OBS-URL: https://build.opensuse.org/request/show/1036720 OBS-URL: https://build.opensuse.org/package/show/Virtualization/virtualbox?expand=0&rev=663
2022-11-18 22:49:33 +01:00
@@ -31,15 +31,9 @@ for i in $HOME/.vboxclient-*.pid; do
test -w $i || rm -f $i
done
-if ! test -c /dev/vboxguest 2>/dev/null; then
- # Do not start if the kernel module is not present.
- # Execute notify-send in the back-ground to avoid racing with sddm,
- # as notify-send may wait for sddm to start while it waits for us to exit.
- 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
- # not use "exit" here as this script is "source"d, not executed.
+# Do not start if the kernel module is not present; or if this script is
+# triggered by a connection over SSH.
+if [ -c /dev/vboxguest -a -z "${SSH_CONNECTION}" ]; then
/usr/bin/VBoxClient --clipboard
/usr/bin/VBoxClient --checkhostversion
/usr/bin/VBoxClient --seamless