Liste des fichiers installés sur un serveur

[F4NRM]

Could you please provide a complete list of all files installed by an sdroxyde installation?

Context: Complete uninstallation of sdroxyde, without reinstalling your server system.

▶ COMPLETE UNINSTALLATION OF SDROXIDE
⚠ Everything related to SDRoxide will be PERMANENTLY REMOVED, WITHOUT A COPY, as if it had never been installed on this machine:
✗ sdroxyde-soapysdr package (binary, voice, icons, udev rules)
✗ 1 dependency(ies) that have become unnecessary, installed solely for this purpose:
libsoapysdr0.8
✗ the systemd service and its override
✗ /root/.config/sdroxyde-brown (292 KB)
✗ /root/sdroxyde-versions (sdrversion library: kept versions, backups, history — 153 MB)
ℹ Dependencies kept because they are used by other packages or installed manually: libasound2t64 libc6 libstdc++6 ℹ Retained: everything else in the system, your sdrbackup archives, Caddy (its reverse proxy to port 4950 remains in the Caddyfile), the sdrversion script.

ℹ Nothing old will be reused: no configuration, no override, no golden.

ℹ Currently installed version: sdroxyde SDR Oxide Brown 2.0.1_brown (nothing will be kept: you will have to download it again).
Uninstall everything and delete permanently, without making a copy? [o/N] o

---

▶ SUPPRESSION
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Les paquets suivants seront ENLEVÉS :
libsoapysdr0.8* sdroxide-soapysdr*
0 mis à jour, 0 nouvellement installés, 2 à enlever et 0 non mis à jour.
Après cette opération, 266 MB d'espace disque seront libérés.
(Lecture de la base de données... 246966 fichiers et répertoires déjà installés.)
Suppression de sdroxide-soapysdr (2.0.1-1) ...
Suppression de libsoapysdr0.8:amd64 (0.8.1-5+b2) ...
Traitement des actions différées (« triggers ») pour hicolor-icon-theme (0.18-2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.41-12+deb13u4) ...
Traitement des actions différées (« triggers ») pour mailcap (3.74) ...
Traitement des actions différées (« triggers ») pour desktop-file-utils (0.28-1) ...
✓ Paquet et dépendances inutiles désinstallés : libsoapysdr0.8 sdroxide-soapysdr
✓ Service systemd et override supprimés.
✓ 1 élément(s) supprimé(s) définitivement.
✓ Bibliothèque de sdrversion supprimée.

▶ VÉRIFICATION
✓ Vérification : plus aucune trace de SDRoxide sur cette machine (paquet, service, configuration, données, bibliothèque).

---

▶ INSTALLATION NEUVE
ℹ = tout désinstaller (comme « désinstaller »), puis installer ce .deb normalement.

▶ TÉLÉCHARGEMENT
ℹ https://github.com/madmedicnl/sdroxide-brown/releases/download/v2.0.1_brown/sdroxide-v2.0.1_brown-linux-x86_64-soapysdr.deb
##################################################################################################################################################### 100.0%
✓ Téléchargé : 153M SHA-256 b6aa901eccebf3a0…

