I think it will work eventually on Kali. I’ve been waiting for someone to ask about it and haven’t tried going through it yet. I’ll get the latest version and take a look.

But which option to select that best matches the operating system in the installer?

The Python3_maint-3.10 branch is what I’ll look at first. The Ubuntu 22.04 option is closest. I’ll have to change the hardcoded gnuradio version in the installer and avoid installing the 20 or so programs that already exist in Kali. Then change how they get called in the menu items. The minimal install will likely be close to working.

I loaded up a fresh Kali 23.1 with the default settings and it looks like you are going to have some trouble. There are some pretty obvious GUI issues going on. You might have better luck with selecting GNOME in the install. I'll update you when I get a fix for it.

Many of the GUI issues for the installer and the FISSURE light theme should be fixed, so now you can at least look at FISSURE in Kali. I added Kali to the installer and tried to uncheck the programs by default that already exist or failed during installation. There are still GUI elements that do not look right and I imagine there are going to be a lot of errors popping up so be cautious when installing and using things. I'll remove the beta designation in the installer and README when I think I cleaned up most of it.

I'm now trying to install on Kali (Kali Rolling 2024.3, Python 3.12.6)
After long installation with some non-blocking warning, when complete, i get
$ fissure
fissure: command not found

If the fissure command was installed from the checkbox in the installer it should be ok. You might have to open a new terminal to try again. I'll see if I can refresh that.

It was installed with installer GUI, with auto selected kali os and default check boxes

Looks like this is a new Kali version I haven't tried yet. I'll take a look. If the fissure command doesn't work you can try executing the commands that are listed when clicking the check box that cd to that ./fissure directory, add it to the PYTHONPATH, and run the ./Dashboard/__main__.py file.

I get this answer:
python ./Dashboard/main.py
Traceback (most recent call last):
File "/home/nico/Documents/FISSURE/fissure/./Dashboard/main.py", line 2, in
from fissure.Dashboard.Frontend import Dashboard
ModuleNotFoundError: No module named 'fissure'

That's what the export line does for that checkbox. For some reason that ./fissure folder isn't being recognized on its own with all the __init__.py files. It will temporarily get your open terminal to recognize it. With your user name and FISSURE location:

export PYTHONPATH=$PYTHONPATH:/home/user/FISSURE
cd /home/user/FISSURE
python3 /home/user/FISSURE/fissure/Dashboard/__main__.py

I guess the cd isn't really necessary but I tend to leave some unintentional artifacts sometimes so it's nice to know where they go. I think I intended to do python3 fissure/Dashboard/__main__.py but it works the same.