Update issue of whonix-15 and debian-10 templates

47 views
Skip to first unread message

taran1s

unread,
Mar 13, 2020, 9:19:53 AM3/13/20
to qubes-users
Hi, all,

I am trying to update whonix-ws-15 and whonix-gw-15, but it fails to do
anything. All fedora-30 templates, and dom0, are updating just fine.

In my Qubes Manager I see an update arrow for both whonix templates gw
and ws.

Using Qubes Updater it starts disp-mgmt-dvm and than starts the
whonix-xx-15 just fine. In my Nyx I but don't see any traffic running.
The update seems to finish with a green tick but the green update arrow
in the Qubes Manager remains and requires an update.
In the Details tab of the Qubes Updater I get only this, I dont see any
details as before (or as when updating Fedora-30 template):

Updating whonix-gw-15

whonix-gw-15:


Once I try to update the whonix templates directly with sudo apt update,
I get "14 packages can be upgraded. Run 'apt list --upgradable' to see
them."

I get a bit similar results for my debian-10 template. After I execute
the sudo apt update in debian-10 template, it doesn't show any traffic
in the Nyx, it ends with the green tick in the Qubes Updater and it
tells me that "1 package can be upgraded. Run 'apt list --upgradable' to
see it."


The issue started after the latest dom0 update. I tried to even onionize
the templates update process but it remains the same.

How should I proceed? Is the qubes updater broken for Debian based
templates?

Should I run sudo apt update && sudo apt dist-upgrade in the related
qubes templates?

Thank you for help!

dono...@unseen.is

unread,
Mar 16, 2020, 9:33:06 AM3/16/20
to qubes-users
I have this same issue with whonix-xx-15.

qtpie

unread,
Mar 18, 2020, 1:04:24 PM3/18/20
to qubes...@googlegroups.com
dono...@unseen.is:
Same for me.

taran1s

unread,
Mar 18, 2020, 1:04:24 PM3/18/20
to qubes-users


dono...@unseen.is:
I solved this by executing sudo apt update && sudo apt dist-upgrade
directly in the respective whonix templates.

My question is if this is a normal procedure that needs to be done on
top of normal qubes updater, or it is a bug in the qubes updater or it
was just this time exception.
Reply all
Reply to author
Forward
0 new messages