-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anon-Connection-Wizard does not start in sys-whonix (whonix-gw 15) #29
Comments
Yes, I'm having trouble with it also on whonix 14. I'll have to research this further. |
/etc/xdg/autostart/whonix-setup-wizard.desktop starts What happens when starting /usr/lib/whonix-setup-wizard/whonixsetup_check_for_start manually?
qubes-whonix package file /usr/lib/qubes-bind-dirs.d/40_qubes-whonix.conf defines among others the following folder to be added to bind-dirs
Clearing /rw might wipe these files also. The qubes-whonix package also ships the following files:
Wondering if that could be the cause. |
|
0brand:
> What happens when starting /usr/lib/whonix-setup-wizard/whonixsetup_check_for_start manually?
```
***@***.***:~$ sudo /usr/lib/whonix-setup-wizard/whonixsetup_check_for_start
missing_disablenetwork_line
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
INFO: No page needs showing.
```
`Anon-Connection-Wizard` starts and Tor connects.
This is at the very first start of the VM? (Or from "simulated first
start" (if you reset the private image somehow)?)
If yes, then that's strange. Anon-Connection-Wizard (ACW) does not
autostart but when you run
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start it works as
intended?
|
That was the simulated start. I confirmed by creating a fresh
Starts a terminal but
Yes, very strange. Just tried again to be sure. Same result. Anon-Connection-Wizard does not auto-start, running simulated start does the trick. |
0brand:
> This is at the very first start of the VM? (Or from "simulated first start" (if you reset the private image somehow)?)
That was the simulated start.
"simulated first start": I mean with a new private image. Just to make
sure we talk about the same thing.
Running /usr/lib/whonix-setup-wizard/whonixsetup_check_for_start
manually is also somewhat simulated but let's call that manual start or
something to avoid confusion.
I confirmed by creating a fresh `sys-whonix` VM. Then,
***@***.*** ~] qvm-run sys-whonix xfce4-terminal`
Starts a terminal but `Anon-Connection-Wizard` does not start.
> If yes, then that's strange. Anon-Connection-Wizard (ACW) does not auto-start but when you run /usr/lib/whonix-setup-wizard/whonixsetup_check_for_start it works as intended?
Yes, very strange. Just tried again to be sure. Same result. Anon-Connection-Wizard does not auto-start, running simulated start does the trick.
So the first autostarted (if it autostarts hopefully) run of and
subsequent manual start of
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start produces
different results.
Therefore we need to look "inside"
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start to see what is
happening. I've added some output to make debugging easier. In future
versions output of
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start will be
prefixed with
"/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start:" to make
searching the logs easier. Version you're having is not having this
usability feature yet and outputs only what it is actually noticing.
Luckily output of
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start (when auto
started) will be stored in file:
~/.xsession-errors
Could you please have a look at
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start as you
currently probably have?
https://github.com/Whonix/whonix-setup-wizard/blob/9a20891f82dc49fc7fb0f18e2522bc7e86421fd1/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start
Check for any line that includes
print
These are the possible outputs by
/usr/lib/whonix-setup-wizard/whonixsetup_check_for_start ending up in
~/.xsession-errors
Alternatively post the whole ~/.xsession-errors here after a start of a
new sys-whonix.
Also, does
whonixcheck --verbose
say something interesting?
Maybe some systemd unit is failing in this configuration?
sudo systemctl --failed list-units
(whonixcheck --verbose should cover this.)
If someone speaking python... Do you see something in function
tor_status that could throw a python exception in this configuration?
https://github.com/Whonix/anon-connection-wizard/blob/master/usr/lib/python3/dist-packages/anon_connection_wizard/tor_status.py
|
Yes I use a new private image for every test.
OK manual start it is ;)
Nothing there with "print"
Maybe a systemd error? (warning: error sending to systemd:)
Just
|
Sorry about that. I somehow managed to close the issue. |
When
sys-whonix
is started for the first timeAnon-Conection-Wizard
is supposed to automaicaly start, and walk users through Tor setup and configuration. However, unlike in previous Whonix versions {13,14} whenvm-boot-protect
is configured insys-whonix
(whonix-gw-15
) this does not happen.A workaround is to either start Anon-Connecton-Wizare manually or run
whonixset up
to configure Tor and populate /var/lib/tor (with Tor State). This file is persistent acrosssys-whonix
restarts.This is not due to Whonix files having been removed from /rw . I should have explained that better here: #18 (comment)
The text was updated successfully, but these errors were encountered: