Did you activate your virtual python env with ‘source .venv/bin/activate’? You must do that in each new shell unless you add some config to your shell profile config to have it detect the presence of a python venv.
Did you activate your virtual python env with ‘source .venv/bin/activate’? You must do that in each new shell unless you add some config to your shell profile config to have it detect the presence of a python venv.
Tried Ubuntu, Drauger OS, Fedora, and Popos. It’s specifically the laptop hardware that’s giving trouble and as far as the drivers go it’s just really a mess because of X11 vs Wayland issues with Nvidia making it all the more difficult.
Heres my current core issue: I need to run nvidia official drivers as the ones provided via open repos don’t support eGPUs/multi-gpu setups. The problem there is nvidia official drivers only support x11, so then I’m forced to used a sunsetting windowing system for my daily driver, which I just can’t bring myself to do.
Okay back that up: I just tried my third time in 5 years to run Linux as a daily driver for software dev work and gaming. I’m on an ASUS ROG Zephyrus M16 2022 and I’ve never been able to fully get Linux working. Here’s my takeaways (and I really wanted Linux to work out fwiw):
But sure proton is great! /s it’s only viable if the damn hardware works in the first place which Linux simply can’t do yet
Okay perfect, just wanted to check.
Next I’d say check your venv to verify the pandoc binary is indeed there:
find $VIRTUAL_ENV -name pandoc
If it’s not there, you should be able to install it by entering a python shell from your venv and do:
import pypandoc pypandoc.download_pandoc()
Hopefully that’s able to resolve it for ya. Venv should be at the front of your path so it should prefer bins from there.