Reinstalling Qubes-Whonix TemplateVMs page created and finished. Mistakenly added all content using admin privileges so I deleted page and started over. Also I’m not sure about the page title. Know it needs to be a redirect from Qubes/ ?
Any other advantage of Manual Reinstallation method other than The advantage of this method is, that it also works with non-Fedora based Qubes dom0 UpdateVMs, i.e. also with Debian based Qubes dom0 UpdateVMs.
(just now added by me).?
this is from when i was creating a chapter for it in the guide i work on a couple months ago. i don’t know if it’s with the latest version. additionally, another bug i forgot to mention was that the ability to even select omemo encryption in a chat window would sometimes be haphazard. the omemo icon simply wouldn’t display.
i have not reported these as bugs to the devs since i am not sure if it had something to do with the virtualbox environment i was experimenting with yet. as you may recall, i had a weird error where coyim and torbrowser appeared to be fighting with each other, and that was fixed by increasing the ram available to the workstation. if there is a strong desire to move to gajim, i can give it another round of experiments.
[user@dom0 Desktop]$ qubes-prefs updatevm
user@dom0 Desktop]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-whonix-ws-14
Qubes OS Repository for Dom0 25 MB/s | 26 kB 00:00
Package Arch Version Repository Size
qubes-template-whonix-ws-14 noarch 4.0.1-201807171801 qubes-dom0-cached 672 M
Total size: 672 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Reinstalling: qubes-template-whonix-ws-14-4.0.1-201807171801.noarch 1/2
whonix-ws-14: Importing data
Erasing : qubes-template-whonix-ws-14-4.0.1-201807171801.noarch 2/2
Verifying : qubes-template-whonix-ws-14-4.0.1-201807171801.noarch 1/2
Verifying : qubes-template-whonix-ws-14-4.0.1-201807171801.noarch 2/2
It took multiple tries running the command due to connection failure (Tor congestion). So maybe a comment should be made that re-running command might be necessary.
Using a non-torrified UpdateVM might also be needed if whonix-gw is the (broken, misconfigured…) template that is reinstalled. Instructions for both torified and non-torified are needed. Or maybe combined into a general - How to set UpdateVM?
I didn’t want to make a new thread but could you please create the Whonix ™ for macOS: Download and Installation page? I am happy to assist macOS users to the best of my ability and will start updating the macOS wiki as issues arise.