初始版本 和 待辦事項 #21962 的 版本 1 之間的變動
- 時間撮記:
- 2024-2-19 上午11:36:25 (13 月 前)
圖例:
- 未更動
- 新增
- 刪除
- 修改
-
待辦事項 #21962 – 描述
初始 v1 3 3 After the initial install, everything worked well. Then updates arrived and degradation sat in. So I decided to purge everything related to ```vboxadd``` and reinstall from the original source but I got an error after GUI installation suggesting me to look at ```/var/log/vboxadd-setup.log``` : 4 4 5 ``` 5 6 {{{ 6 7 Building the main Guest Additions 7.0.10 module for kernel 6.5.0-13parrot1-amd64. 7 8 Building the shared folder support module. … … 55 56 make[1]: *** [/usr/src/linux-headers-6.5.0-13parrot1-common/Makefile:2059: /tmp/vbox.0] Error 2 56 57 make: *** [/tmp/vbox.0/Makefile-footer.gmk:133: vboxvideo] Error 2 57 ``` 58 }}} 58 59 59 60 Something that came to light when looking at boot process is how ```vboxadd-service.service```fails. Perhaps one part of the problem is that there seems to 2 instances of that service created: 60 61 61 ``` 62 {{{ 62 63 ● vboxadd-service.service loaded failed > 63 64 vboxadd.service loaded active > … … 66 67 vboxdrv.service loaded active > 67 68 vboxweb-service.service loaded active > 68 ``` 69 }}} 69 70 70 71 Purging the failing entry did not fixed my problem with the local shared drive. … … 72 73 Also, it's status is useless: 73 74 74 ``` 75 {{{ 75 76 # service vboxadd-service status 76 77 × vboxadd-service.service … … 91 92 Jan 16 00:57:33 MYMACHINE systemd[1]: vboxadd-service.service: Control group is empty. 92 93 lines 1-16/16 (END) 93 ``` 94 }}} 94 95 95 96 When I ```sudo cp``` files I am greeting by ```Segmentation fault``` always at the 3rd file. … … 99 100 I actually lied when I mentionned interacting with the folder was my only problem. Before opening up an account to post this I tried drag and dropping and got the following: 100 101 101 ``` 102 {{{ 102 103 DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT). 103 104 … … 111 112 Callee: 112 113 IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d} 113 ``` 114 }}} 114 115 115 116 I thought about opening a request on the ParrotOS side but considering all of this seems to be pointing to ```VBox``` that I am now taking this chance. 116 117 117 118 More information about my system: 118 ``` 119 {{{ 119 120 i virtualbox-7.0 7.0.12-159484~Debian~bookworm amd64 Oracle VM VirtualBox 120 121 ii virtualbox-guest-utils 7.0.12-dfsg-1 amd64 x86 virtualization solution - non-X11 guest utilities 121 122 ii virtualbox-guest-x11 7.0.12-dfsg-1 amd64 x86 virtualization solution - X11 guest utilities 122 ``` 123 ``` 123 }}} 124 {{{ 124 125 Linux MYMACHINE 6.5.0-13parrot1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1parrot1 (2023-12-19) x86_64 GNU/Linux 125 126 #cat /etc/os-release … … 133 134 SUPPORT_URL="https://www.parrotsec.org/community/" 134 135 BUG_REPORT_URL="https://gitlab.com/parrotsec/" 135 ``` 136 }}} 136 137 137 138 Is running all of the latest.
