Repository navigation
GUI guide
python3 gui/sp_gui.py --store /var/lib/tuxchangeOr launch Tuxchange from your desktop menu, if you ran the installer. Without --store it looks
in ~/.local/share/tuxchange/store, which is not where the service keeps its store.
The GUI is a client of the daemon. It uses the same unix control socket as sp_relay.py ctl and
knows nothing about CEC, 802.11 or the store layout, so anything the socket cannot provide is
missing from the window. If the daemon is unreachable, the GUI says so and offers Start instead of
showing old values.
Start, stop and restart tuxchange.service, and see whether it is running.
This works without a password because the installer wrote a polkit rule letting your desktop user start, stop and restart this one unit. If you skipped that step, you need a polkit agent running or these buttons will fail with interactive authentication required.
On the Home tab, choose which wireless interface the service uses. The service has to be running
for this, because the daemon saves the choice. It takes effect at the next restart. If the service
will not start, set SP_IFACE in /etc/default/tuxchange.
The switch on the Home tab stops the daemon engaging consoles without stopping the process.
The Home tab shows the address the daemon transmits from and how it is chosen. The address is derived from the store path, so it is stable.
Change the MAC sets how often a new address is presented. The daemon applies it straight away and saves it for restarts. See The MAC filter for when you want it.
The messages the daemon serves to consoles. Each title shows its messages, and each message shows its origin, size, creation time, send mode and whether its HMAC verifies. A message marked not served is held but never sent. A message that arrived over the air is never forwarded.
Author Mii identity writes the Mii, author name and greeting the daemon presents. Import CEC data loads a console dump. You can remove a single message or a whole title.
Messages received from consoles, shown the same way. You can delete them from here. Each title keeps up to 24 messages or 1 MiB, and the oldest are dropped first when it fills up.
Which consoles were met and when, and what was sent and received.
Consoles you have blocked, with a note saying why, and consoles inside a cooldown. Cooldowns expire on their own, and you can clear or change them here.
The daemon's recent log. Under the service this is the same text as journalctl -u tuxchange. The
verdict block appears here at the end of each pass, and that block is what to quote in a bug
report.
Every socket call and every systemctl runs off the main loop and comes back through an idle
callback. A single transfer can hold the daemon's attention for seconds, and those calls would
otherwise lock up the window during an exchange.