#8809 I have executed the commands, as you say:""git clone https://github.com/jianchang512/pyvideotranscd pyvideotransuv syncu

66.234**5 Posted at: 1 day ago

I have executed the commands, as you say:

""git clone https://github.com/jianchang512/pyvideotrans
cd pyvideotrans

uv sync

uv run sp.py"

But nothing happens.

My system is:

"Linux trisquel 5.15.0-67-generic #74+11.0trisquel18 SMP Sun Mar 5 03:14:11 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux"

What can I prove to make it work?

Thank you.

6 Replies

#1 DeepSeek reply at 1 day ago

The cause cannot be determined yet: sp.py produces no visible output, which usually means the process failed silently at startup (missing system libraries such as ffmpeg, libsndfile, or Qt/X11 runtime), or it exited with an error before the window appeared. The actual error text must be captured first.

  1. Ensure the required system dependencies are installed:

    sudo apt-get install ffmpeg libsndfile1-dev
  2. Run it again capturing all output instead of running it plainly:

    cd pyvideotrans
    uv sync
    uv run sp.py > /tmp/sp_start.log 2>&1; echo "exit code: $?"
  3. Open /tmp/sp_start.log and check the last part; also check the log file in the logs/ folder inside the software directory (logs/YYYYMMDD.log, e.g. logs/20260305.log).
  4. Optional, to reveal Qt plugin loading problems on Linux:

    QT_DEBUG_PLUGINS=1 uv run sp.py > /tmp/sp_qt.log 2>&1
  5. Confirm the source deployment environment itself is sane:

    uv run python -c "import PySide6; print('ok')"

Paste the last ~30 lines of /tmp/sp_start.log and of the newest file in logs/ so the exact failure (missing module, missing .so, missing Qt xcb plugin, or ffmpeg error) can be identified.

Please refer to the related documentation:

#2 66.234**5 reply at 1 day ago

both files, that of the "tmp" folder like that of the "logs" folder, are empty and the order: "uv run sp.py > /tmp/sp_start.log 2>&1; echo "exit code: $?" shows the following message: "exit code: 134"

#3 DeepSeek reply at 1 day ago

Exit code 134 = 128 + 6 = SIGABRT: the process was killed by an abort at the native (C/C++) layer, not by a Python exception, so no traceback is printed and both log files stay empty. On Linux this is almost always Qt failing to initialize (no X display available, or missing xcb/xkb runtime libraries), because PySide6 calls abort() in that case.

Check and fix in this order:

  1. Run it in the foreground with unbuffered output, so the abort message is not lost:

    cd pyvideotrans
    stdbuf -o0 -e0 uv run sp.py 2>&1 | tee /tmp/sp_start.log

    Then read /tmp/sp_start.log (it should now contain a line such as qt.qpa.plugin: could not load the Qt platform plugin "xcb" or cannot connect to display).

  2. Check whether a graphical session exists:

    echo "$DISPLAY"

    If it is empty (SSH/headless), Qt cannot open a window. Use ssh -X/ssh -Y for X forwarding, or:

    sudo apt-get install -y xvfb
    xvfb-run -a uv run sp.py
  3. Install the Qt/X11 runtime libraries Trisquel does not ship by default:

    sudo apt-get install -y libxcb-cursor0 libxcb-xinerama0 libxkbcommon-x11-0 libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0 libxcb-render-util0 libxcb-shape0 libgl1 libegl1 libfontconfig1 libdbus-1-3
  4. Isolate the failing layer:

    uv run python -c "from PySide6.QtWidgets import QApplication; QApplication([]); print('qt ok')"

    If this also aborts, the problem is Qt/system libraries; if it prints qt ok, the abort happens later, inside an imported AI library.

  5. Extra diagnostics if still unclear:

    QT_DEBUG_PLUGINS=1 uv run sp.py 2>&1 | head -60
    dmesg | tail -20
    ldd --version | head -1

If none of the above resolves it, provide: the content of /tmp/sp_start.log from step 1, the output of step 4, the DISPLAY value, whether the machine is headless/remote, and the ldd version line — the exact aborting library can then be identified.

Please refer to the related documentation:

#4 212.104**4 reply at 1 day ago

all logs are empty, 0 bytes

#5 DeepSeek reply at 1 day ago

Exit code 134 is SIGABRT from a native library, not a Python traceback, so the software's own logs/ stay empty by design: that log is only created after the main window starts. Since even stdbuf ... | tee captured nothing, the abort happens before Python writes anything to stderr, so the Python-level handler must be enabled explicitly or the crash caught at the OS level.

Run these in order and stop at the first step that behaves differently:

  1. Baseline interpreter check (rules out uv/Python itself):

    cd ~/pyvideotrans
    uv run python -X faulthandler -V
    uv run python -X faulthandler -c "print('ok')"; echo "rc=$?"

    If rc=134 already here, the abort is in the interpreter or its loader, not pyVideoTrans.

  2. Force Python to dump the aborting stack (this is the key step — it prints a traceback on SIGABRT even with no buffered output):

    uv run python -X faulthandler sp.py
    echo "rc=$?"

    Equivalent form if the above prints nothing: PYTHONFAULTHANDLER=1 uv run sp.py.

  3. If still no output, capture it at the OS level:

    ulimit -c unlimited
    uv run python -X faulthandler sp.py; echo "rc=$?"
    dmesg | tail -40
    journalctl -xe | tail -40

    Look for lines containing traps:, Aborted, segfault at, or a library path (e.g. libQt6Core, libtorch, libonnxruntime) — that names the aborting component.

  4. Get a real backtrace with gdb:

    sudo apt-get install -y gdb
    gdb -batch -ex run -ex bt --args .venv/bin/python sp.py 2>&1 | tail -40

    The top frames identify the library that calls abort().

  5. Bisect the heavy native imports (very common cause of silent SIGABRT on minimal distros: a C++ extension needing a newer glibc or an unsupported CPU instruction set):

    uv run python -X faulthandler -c "import PySide6; print('pyside6 ok')"
    uv run python -X faulthandler -c "from PySide6.QtWidgets import QApplication; QApplication([]); print('qt ok')"
    uv run python -X faulthandler -c "import torch; print('torch ok')"
    uv run python -X faulthandler -c "import onnxruntime; print('onnx ok')"
    ldd --version | head -1
  6. Check the runtime environment variables Qt aborts on:

    echo "DISPLAY=$DISPLAY WAYLAND_DISPLAY=$WAYLAND_DISPLAY XDG_RUNTIME_DIR=$XDG_RUNTIME_DIR"
    df -h .
    free -h
    ls -ld /dev/shm

    If DISPLAY is empty (headless or plain SSH without -X), Qt aborts immediately with no message in some builds.

  7. Confirm uv sync actually finished cleanly — a half-installed environment also aborts silently:

    uv sync
    uv run python -c "import PySide6, torch, onnxruntime; print('all imports ok')"

Also verify Trisquel's base glibc supports the wheels uv installed; ldd --version output from step 5 is required for that check.

If no step produces any text at all, report: the output of steps 1, 4, 5, 6, plus ldd --version | head -1 and whether the machine is headless/remote. Without at least the faulthandler traceback or the gdb backtrace, the aborting library cannot be identified.

Please refer to the related documentation:

#6 Admin reply at 1 day ago

sp.py can only be used on a desktop application.

For headless applications, please use cli.py instead.

Thinking...
Post Your Reply
If you have more than 50 messages, you will no longer receive an automatic reply. Please ask a new question!
Open source and free maintenance is not easy. If this project is helpful to you, please consider making a small donation to help the project continue to maintain and update.

Dondate via ko-fi.com

Related resource