-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
We're pleased to announce the first release candidate for Qubes 3.2.1!
This is the first and only planned point release for version 3.2.
Features:
- - Fedora 28 TemplateVM
- - Debian 9 TemplateVM
- - Whonix 14 Gateway and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
Due to limited developer time and resources, the Whonix Project [1] will
end support for Qubes 3.2 on 2018-11-15.
Whonix support for Qubes OS
- ---
Please note that there is a distinction between
I guess it should be evident but apparently not ? I've changed the
timezone manually on the taskbar to the new TZ , however I see that
when I update a Template it is still using my home TZ not my current TZ
what are the steps to correctly change to a new TZ when travelling with
Q4.0 and a
On Friday, October 5, 2018 at 3:26:51 PM UTC-4, Ivan Mitev wrote:
> Every time I had a "failed to synchronize..." erorr it was because there
> was a problem with the proxy in sys-net. Restarting it usually did the
> trick, eg:
>
> sudo systemctl restart qubes-updates-proxy.service
>
> (run the
Unfortunately, it didn't work still when qubes-gui-agent was running.
I tried recompiling everything again, and the results have changed quite a bit.
Now, instead of autohiding the HVM window in dom0, I can see a very clear
failure which points me in the direction of Xorg instead.
Sadly, this
On 10/5/18 9:48 PM, Otto Kratik wrote:
Qubes 3.2
Ever since a routine qubes-dom0-update was interrupted in the middle of the
upgrade process, I can no longer run any updates on dom0. Instead I see the
message:
"Failed to synchronize cache for repo 'qubes-dom0-cached', disabling."
..in
Qubes 3.2
Ever since a routine qubes-dom0-update was interrupted in the middle of the
upgrade process, I can no longer run any updates on dom0. Instead I see the
message:
"Failed to synchronize cache for repo 'qubes-dom0-cached', disabling."
..in response to most commands that I attempt
On Thursday, October 4, 2018 at 3:05:00 PM UTC-4, Achim Patzner wrote:
> I just tried installing Qubes 4.0 on a Lenovo P52 (out of the box, no
> firmware updates) and it didn't even boot the distribution media off
> USB (after trying several USB ports; there are at least three separate
>
On Friday, October 5, 2018 at 12:13:42 AM UTC-4, Manuel Amador (Rudd-O) wrote:
> On 2018-09-22 07:13, Daniel Allcock wrote:
> > Even better would be to "hibernate" a qube by suspending it to disk,
> > but I know the qubes team has other priorities. I'm hoping per-vm
> > session management is
