Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upwhonix clock issues after recent updates #3930
Comments
andrewdavidwong
added
bug
C: Whonix
labels
May 26, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
May 26, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
esote
May 26, 2018
I am getting this exact same error. The error also prevents the rest of the WhonixCheck, however I have (so far) not experienced it losing network after about 10 minutes.
esote
commented
May 26, 2018
•
|
I am getting this exact same error. The error also prevents the rest of the WhonixCheck, however I have (so far) not experienced it losing network after about 10 minutes. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Duplicate of #3469 |
marmarek
marked this as
a duplicate of
#3469
May 26, 2018
marmarek
closed this
May 26, 2018
andrewdavidwong
added
the
duplicate
label
May 26, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesissues
May 26, 2018
@marmarek @andrewdavidwong Is this a duplicate? On my system this issue began only on a very recent update. The other issue was reported in January.
qubesissues
commented
May 26, 2018
|
@marmarek @andrewdavidwong Is this a duplicate? On my system this issue began only on a very recent update. The other issue was reported in January. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 27, 2018
Member
@adrelanos, can you confirm whether this is a duplicate of #3469?
|
@adrelanos, can you confirm whether this is a duplicate of #3469? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marcialvieira
Jun 1, 2018
This is happening to me too, this is what was updated in my whonix-gw when it occurred.
Start-Date: 2018-05-29 05:34:19
Commandline: /usr/bin/apt-get.anondist-orig -V dist-upgrade
Install: dconf-cli:amd64 (0.22.0-1, automatic)
Upgrade: procps:amd64 (3.3.9-9, 3.3.9-9+deb8u1), libxen-4.8:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libxen-lowlevel1.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), libxenstore3.0:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), libprocps3:amd64 (3.3.9-9, 3.3.9-9+deb8u1), xenstore-utils:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), xdg-utils:amd64 (1.1.0~rc1+git20111210-7.4, 1.1.0~rc1+git20111210-7.4+deb8u1), qubes-core-agent-networking:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), xen-utils-common:amd64 (4.8.3-4+deb8u1, 4.8.3-7+deb8u1), qubes-core-agent-dom0-updates:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-passwordless-root:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1), qubes-core-agent-qrexec:amd64 (4.0.24-1+deb8u1, 4.0.28-1+deb8u1)
End-Date: 2018-05-29 05:34:59
marcialvieira
commented
Jun 1, 2018
•
|
This is happening to me too, this is what was updated in my whonix-gw when it occurred.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jun 21, 2018
Member
Doesn't happen in Whonix 14.
https://www.whonix.org/wiki/Upgrading_Whonix_13_to_Whonix_14
|
Doesn't happen in Whonix 14. https://www.whonix.org/wiki/Upgrading_Whonix_13_to_Whonix_14 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marcialvieira
commented
Jun 23, 2018
|
Thank you @adrelanos, using Whonix 14 I get no alerts. |
qubesissues commentedMay 26, 2018
Qubes OS version:
4.0 Release Candidate updated (all Qubes and dom0) on 24 May 2018
Affected component(s):
sys-whonix and other NetVMs based on whonix-gw
Steps to reproduce the behavior:
Expected behavior:
The netVM (ex - sys-whonix) will start up without error and provide TOR networking.
Actual behavior:
Two things happen:
First you will get a popup from the netVM (ex sys-whonix) that has this error:
Second you will lose networking through this netVM (ex sys-whonix) after about 10 minutes.
General notes:
My dom0 time is set to UTC. It has been set to UTC always and I only have this error after upgrading on 24 May 2018.
Related issues: