From 8e06262d7a28a01c0421c94446ad61791c166e8a Mon Sep 17 00:00:00 2001 From: PROTechThor Date: Sat, 21 Nov 2020 00:20:47 +0100 Subject: [PATCH 1/2] Add Update Troublshooting, edit VM TS --- doc.md | 1 + introduction/faq.md | 34 ++------------ .../troubleshooting/update-troubleshooting.md | 47 +++++++++++++++++++ user/troubleshooting/vm-troubleshooting.md | 17 +++++++ 4 files changed, 69 insertions(+), 30 deletions(-) create mode 100644 user/troubleshooting/update-troubleshooting.md diff --git a/doc.md b/doc.md index 9b5982ab..c9082b19 100644 --- a/doc.md +++ b/doc.md @@ -132,6 +132,7 @@ Core documentation for Qubes users. * [Media Troubleshooting](/doc/media-troubleshooting/) * [Firewall Troubleshooting](/doc/firewall/#firewall-troubleshooting) * [VPN Troubleshooting](/doc/vpn-troubleshooting/) + * [Update Troubleshooting](/doc/update-troubleshooting/) ### Reference Pages diff --git a/introduction/faq.md b/introduction/faq.md index a3b39d63..83d61ae0 100644 --- a/introduction/faq.md +++ b/introduction/faq.md @@ -445,12 +445,9 @@ It begins with an explanation of the risks with such a setup. See [here][version]. -### My qubes lost Internet access after a TemplateVM update. What should I do? +### My qubes lost internet access after a TemplateVM update. What should I do? -Run `systemctl enable NetworkManager-dispatcher.service` in the TemplateVM upon which your NetVM is based. -You may have to reboot afterward for the change to take effect. -(Note: This is an upstream problem. See [here](https://bugzilla.redhat.com/show_bug.cgi?id=974811)). -For details, see the qubes-users mailing list threads [here](https://groups.google.com/d/topic/qubes-users/xPLGsAJiDW4/discussion) and [here](https://groups.google.com/d/topic/qubes-users/uN9G8hjKrGI/discussion).) +See [Update Troubleshooting](/doc/update-troubleshooting/#lost-internet-access-after-a-templatevm-update). ### My keyboard layout settings are not behaving correctly. What should I do? @@ -611,34 +608,11 @@ From a `dom0` prompt, enter: ### When I try to install a TemplateVM, it says no match is found. -For example: - -``` -[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-debian-10 -Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time... -No Match for argument qubes-template-debian-10 -Nothing to download -``` - -This normally means you already have the template installed. -It may be that you have the matching package installed, but you removed or renamed the template. -Check `rpm -q qubes-template-`. -If it lists the package, but you don't really have the template present (`qvm-ls` doesn't list it), you need to clean up leftovers of the package with `rpm -e --noscripts qubes-template-`, then install it normally. +See [VM Troubleshooting](/doc/vm-troubleshooting/#no-match-found-when-trying-to-install-a-templatevm). ### I keep getting "Failed to synchronize cache for repo" errors when trying to update my Fedora templates -This is general Fedora issue, not a Qubes-specific issue. -Usually, this is due to network problems (especially if downloading updates over Tor) or problems with the download mirrors. -Often, the problem can be resolved by trying again on a different connection (a different Tor circuit, if using Tor) or waiting and trying again later. -Here are some examples of non-Qubes reports about this problem: - - - - - - - - - - - - -More examples can be found by searching for "Failed to synchronize cache for repo" (with quotation marks) on your preferred search engine. +See [Update Troubleshooting](/doc/update-troubleshooting/#failed-to-synchronize-cache-for-repo-errors-when-updating-fedora-templates). ### I see a "Failed to start Load Kernel Modules" message on boot diff --git a/user/troubleshooting/update-troubleshooting.md b/user/troubleshooting/update-troubleshooting.md new file mode 100644 index 00000000..b273eb5e --- /dev/null +++ b/user/troubleshooting/update-troubleshooting.md @@ -0,0 +1,47 @@ +--- +layout: doc +title: Update Troubleshooting +permalink: /doc/update-troubleshooting/ +--- + +# Fixing issues that arise during updating # + + + +## “Failed to synchronize cache for repo” errors when updating Fedora templates ## + +This is general Fedora issue, not a Qubes-specific issue. +Usually, this is due to network problems (especially if downloading updates over Tor) or problems with the download mirrors. +Often, the problem can be resolved by trying again on a different connection (a different Tor circuit, if using Tor) or waiting and trying again later. +Here are some examples of non-Qubes reports about this problem: + + - + - + - + - + - + +More examples can be found by searching for "Failed to synchronize cache for repo" (with quotation marks) on your preferred search engine. + +## Lost internet access after a TemplateVM update ## + +In earlier versions of Qubes, there were situations where qubes lost internet access after a TemplateVM update. The following fix should be applied in recent versions of Qubes. + +Run `systemctl enable NetworkManager-dispatcher.service` in the TemplateVM upon which your NetVM is based. +You may have to reboot afterward for the change to take effect. +(Note: This is an upstream problem. See [this Redhat ticket](https://bugzilla.redhat.com/show_bug.cgi?id=974811)). +For details, see the qubes-users mailing list threads [here](https://groups.google.com/d/topic/qubes-users/xPLGsAJiDW4/discussion) and [here](https://groups.google.com/d/topic/qubes-users/uN9G8hjKrGI/discussion).) + +## Windows update is stuck ## + +This has nothing to do with Qubes. +[It's a longstanding Windows bug.](https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates) + +## Dom0 and/or TemplateVM update stalls when updating via the GUI tool + +This can usually be fixed by updating via the command line. + +In dom0, open a terminal and run `sudo qubes-dom0-update`. + +In your TemplateVMs, open a terminal and run `sudo dnf upgrade`. + diff --git a/user/troubleshooting/vm-troubleshooting.md b/user/troubleshooting/vm-troubleshooting.md index 5fbbf2a4..6c4a1df7 100644 --- a/user/troubleshooting/vm-troubleshooting.md +++ b/user/troubleshooting/vm-troubleshooting.md @@ -71,3 +71,20 @@ If you face this error when starting a VM, look into the VM logs at `/var/log/xe Common reasons that may be revealed are: too low memory, corrupted files or a VM crash on startup. If the error occurs as a result of too little initial memory, increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory. + +## "No match found" when trying to install a TemplateVM ## + +For example: + +``` +[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-debian-10 +Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time... +No Match for argument qubes-template-debian-10 +Nothing to download +``` + +This normally means you already have the template installed. +It may be that you have the matching package installed, but you removed or renamed the template. +Check `rpm -q qubes-template-`. +If it lists the package, but you don't really have the template present (`qvm-ls` doesn't list it), you need to clean up leftovers of the package with `rpm -e --noscripts qubes-template-`, then install it normally. + From 3303fab5e76d2e4efbae40039fe2a7c7673d2a61 Mon Sep 17 00:00:00 2001 From: Enjeck Cleopatra <32180937+PROTechThor@users.noreply.github.com> Date: Tue, 24 Nov 2020 20:02:32 +0100 Subject: [PATCH 2/2] Update update-troubleshooting.md --- user/troubleshooting/update-troubleshooting.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/user/troubleshooting/update-troubleshooting.md b/user/troubleshooting/update-troubleshooting.md index b273eb5e..459e061c 100644 --- a/user/troubleshooting/update-troubleshooting.md +++ b/user/troubleshooting/update-troubleshooting.md @@ -35,7 +35,8 @@ For details, see the qubes-users mailing list threads [here](https://groups.goog ## Windows update is stuck ## This has nothing to do with Qubes. -[It's a longstanding Windows bug.](https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates) +It's a longstanding Windows bug. +More information about this issue and solutions can be found [here](https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates). ## Dom0 and/or TemplateVM update stalls when updating via the GUI tool @@ -43,5 +44,8 @@ This can usually be fixed by updating via the command line. In dom0, open a terminal and run `sudo qubes-dom0-update`. -In your TemplateVMs, open a terminal and run `sudo dnf upgrade`. +Depending on your operating system, open a terminal in the TemplateVMs and run: +* Fedora: `sudo dnf upgrade` +* Debian: `apt-get update && apt-get dist-upgrade` +