diff --git a/docs/_static/rtd_dark.css b/docs/_static/rtd_dark.css index 91f3a03..e6de196 100644 --- a/docs/_static/rtd_dark.css +++ b/docs/_static/rtd_dark.css @@ -172,4 +172,9 @@ .wy-menu-vertical .xref { color: #529ecf !important; } + + .kbd { + color: #404040 !important; + } + } diff --git a/docs/admin/install/troubleshoot.rst b/docs/admin/install/troubleshoot.rst index 3bec9f5..8a5a878 100644 --- a/docs/admin/install/troubleshoot.rst +++ b/docs/admin/install/troubleshoot.rst @@ -31,7 +31,7 @@ On some hardware, network devices (Ethernet and Wi-Fi) will not immediately work |screenshot_sys_net_pci_reset| -Open a ``dom0`` terminal via **Q > Settings Gear > Other Tools > Xfce Terminal**, and run the following command to list the devices connected to the ``sys-net`` VM. +Open a ``dom0`` terminal via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal**, and run the following command to list the devices connected to the ``sys-net`` VM. .. code-block:: sh @@ -84,7 +84,7 @@ cursor to before ``${xen_rm_opts}`` and type :kbd:`cpufreq=xen:hwp=off` (leave a Press :kbd:`Ctrl-x` to continue with booting. This will fix the current boot, we now need to make the fix permanent. -Once Qubes has started and you have logged in, open a ``dom0`` terminal via **Q > Settings Gear > Other Tools > Xfce Terminal** and type +Once Qubes has started and you have logged in, open a ``dom0`` terminal via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal** and type :kbd:`sudo nano /etc/default/grub` to start an editor. Move your cursor to the bottom of the file and add: :kbd:`GRUB_CMDLINE_XEN_DEFAULT="$GRUB_CMDLINE_XEN_DEFAULT cpufreq=xen:hwp=off"` diff --git a/docs/admin/reference/backup.rst b/docs/admin/reference/backup.rst index fe307b3..32d95f9 100644 --- a/docs/admin/reference/backup.rst +++ b/docs/admin/reference/backup.rst @@ -24,7 +24,7 @@ Preserve files from ``dom0`` and ``sd-gpg`` Preserve configuration files and private key material by copying them into ``dom0``. -In a ``dom0`` Terminal via **Q ▸ Terminal Emulator**: +In a ``dom0`` Terminal via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal**: .. code-block:: sh @@ -66,7 +66,7 @@ will re-download from your SecureDrop server. Ensure your storage medium is plugged in, attached to ``sd-devices``, and unlocked. -Navigate to **Q ▸ Qubes Tools ▸ Backup Qubes**, and move all VMs from +Navigate to **Q > Gear Icon (left-hand side) > Qubes Tools > Backup Qubes**, and move all VMs from "Selected" to "Available" by pressing the ``<<`` button. To target a VM for backup, highlight it and move it into the "Selected" @@ -124,7 +124,7 @@ intend to restore from a backup. Example: If you wish to restore the ``vault`` VM, rename or delete the existing ``vault`` VM prior to restoring the backup. You can do so in -**Q Apps ▸ vault ▸ Settings** (the VM must not be running). +**Q > Apps > vault > Settings** (the VM must not be running). Restore Backup (SecureDrop Workstation components) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -132,7 +132,7 @@ Plug in your backup medium and unlock it as during the backup. By default on a new system, your peripheral devices will be managed by a VM called ``sys-usb``. -Navigate to **Q Application Menu ▸ Gear Icon ▸ Qubes Tools ▸ Restore Backup**, +Navigate to **Q > Gear Icon (left-hand side) > Qubes Tools > Restore Backup**, and enter the location of the backup file. You do not need to adjust the default Restore options, unless you have made customizations to the backup. Enter the decryption/verification passphrase, and proceed to restoring the available diff --git a/docs/admin/reference/troubleshooting_connection.rst b/docs/admin/reference/troubleshooting_connection.rst index 33b1116..e5abdc2 100644 --- a/docs/admin/reference/troubleshooting_connection.rst +++ b/docs/admin/reference/troubleshooting_connection.rst @@ -38,9 +38,9 @@ connection notification, it is most likely due to one of these causes. .. important:: - Not all VMs in Qubes OS have Internet access. For example, opening the Qubes - menu (top left) and clicking **Terminal Emulator** opens a ``dom0`` terminal - without Internet access. See our :ref:`networking architecture ` + Not all VMs in Qubes OS have Internet access. For example, opening a terminal via + **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal** opens a ``dom0`` + terminal without Internet access. See our :ref:`networking architecture ` overview for additional background. If the network manager shows that you are connected to the Internet, you can @@ -216,8 +216,7 @@ To temporarily increase the timeout, and give the system more time to finish synchronizing with the server, you can perform the following steps: 1. Log into the Qubes workstation -2. Start a system Terminal in ``dom0`` by going to the Qubes Menu, then choose - *Terminal Emulator* +2. Start a system Terminal in ``dom0`` via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal** 3. Run the following commands:: qvm-service --enable sd-app SDEXTENDEDTIMEOUT_600 diff --git a/docs/admin/reference/troubleshooting_updates.rst b/docs/admin/reference/troubleshooting_updates.rst index 245a194..521d491 100644 --- a/docs/admin/reference/troubleshooting_updates.rst +++ b/docs/admin/reference/troubleshooting_updates.rst @@ -35,9 +35,7 @@ previous log file. In order to examine the most recent log file: -1. Open a terminal in ``dom0`` by clicking the Qubes menu - icon in the upper left corner of your screen, and - selecting **Terminal Emulator**. +1. Open a terminal in ``dom0`` via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal**. 2. Change to the ``~/.securedrop_updater/logs/`` directory: @@ -88,9 +86,7 @@ Note that ``dom0`` and ``apply_dom0`` are separate steps. ``dom0`` update failures ^^^^^^^^^^^^^^^^^^^^^^^^ -1. Open a terminal in ``dom0`` by clicking the Qubes menu - icon in the upper left corner of your screen, and - selecting **Terminal Emulator**. +1. Open a terminal in ``dom0`` via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal**. 2. Perform an interactive ``dom0`` update by running the following command: @@ -127,9 +123,7 @@ Signing Key. The new, valid key will already be locally available on your system, so you can perform the following steps to remove the expired key and enable this updated key: -1. Open a terminal in ``dom0`` by clicking the Qubes menu - icon in the upper left corner of your screen, and - selecting **Terminal Emulator**. +1. Open a terminal in ``dom0`` via **Q > Gear Icon (left-hand side) > Other Tools > Xfce Terminal**. 2. Run the following command: