docs: update README.md with font download link and VSCode trust settings

- Replaced the font download link for LibreOffice with a new source.
- Added instructions for configuring VSCode to disable workspace trust prompts, enhancing user experience.
- Maintained existing content while improving clarity and providing additional setup guidance.
This commit is contained in:
yuanmengqi
2025-07-28 15:13:37 +00:00
parent 70cf3e6982
commit af64f4ef49

View File

@@ -442,7 +442,7 @@ Since for some examples like change the settings of certain software, we hardcod
##### LibreOffice font installation
Some examples in LibreOffice Impress use non-default system fonts, and you need to download the corresponding **TTF files** and put them in the system fonts directory.
[Here](https://drive.usercontent.google.com/download?id=1UzmdsfUQRTnvCxkvWrKguwZM3G5eQk87&export=download&authuser=0&confirm=t&uuid=70b9fbb7-9585-4aa4-a2c0-a7d6126469a0&at=AEz70l4rdEjdxBpqkLyW9lcil6S5:1740142224052) we provides all the fonts downloaded, just download it, and unzip to the system fonts directory (which usually `usr/share/fonts/`).
[Here](https://huggingface.co/datasets/xlangai/ubuntu_osworld_file_cache/resolve/main/fonts_20250608_fixed.zip) we provides all the fonts downloaded, just download it, and unzip to the system fonts directory (which usually `usr/share/fonts/`).
```bash
unzip fonts.zip -d /usr/share/fonts/
```
@@ -488,6 +488,20 @@ touch ~/.local/share/keyrings/login.keyring
Or you can use any ways to disable the keyring service, which will prevent Chrome from requesting a password input.
3. VSCode Trust Settings:
To prevent VSCode from showing "Do you trust this workspace?" dialog when opening projects, configure the following setting:
```bash
# Open VSCode
# Go to File -> Preferences -> Settings (or press Ctrl+,)
# In the search bar, type "workspace trust"
# Find "Security: Workspace Trust Enabled" and uncheck it
# Find "Security: Workspace Trust Banner" and set to "never"
# Find "Security: Workspace Trust Empty Window" and uncheck it
# Find "Security: Workspace Trust Startup Prompt" and set to "never"
```
This disables the workspace trust feature and prevents trust dialog prompts when opening projects.
### Network Configuration
@@ -539,20 +553,30 @@ The following is the screenshot of the VLC configuration:
When VLC is open, the service will be running on port 8080.
##### Chrome Configuration
When you open Chrome through the GUI interface, it doesn't automatically enable remote debugging port 1337 (the port we set for controlling the client machine's Chrome through the host, which gets forwarded to 9222).
This is because GUI startup and command-line startup use different parameters.
The consequence is that once Chrome is closed and reopened, it will fail to connect.
To ensure Chrome uses consistent debugging ports even after being closed and reopened, follow these steps:
1. Create or edit Chrome desktop entry:
```bash
sudo nano /usr/share/applications/google-chrome.desktop
sudo vim ~/.local/share/applications/google-chrome.desktop
```
If that doesn't work, try:
```
sudo vim /usr/share/applications/google-chrome.desktop
```
2. Modify the Exec lines to include debugging port:
```bash
# Find lines starting with "Exec=" and add the following flags:
--remote-debugging-port=1337 --remote-debugging-address=0.0.0.0
2. Modify **all** the `Exec` lines to include debugging port, for example, change:
```
Exec=/usr/bin/google-chrome-stable %U
```
into:
```
Exec=/usr/bin/google-chrome-stable --remote-debugging-port=1337 --remote-debugging-address=0.0.0.0 %U
```
In cases where need Chrome, the 1337 will be forwarded to 9222 in the virtual machine via socat.
In cases where Chrome is needed, the 1337 will be forwarded to 9222 in the virtual machine via socat.
### Miscellaneous Settings