Troubleshooting

Common build errors and runtime issues.

Build errors

`fatal error: Python.h: No such file or directory`

Python development headers are missing. Install for your distro:

# Arch
sudo pacman -S python
 
# Ubuntu / Kali
sudo apt install python3.10-dev
 
# Debian
sudo apt install python3-dev python3.10-dev libpython3.10-dev

bash

Qt version mismatch (SIGABRT on client launch)

All Qt5 packages must be at the same version. This usually affects qt5-websockets on Arch when it lags behind qt5-base. Fix by building from source:

git clone https://invent.kde.org/qt/qt/qtwebsockets
cd qtwebsockets
git checkout kde/5.15
qmake && make -j$(nproc) && sudo make install

bash

Then launch with:

QT_PLUGIN_PATH=/usr/lib/qt/plugins ./mugen client

bash

Runtime issues

Font or formatting problems in the console

Some distros (Kali, older Ubuntu) fail to load the embedded Monaco font from Qt resources. Use any monospace font as a fallback - the console will still function correctly.

Payload compiler not found

The teamserver checks the Build compiler paths at startup and exits if they are missing.

The default profile (profiles/mugen.yaotl) uses the musl.cc toolchains under data/:

Teamserver {
    Build {
        Compiler64 = "data/x86_64-w64-mingw32-cross/bin/x86_64-w64-mingw32-gcc"
        Compiler86 = "data/i686-w64-mingw32-cross/bin/i686-w64-mingw32-gcc"
        Nasm       = "/usr/bin/nasm"
    }
}

hcl

Those directories are created by make / make ts-build (teamserver/Install.sh). make rebuild does not restore them.

If you deleted data/ and see Compiler x64 path doesn't exist, restore the compilers:

make ts-build
# or from the repo root:
./teamserver/Install.sh

bash

If your profile points at system MinGW instead (/usr/bin/x86_64-w64-mingw32-gcc):

# Arch
sudo pacman -S mingw-w64-gcc nasm
 
# Ubuntu / Debian / Kali
sudo apt install mingw-w64 nasm

bash

Behavior questions

Why does Demon sleep obfuscation stop working while jobs are running?

Jobs run in their own threads. Demon sleep obfuscation requires all threads to be suspended to safely encrypt the heap and stack. Mugen waits for all active jobs to finish before applying obfuscation. Once jobs complete, normal obfuscated sleep resumes.

This does not affect Tengu - Tengu sleep obfuscation operates on code pages only and is not blocked by running jobs.