Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a few menu invocations & dark mode issue #250

Merged
merged 2 commits into from
Aug 5, 2024
Merged

Fix a few menu invocations & dark mode issue #250

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
768edb2
Standardize menu invocations and fix a few missing ones
eloquence Jul 22, 2024
5f5955d
Render kbd class visible in dark mode
eloquence Jul 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/_static/rtd_dark.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,4 +172,9 @@
.wy-menu-vertical .xref {
color: #529ecf !important;
}

.kbd {
color: #404040 !important;
}

}
4 changes: 2 additions & 2 deletions docs/admin/install/troubleshoot.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As was discussed in #228, unfortunately there are two settings gears visible at the same time in the menu, so we have to disambiguate.


.. code-block:: sh

Expand Down Expand Up @@ -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"`
Expand Down
8 changes: 4 additions & 4 deletions docs/admin/reference/backup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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**:
nathandyer marked this conversation as resolved.
Show resolved Hide resolved

.. code-block:: sh

Expand Down Expand Up @@ -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"
Expand Down Expand Up @@ -124,15 +124,15 @@ 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)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
Expand Down
9 changes: 4 additions & 5 deletions docs/admin/reference/troubleshooting_connection.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <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 <Networking Architecture>`
overview for additional background.

If the network manager shows that you are connected to the Internet, you can
Expand Down Expand Up @@ -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
Expand Down
12 changes: 3 additions & 9 deletions docs/admin/reference/troubleshooting_updates.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down Expand Up @@ -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:
Expand Down Expand Up @@ -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:

Expand Down