Whonix 18 CLI — setup-dist fails due to missing anon_connection_wizard

Support
1

Hi Whonix team,

today I downloaded the latest Whonix 18 Gateway CLI build for KVM and noticed an issue during the first-run wizard.

The system itself works fine (Tor service starts and anon-verify -v reports no problems), however the setup-dist wizard fails with the following error:

ModuleNotFoundError: No module named 'anon_connection_wizard'

It looks like the CLI build does not ship the anon-connection-wizard component (which normally belongs to the GUI edition), but setup-dist still tries to import and use it. Because of this, setup-dist cannot complete successfully, even though Tor is running correctly in the background.

Environment details:

  • Product: Whonix-Gateway 18 (CLI)

  • Platform: KVM / libvirt

  • Image: Whonix-Gateway-CLI-18.0.8.7.Intel_AMD64.qcow2

  • Network: default KVM NAT + Whonix internal network (unchanged)

  • Tor status: active (tor@default) and verified (anon-verify -v exit code 0)

Steps to reproduce:

  1. Import Whonix 18 Gateway CLI KVM image.

  2. Boot the VM and proceed through setup-dist.

  3. Choose “I’m ready to enable Tor”.

  4. Wizard fails with the above Python error.

This is confusing for new users because it looks like Tor is broken, while in reality only the wizard fails.

screen
screen1263×777 7.26 KB

1 Like
2

Thanks for the report!

Since connect to public Tor network by default / avoid Anon Connection Wizard (ACW) popup at first boot was implemented, the setup-dist terminal user interface (TUI) feature to enable/disable Tor is no longer important enough to justify its maintenance. [1]

anon-connection-wizard (ACW) is planned to be merged with tor-control-panel (TCP). Both are GUI applications. tor-control-panel is also supposed to be standalone, not depending on helper-scripts. Discussion here: Tor controller GUI (tor-control-panel) - #101 by Patrick

ACW and TCP are GUI applications. These are not great to have on CLI builds. Hence, setup-dist should not Depends: on ACW / TCP.

Hence, this feature will be removed in version 18.0.9.4 (and above) and therefore cause no further issues.

[1] related: Maintainability

2 Likes
3

You’re welcome, and thank you for your prompt response.

1 Like