▶ CONTRÔLES AVANT TOUTE SUPPRESSION (rien n'est modifié à ce stade)
✓ Paquet sdroxide-soapysdr, version 2.0.1-1, architecture amd64
✓ Dépôts apt joignables, toutes les dépendances sont disponibles.
ℹ Il n'y a rien d'ancien à supprimer : c'est déjà une machine vierge.

ℹ PUIS installation normale de 2.0.1-1 (sdroxide-v2.0.1_brown-linux-x86_64-soapysdr.deb) par apt : dépendances réinstallées, service standard créé,
ℹ identifiant et mot de passe d'accès demandés. Rien n'est restauré, aucun override, aucun golden.
Lancer l'installation neuve ? [o/N] o

▶ SUPPRESSION COMPLÈTE

▶ VÉRIFICATION
✓ Vérification : plus aucune trace de SDRoxide sur cette machine (paquet, service, configuration, données, bibliothèque).

▶ INSTALLATION NORMALE
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Note : sélection de « sdroxide-soapysdr » au lieu de « /tmp/sdrversion.Ru5v5O/pkg.deb »
Les paquets supplémentaires suivants seront installés :
libsoapysdr0.8
Paquets recommandés :
soapysdr0.8-module-all | soapysdr0.8-module soapysdr-module-all
Les NOUVEAUX paquets suivants seront installés :
libsoapysdr0.8 sdroxide-soapysdr
0 mis à jour, 2 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 0 o/160 Mo dans les archives.
Après cette opération, 266 Mo d'espace disque supplémentaires seront utilisés.
Réception de : 1 /tmp/sdrversion.Ru5v5O/pkg.deb sdroxide-soapysdr amd64 2.0.1-1 [159 MB]
Sélection du paquet libsoapysdr0.8:amd64 précédemment désélectionné.
(Lecture de la base de données... 246925 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../libsoapysdr0.8_0.8.1-5+b2_amd64.deb ...
Dépaquetage de libsoapysdr0.8:amd64 (0.8.1-5+b2) ...
Sélection du paquet sdroxide-soapysdr précédemment désélectionné.
Préparation du dépaquetage de /tmp/sdrversion.Ru5v5O/pkg.deb ...
Dépaquetage de sdroxide-soapysdr (2.0.1-1) ...
Paramétrage de libsoapysdr0.8:amd64 (0.8.1-5+b2) ...
Paramétrage de sdroxide-soapysdr (2.0.1-1) ...
Traitement des actions différées (« triggers ») pour desktop-file-utils (0.28-1) ...
Traitement des actions différées (« triggers ») pour hicolor-icon-theme (0.18-2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.41-12+deb13u4) ...
Traitement des actions différées (« triggers ») pour mailcap (3.74) ...
✓ Paquet installé avec ses seules dépendances déclarées (apt), puis remis en apt-mark hold.

▶ SERVICE SYSTEMD
✓ Service créé : /etc/systemd/system/sdroxide.service (serveur sur le port 4950).
✓ Démarrage automatique activé.

---

▶ VÉRIFICATION DU DÉMARRAGE
✓ Service actif, port 4950 en écoute — sdroxide SDR Oxide Brown 2.0.1_brown
ℹ Démarrage : serveur en écoute
ℹ Journal : 1 avertissement(s), 0 erreur(s) depuis le démarrage (détail : journalctl -u sdroxide)

▶ TERMINÉ
✓ SDRoxide : sdroxide SDR Oxide Brown 2.0.1_brown (empreinte 6e59f579e805), installation neuve complète.
ℹ Dans le navigateur : Ctrl+F5 (ou fenêtre privée) — le client web est embarqué dans le binaire.
ℹ Configuration de cette version : /root/.config/sdroxide-brown

---

FTx still isn't decoding anything.

Have I forgotten something?

Thx

73

[madmedicnl]

73 Kevin — thank you, and yes: here is the complete list, taken out of the packaging itself rather than guessed. It is now in the manual as well, so nobody has to ask again.

Everything an installation puts on the machine

The .deb package (sdroxide, or sdroxide-soapysdr) owns exactly this, and apt purge removes every line of it:

Path	What
/usr/bin/sdroxide	the one binary — the client and the server are the same program
/usr/share/applications/sdroxide.desktop	the desktop menu entry
/usr/lib/udev/rules.d/60-sdroxide-{rtlsdr,rx888,airspyhf,hackrf,airspy,hydrasdr,elad,limerfe,relay}.rules	9 rules, so a dongle is usable without root
/usr/share/icons/hicolor/{16x16,24x24,32x32,48x48,64x64,128x128,256x256,512x512}/apps/sdroxide-brown.png and .../scalable/apps/sdroxide-brown.svg	the icon, in nine sizes
/usr/share/sdroxide/voices/	the speech voice (.onnx, its .json, the model card) for spoken announcements
/usr/share/doc/sdroxide/	README.md, copyright, and the four licence notices — voice, CMUdict, RX-888 firmware, DeepCW

That is the whole list. In particular, and this is the useful part for you:

• The package installs no systemd service. Nothing of ours can be left running or enabled after a purge, because a purge has nothing to remove. The /etc/systemd/system/sdroxide.service in your log was created by your sdrversion script, not by the package — so systemctl disable --now sdroxide and removing that file is yours to do, and we do not ship it.
• Nothing in /etc and nothing in /var.
• No configuration is created by the installer. The program makes its own directory on first run, and that is the other half of your cleanup: ~/.config/sdroxide-brown (XDG; SDROXIDE_CONFIG_DIR overrides it). Your 292 KB. Inside it are config.toml, radios.json, radio.json, one radio-N/ per radio you added, session.json, modeprofiles.json, bandplan.json, bandstacks.json, scanner.json, tciserver.json, rigctld.json, wsjtx.json, clientsettings.json, remote_login.json, input.json, memories.json, qso_log.json, swl_log.json, profiles.json, the recordings/ folder and the solar cache — plus any .quarantined file, which is a file we could not read and set aside rather than throw away.

So for a machine with no trace left at all:

sudo apt purge sdroxide-soapysdr          # or sdroxide
rm -rf ~/.config/sdroxide-brown          # every setting, logbook and recording it wrote

The portable tarball installs nothing outside the folder you unpacked it into, except if you ran ./install-desktop-entry.sh: that adds ~/.local/share/applications/sdroxide.desktop and ~/.local/share/icons/hicolor/scalable/apps/sdroxide-brown.svg, and ./install-desktop-entry.sh --uninstall removes both. The Arch package installs the same paths as the .deb (the list above, minus the Debian copyright file).

What is not ours to remove: your Caddy entry and the reverse proxy on port 4950, your sdrversion script and its /root/sdroxide-versions library, your backups, and any other program using libsoapysdr0.8. The RX-888 firmware is inside the binary rather than in a file of its own, so there is nothing to delete for it either.

On "FTx still isn't decoding anything"

I think you have forgotten one thing, and it is the reason: a fresh install has no radio in it. No radios.json, no radio.json, no radio-N/ — all of that lived in the configuration you just deleted on purpose. There is no receiver configured, so there is nothing listening and nothing can decode. That is not a fault and it is not the decoder.

To get FT8 back on the new machine:

1. Add the radio: Settings → General → Radio, driver SoapySDR, then pick the interface (your Pluto / HackRF / RTL-SDR) and a sample rate — 2.0 or 2.4 Msps for the Pluto and the RTL, 8 or 10 Msps for the HackRF — and a sensible gain. If the dongle is on another machine, it has to be reachable as a network source instead; sdroxide cannot open a USB device it is not plugged into.
2. Look at the meters before anything else. A live spectrum and moving power level means the radio is open and the dial is worth tuning. A flat waterfall means no samples are arriving, and the mode is irrelevant.
3. Then choose FT8 and a dial on the mode's frequency for that band — the band/mode menu will take you there.

One question that would settle it in a look: does the waterfall show a live spectrum? If it is flat, it is the radio; if it is alive and there are still no decodes, it is the mode or the dial and I want to see it.

Also worth knowing: you installed 2.0.1, and 2.0.2 is out now — the one with the sign-in cookie, so three radios are one sign-in rather than three.

Thank you again for the report on the other thread; the credit is in the README now.

73

[F4NRM]

Thank you, that's kind of you. I just needed to know what goes where. Let's get to work!

It's perfect, the manual is up to date. 73

[F4NRM]

While I'm on the subject, I should add that we absolutely must check the browsers (windows and other platform ) and installed apps. I just found some traces, for example, that could be causing conflicts.

[madmedicnl]

Kevin — agreed, and that is worth doing properly. Two things that would help you most, neither of which needs any software from us.

Ask Chrome what it is showing you. The most common cause of a prompt nobody recognises is not ours at all: Chrome's own password manager. When you land on a sign-in page it will offer Save password?, and that is a Chrome dialog with Chrome's wording — not our card. If you tell it Never for this site it stops asking, which also removes one more thing from the pile while you are testing.

The other candidate is an extension touching cookies or storage. Anything that manages passwords, privacy or "site data" can rewrite or block the cookie and the stored screen. Worth testing with extensions disabled for one session: if a prompt that used to appear stops appearing, that extension is the cause and we never need to look at it again.

Why this is easier to sort from tonight's build: the sign-in is now one REMEMBER ME box instead of three choices, so there is a single thing appearing rather than a card plus a browser popup competing for attention. If something still asks more than once, it is easier to say which one it is.

Two things I would find most useful if you get a moment:

• a screenshot of any remaining prompt, with the browser's own UI visible if it has any — that distinguishes our card from Chrome's in one glance;
• and whether it still appears in a normal window now, or only in a private one. If only in a private window, that is expected: a private window keeps nothing between sessions, so it will always ask.

We keep the screen on the station rather than in the browser, so anything that clears browser storage costs you much less here than it used to — a fresh sign-in brings the layout back.

[F4NRM]

Remember; browsers are not reliable. Cookie management and settings can be modified by the user beforehand. Too many assumptions.

The only reliable solution: server-side storage.

You've already acknowledged that this is the only reliable and persistent solution.