[BUG?] koboldcpp.py fails to start launcher from folder created by --unpack

[alex-ie]

Describe the Issue
The behavior of python3 koboldcpp.py differs from one of standalone exec file. Standalone starts Launcher by default, but extracted one produces "errors": 'No module named darkdetect' and 'customtkinter python module required'.

Wiki:

Launching with this flag allows the internal contents of the KoboldCpp pyinstaller binary to be unpacked into a directory. This is useful for modifying or replacing files, and KoboldCpp can then be launched by running python3 koboldcpp.py

This seems minor, the launcher can still be started from its own exec file as I have found out by try-and-error, but confusing for newbies. If the fix is not easy, let us improve description in wiki a bit:

Launching with this flag allows the internal contents of the KoboldCpp pyinstaller binary to be unpacked into a directory (e.g. KoboldCpp). This is useful for modifying or replacing files, and KoboldCpp can then be launched by running python3 KoboldCpp/_internal/koboldcpp.py with flags to launch it without a GUI. To run GUI launcher, execute KoboldCpp/koboldcpp-launcher.

P.S. I have found mentioning issue with TKinter in wiki, but GUI works on my system when run from a single exec file.

Additional Information:
v1.111.2 Linux

[askmyteapot]

If you havent built from source, you will need to pip install the packages into your environment.
https://github.com/LostRuins/koboldcpp/blob/concedo/requirements.txt has all of the dependencies required.

if you download that .txt file, you can install them by using pip install -r requirements.txt

[alex-ie]

@askmyteapot ,

you will need to pip install the packages into your environment.

Why? If everything works if extracted from exec file to /tmp , why does it not work from --unpack _ed folder?

[LostRuins]

Did you click the small koboldcpp_laucher.exe? It should be in the unpacked files

[alex-ie]

@LostRuins

Did you click the small koboldcpp_laucher.exe? It should be in the unpacked files

I have written "This seems minor, the launcher can still be started from its own exec file". So IMO change to wiki might be enough. But also : Why integration with GUI gets lost after extraction? - that might be easy to fix.

P.S. Wiki is a description of how the system works, not how it might work theoretically, so if integration is not gonna be fixed soon, I suggest change in wiki.

[LostRuins]

If you're not using the exec file, then it will fall back to your own system python, which may need some packages installed. To do that, you can run

pip install -r requirements.txt from the koboldcpp folder. In particular, you need tk , tkinter customtkinter psutil and jinja2 for full functionality.

[alex-ie]

@LostRuins

If you're not using the exec file, then it will fall back to your own system python, which may need some packages installed.

If exec contains its own python environment then why not extract it too and advice users to run it?

P.S. I still do not understand why koboldcpp-launcher can be started as separate file but cannot by koboldcpp.py. Ah, there are two launchers, correct? One standalone and one generated by koboldcpp.py on the fly? If so, seems like an unexpected duplication in the main exec file.

[LostRuins]

Because when you run an exe, it's a pyinstaller that has all the modules already baked in. Yes, even the launcher.

When you run a .py file, it's running on your own system python. I cannot extract my python modules into your system python environment.