kdesudo error popup window ( sdwdate-gui )

Patrick · August 13, 2018, 8:02am

That doesn’t give me any clues. kdesudo error popup window ( sdwdate-gui ) - #2 by Patrick required.

Please create a separate forum thread for that.

tempest · August 13, 2018, 11:56am

@Patrick. here is the output of kdesudo.log after error on boot:

user -u sdwdate-gui /usr/lib/sdwdate-gui/sdwdate-gui

RED29 · August 13, 2018, 2:46pm

Ok thanks I will.
I hope we can fix this popup. Its annoying and maybe a security breach.

Patrick · August 13, 2018, 3:08pm

Frequently Asked Questions - Whonix FAQ

Patrick · August 14, 2018, 5:02pm

That moves us a lot closer! Thanks!

Does your file /etc/sudoers.d/sdwdate-gui look like sdwdate-gui/etc/sudoers.d/sdwdate-gui at master · Kicksecure/sdwdate-gui · GitHub?

sudo cat /etc/sudoers.d/sdwdate-gui

What happens if you manually run…?

sdwdate-gui

What happens if you manually run…?

/usr/lib/sdwdate-gui/start-maybe

What happens if you manually run…?

kdesudo -u sdwdate-gui /usr/lib/sdwdate-gui/sdwdate-gui

xXXXx · August 14, 2018, 6:33pm

“System Settings” > “Startup and Shutdown” > “Desktop Session” > “Start with empty Session”

Will solve the issue

Kas · August 14, 2018, 7:53pm

works for me

Patrick · August 14, 2018, 7:56pm

Did sdwdate-gui autostart for you before doing “System Settings” > “Startup and Shutdown” > “Desktop Session” > “Start with empty Session”? I guess not.

And after “System Settings” > “Startup and Shutdown” > “Desktop Session” > “Start with empty Session” sdwdate-gui autostarts for you?

I can’t reproduce this.

We should still find out what “System Settings” > “Startup and Shutdown” > “Desktop Session” > “Start with empty Session” has to do with it anyway.

^ in worst case this does nothing. In best case it prevents the popup but sdwdate-gui still doesn’t autostart. Might also help us to debug this issue.

RED29 · August 16, 2018, 6:49am

Thanks for the solving this. But it still bother me what the cause is? What are the consequences?

Patrick · August 16, 2018, 10:20am

Unknown.

sdwdate-gui does not automatically start. Usability issue. More so once we implement ⚓ T551 enter Whonix firewall timesync-fail-closed mode before suspend / enter Whonix firewall full mode after resume and clock-fix.

tempest · August 16, 2018, 11:54am

yes.

an additional gui icon appears in the lower right corner. no error.

same as above. no error window.

also the same as above. no error.

Patrick · August 16, 2018, 1:36pm

Could you try this version please?

github.com

Kicksecure/sdwdate-gui/blob/master/usr/bin/sdwdate-gui

#!/bin/bash

## Copyright (C) 2018 - 2022 ENCRYPTED SUPPORT LP <adrelanos@whonix.org>
## See the file COPYING for copying conditions.

## AUDIT: Is there a safer way?
## Required since Debian buster.
xhost +

sudo \
   --set-home \
   --non-interactive \
   -u sdwdate-gui \
   /usr/libexec/sdwdate-gui/sdwdate-gui

tempest · August 18, 2018, 3:01pm

@Patrick, the error still occurs with the above version.

troubadour · August 18, 2018, 10:16pm

Not directly related, but…
Testing sdwdate-gui[qubes] in VirtualBox.

The kdesudo popup does not seem to be caused by sdwdate-gui.

@tempest
Could you try the following:
In /usr/lib/sdwdate-gui/start-maybe comment out the line containing only sdwdate-gui
Reboot Whonix-Gateway.

sdwdate-gui is not started but the popup is still showing.

@Patrick
I have installed the kdesudo wrapper. With the above setup, nothing is written in kdesudo.log. When we let sdwdate-gui start at boot, we have the expected user -u sdwdate-gui /usr/lib/...

The installation of the new sdwdate-gui basically crash everything. After rebooting, at least whonix-firewall and Tor do not start, dolphin stops working… but the popup is not showing. That is the point. Something weird must be happening before… what?

Patrick · August 19, 2018, 12:39pm

Networking not coming up?
sudo ifconfig
?

Could be this one:

But works again after reboot?

tempest · August 19, 2018, 2:33pm

i tried it. error still occurs and sdwdate still appears to be running per “sudo systemctl status sdwdate.service.”

Patrick · August 19, 2018, 2:51pm

sdwdate is unaffected by all of this.

This is sdwdate-gui:

tempest · August 19, 2018, 3:02pm

right. my mistake. sdwdate-gui is not running. the error does still occur. kdesudo.log is empty.

tempest · August 19, 2018, 5:33pm

@patrick. others have run into the same problem. similar fix as mentioned above by @xXXXx. i guess kde is trying to “restore the previous desktop session.” setting it to a new session fixes the problem.

https://www.linux.com/forums/ubuntu/kubuntu-1110-kde-sudo-error-every-start-here-fix-it

this fixed it for me as well. sdwdate-gui is running as well. so, in summary, here is the fix:

go to “system settings → startup and shutdown → desktop session.”
in the “on login” section, change it from “restore previous session” to “start with an empty session.”

a bit more on session management:
https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/kcmsmserver/

i’d think that starting from an empty session, rather than saved application states at shutdown, is preferable for whonix anyways. or is there something i’m not considering? in whonix 13, the default option selected on install is “start with an empty session.”

RED29 · August 19, 2018, 9:38pm

This explain why my first whonix session (fresh from image) never gives me the popup screen. Its always on the follow bootup, its something to do with restoring previously sessions.