Sdwdate-gui broken after last update

Qubes-Whonix
1

Hello,

Yesterday I did updates for my whonix/kicksecure templates on QubesOS 4.3 and after a restart I noticed that sdwdate-gui doesn’t work as it was before.

The sys-whonix sdwdate-gui widget list nothing other than '“Exit”, it doesn’t show my other whonix/kicksecure App qubes like it used to before and the icon shows the “spinning” one, like it’s doing something.

I checked the logs, but it appears that sdwdate works as normal. I can’t find any proper log for sdwdate-gui, only these lines but I don’t know if it’s related:

systemd[1730]: Starting sdwdate-gui.service - Secure Distributed Web Date Graphical User Interface...
systemd[1730]: sdwdate-gui.service: Found left-over process 1995 (has_netvm_on_qu) in control group while starting unit. Ignoring.
systemd[1730]: sdwdate-gui.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[1730]: Finished sdwdate-gui.service - Secure Distributed Web Date Graphical User Interface.
systemd[1]: sdwdate-gui-qubes@0.socket - sdwdate graphical user interface - Qubes socket proxy was skipped because of an unmet condition check (ConditionPathExists=/run/sdwdate-gui-qubes-should-proxy).

Any idea of what’s going on?

3 Likes
2

Yeah. I have the same problem

1 Like
3

My fault, I appear to have botched the systemd unit for sdwdate-gui, and then didn’t notice since I had sdwdate-gui disabled on my end (due to other testing I had done previously). I submitted a fix:

5 Likes
4

can confirm, I experience this issue as well.

1 Like
5

New update fixed the issue, thanks @arraybolt3 !

1 Like
6

This fix is now available in all repositories.

1 Like