Qubes: Difference between revisions

Latest revision as of 01:11, 19 May 2024

Note: after restoring from a backup make sure to recreate the templates from the base again to save disk space because of copy-on-write.

Template VMs

In my Fedora VMs

systemctl mask packagekit
echo "vm.swappiness = 1" | sudo tee systemctl.conf
- I used this for Qubes 4.0 and 4.1, seeing if I don't need it for 4.2

dom0

RPC Policy: Set USB keyboards and mice to ask for being attached to dom0

~~Follow https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md for getting it to work with my 4k display.~~ Went back to a non-4k display.
~~Appearance -> Style -> Adwaita-dark~~
Change global copy/paste to use Win+C and Win+V
Clock format: %a %F %r

Create /usr/local/bin/vault, mapped to ctrl+shift+x

#!/bin/sh
exec qvm-run vault keepassxc

Redshift, following https://www.bryceguinta.me/install-configure-and-autostart-redshift-on-qubes-40.html, except place the config file at ~/redshift.conf so it gets included in dom0 backups and use Settings -> Session and Startup to add the autostart entry.

Advanced debugging

In the grub bootloader you can press "E" on a menu item to edit both the Linux and Xen command lines before booting. Removing "quiet" from Linux will make the boot process verbose and you can see where you get stuck.

Boot a Qubes installer USB, select rescue mode. Select option #1, enter your decryption password. Ignore the error which says "You have no Linux partitions...", it's wrong and a known issue.

If you run e.g. fdisk -l, you should see your disks and VMs. You should be able to mount dom0 with e.g. mkdir /mnt/dom0 && mount /dev/qubes_dom0/root /mnt/dom0. To do stuff in dom0, you might chroot /mnt/dom0.

If you need /proc, /sys, etc. inside the chroot, see this post for how to mount them.

@@ Line 1: / Line 1: @@
 Note: after restoring from a backup make sure to recreate the templates from the base again to save disk space because of copy-on-write.
-== VMs ==
-* DD (km-d11)
-* media (km-f34)
-** flatpak: handbrake, kdenlive, picard
-* personal (km-f34)
-** flatpak: Signal, xournalpp, hexchat, runelite, dolphinemu
-* fopf (km-f34)
-* school (km-f34)
-* dev (km-f33-dev)
-* gpg (km-f34)
-** no network
-* vault (km-f34-vault)
-** no network
-* vault-gpg (fedora-34)
-** no network
-* sys-mullvad-vpn (fedora-34)
-** see [https://micahflee.com/2019/11/using-mullvad-in-qubes/ Micah's setup guide]
 == Template VMs ==
+In my Fedora VMs
-* km-d11: fork:
+* <code>systemctl mask packagekit</code>
-** (from backports) devscripts git-buildpackage dput-ng
+* <code>echo "vm.swappiness = 1" | sudo tee systemctl.conf</code>
-** command-not-found gitk git-cola webext-ublock-origin webext-https-everywhere dh-php php-dev lintian-brush dh-buildinfo apache2-dev ack webext-privacy-badger ubuntu-dev-tools pkg-kde-tools dh-python cython3 python3-setuptools neomutt vlc gnome-system-monitor curl php-mbstring php-intl php-sqlite3 php-apcu python3-isort python3-sphinx
+** I used this for Qubes 4.0 and 4.1, seeing if I don't need it for 4.2
-* fedora-34: upstream
-* km-f34: fork:
-** enabled rpmfusion
-*** <code>sudo dnf config-manager --set-enabled rpmfusion-free</code>
-*** <code>sudo dnf config-manager --set-enabled rpmfusion-free-updates</code>
-** enabled pycharm-community, vscodium
-** fuse-exfat exfat-utils chromium ffmpeg vlc pcsc-tools mozilla-privacy-badger filezilla shotwell youtube-dl libreoffice libgnome-keyring tree ack nano mozilla-https-everywhere mozilla-ublock-origin nextcloud-client-nautilus quassel-client mosh mono-core mono-devel mono-locale-extras mediainfo curl transmission-gtk fish python3 python3.5 python3.6 python3.7 python3.8 python3.9 python3.10 composer php-cli php-mysqli git-cola gitk podman pycharm-community vscodium
-* km-f34-vault: (fork of minimal)
-** nano keepassxc qubes-gpg-split pinentry-gtk
-== Config ==
-* <code>/etc/qubes-rpc/policy/qubes.InputKeyboard</code>
-** <code>sys-usb dom0 ask,default_target=dom0</code>
-* <code>/etc/qubes-rpc/policy/qubes.InputTablet</code>
-** <code>sys-usb dom0 allow</code>
-* <code>/etc/qubes-rpc/policy/qubes.Gpg</code>
-** <code>DD gpg allow</code>
-** <code>dev gpg allow</code>
-** <code>personal gpg allow</code>
-* <code>/etc/qubes-rpc/policy/qubes.GpgImportKey</code>
-** <code>DD gpg allow</code>
-** <code>dev gpg allow</code>
-** <code>personal gpg allow</code>
-Follow https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md for getting it to work with my 4k display.
 == dom0 ==
-Appearance -> Style -> Adwaita-dark
+* RPC Policy: Set USB keyboards and mice to ask for being attached to dom0
-In <code>/etc/qubes/guid.conf</code>:
-<pre>
-secure_copy_sequence = "Mod4-c";
-secure_paste_sequence = "Mod4-v";
-</pre>
+* <s>Follow https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md for getting it to work with my 4k display.</s> Went back to a non-4k display.
-<code>/usr/local/bin/vault</code>, mapped to ctrl+shift+x
+* <s>Appearance -> Style -> Adwaita-dark</s>
+* Change global copy/paste to use Win+C and Win+V
+* Clock format: <code>%a %F %r</code>
+Create <code>/usr/local/bin/vault</code>, mapped to ctrl+shift+x
 <pre>
 #!/bin/sh
@@ Line 64: / Line 22: @@
 </pre>
+<s>Redshift, following https://www.bryceguinta.me/install-configure-and-autostart-redshift-on-qubes-40.html, except place the config file at <code>~/redshift.conf</code> so it gets included in dom0 backups and use Settings -> Session and Startup to add the autostart entry.</s>
-Clock format: <code>%a %F %r</code>
+== Advanced debugging ==
+In the grub bootloader you can press "E" on a menu item to edit both the Linux and Xen command lines before booting. Removing "quiet" from Linux will make the boot process verbose and you can see where you get stuck.
+Boot a Qubes installer USB, select rescue mode. Select option #1, enter your decryption password. Ignore the error which says "You have no Linux partitions...", it's wrong and [https://github.com/QubesOS/qubes-issues/issues/5609 a known issue].
+If you run e.g. <code>fdisk -l</code>, you should see your disks and VMs. You should be able to mount dom0 with e.g. <code>mkdir /mnt/dom0 && mount /dev/qubes_dom0/root /mnt/dom0</code>. To do stuff in dom0, you might <code>chroot /mnt/dom0.</code>
+If you need <code>/proc</code>, <code>/sys</code>, etc. inside the chroot, see [https://superuser.com/questions/165116/mount-dev-proc-sys-in-a-chroot-environment#417004 this post] for how to mount them.
-Redshift, following https://www.bryceguinta.me/install-configure-and-autostart-redshift-on-qubes-40.html, except place the config file at <code>~/redshift.conf</code> so it gets included in dom0 backups and use Settings -> Session and Startup to add the autostart entry.

Not logged in

Search

Navigation

Tools