Not fully functional. There is a few seconds lapse to open the gui message after clicking the icon, showing the dbus connection error every time.
Guess kdesudo clears that environment. Is that really needed? What is the reason for starting it as a different user?
Originally, I was wary of giving permission to the `rm' command without password (in /etc/sudoers.d/sdwdate-gui). Now, it's there in Qubes. @patrick Otherwise, any other reason?
In any case, you can allow in sudo a single rm including its parameter - which will work also on non-Qubes then.
I am not sure anymore why we started sdwdate-gui as user sdwdate. Was probably convenient because of file permissions. Can surely be implemented some other way. Now what's missing is something like sudo's parameter -E (preserve environment). Doesn't seem to exist for kdesudo. Perhaps for some other tool.
It sdwdate-gui would be running as user, sudo -E will not be necessary. Anyway since that sudo call is password-less, standard sudo can be used instead of kdesudo, can't be?
swdate-gui was run as user in the early design. See https://github.com/troubadoour/sdwdate-gui/blob/3cf36079a13f631308f3e7f01ef97f1c2e33191e/etc/xdg/autostart/sdwdate-gui.desktop
I did complicate things afterwards
It should be OK running sdwdate-gui, restricting rm to the file to be removed.
Tested in Qubes and VirtualBox.
Great. Works for me in a Qubes Debian VM. So we can consider this case closed.
Switched to master branch, merge origin/master (was up to date), merged origin/python. Hope this is OK.
Happening during Tor bootstrap (SUMMARY between double quotes).
I cherry picked.
git cherry-pick fffc44e6559a411f6c027160d149ac8b54708ff6
git cherry-pick 18d23bb8eb6e03bc21403065cb6b582e4258d932
Somehow these were not included in Whonix sdwdate master. My mistake.
Our branches match now. Looks good.
Good catch. Merged.