The issue seems to be linked to the python3-pam package. Unresolved dependency?
Probably different issue.
Please report as per: Reporting Guidelines
Sorry for the delay in reply Patrick. I have been digging around and within the issue for a number of hours now. There is good and bad news for both the Whonix devs and the Whonix-Qubes devs.
There are dependency issues with the Whonix support for Xen hypervisors. The good news for the Whonix people is that the sdwdate issue with Qubes is unlikely to be a whonix problem. I fixed easily that by setting my dom0 clock to the sys-firewall service, my embedded clock sources stopped being all wacky after that. The bad news is that whonix has a regression bug when updating sandboxed installations after less than a handful of months. On installation that python package I mentioned completely broke upgrade-nonroot as well as spitting out the OSCP cert rejections only yesterday. I fixed this for a time by nuking the former qube and reinstating a new template. Curiously found I could only torify Whonix with an Obs4 bridge as opposed to a direct connection this time. This is where the news maybe gets bad for everyone involved is that in my hypervisor, the private storage size toggle that can be increased or decreased has a very unique bug only specific to Whonix cubes. Regardless of where I set that number upwards it it reports in the hypervisor as only 2GB of private storage that holds the filesystem with a percentage status over 100%
It is not my prerogative to sling any mud nor fix the blame in any certain sense. Though after going right down the rabbithole over about 12hrs I have a strong inkling that this issue is a juxtaposition between a bad pre-installation Qubes qvm parameter in the whonix-workstation-17 community template and a regression bug based of dependency issues from the python3-pam package causing grief with Xen and Qubes support within the Whonix file system.
I would suggest a coming together of the devs from both camps on this one as it is my educated assumption the situation is not as plain as an issue exclusive of either.
As a courtesy I will later on post a link to this page and a copypaste of this post for the reference of the Qubes community. I posted here first because this thread and the sdwdate disclaimer elsewhere on this page was my best clue to nailing down a number of issues at my Qubes end of my ecosystem.
Will be moved to separate forum thread since sounds very different.
Separate issue.
None are known. None reported except by you. Please post output of apt.
the private storage size toggle that can be increased or decreased has a very unique bug only specific to Whonix cubes. Regardless of where I set that number upwards it it reports in the hypervisor as only 2GB of private storage that holds the filesystem with a percentage status over 100%
Separate issue. Please report to Qubes.
1 issue = 1 forum thread or 1 ticket please. Otherwise gets confusing.