Field-Tested Notes

Field-Tested Notes (Arch Linux, 2026-05-29)

This guide was walked through step-by-step on a live Arch system (ThinkPad P16g, Hyprland). Every issue below was encountered and resolved in real time.

Issue Symptom Resolution

sudo lockout after failed password attempts

"Sorry, try again" even with correct password after 3 failures

PAM’s pam_faillock locks the account. Fix: su - to root, then faillock --user <username> --reset, exit, retry sudo.

uucp group not active

Group added but groups doesn’t show it

newgrp uucp activates it in the current shell without re-login.

AUR OrcaSlicer segfaults

zsh: segmentation fault (core dumped) on launch — both orca-slicer and orca-slicer-bin

Known library conflict on Arch as of 2026-05. Flatpak install is the working path.

Flatpak first-run permission error

bwrap: Can’t find source path /run/user/1000/doc/by-app/…​ Permission denied

Flatpak requires a desktop session re-login after first install. No terminal workaround — xdg-document-portal must initialize with the session. Log out of your DE and log back in.

XDG_DATA_DIRS warning

"directories are not in the search path" on every flatpak run

Resolved automatically after session re-login. Manual export does not fix the bwrap error.

Printables STL download fails via curl

file reports XML (232 bytes) instead of STL data

Printables redirects to an XML page. Use the GitHub URL instead: raw.githubusercontent.com/CreativeTools/3DBenchy/master/Single-part/3DBenchy.stl. Verify with file <name>.stl — should say data, not XML.

pronsole command not found

zsh: command not found: pronsole

The printrun package installs as pronsole.py, not pronsole. Check with pacman -Ql printrun | grep bin.

pronsole can’t find G-code file

File not found! when using ~/ path

pronsole doesn’t expand ~. Use the full absolute path: /home/<user>/3dprints/…​

G-code commands rejected as "Unknown command"

echo:Unknown command: "m105"

G-code commands are case-sensitive. Use uppercase: M105, M104, G28 — not lowercase.

picocom stuck in tmux

Ctrl+A captured by tmux prefix instead of picocom

Kill from another pane: lsof /dev/ender3v3sekill <PID>.

Filament not extruding despite motor running

extrude 50 accepted, motor turns, spool doesn’t unwind, nothing comes out of nozzle

Filament wasn’t seated deep enough. Needed: unclogging rod through nozzle from below, cold pull (230°C→90°C→yank), then power cycle. Final fix was full power cycle after rod cleaning + manually pushing filament until steady flow confirmed with extrude 50. See detailed 6-step procedure in Troubleshooting section.

pronsole reset doesn’t stop print

Print continues after reset command

Must pause first, then reset. There is no abort or cancel command in pronsole.

Printer disconnects after power cycle

Can’t write to printer (disconnected?) errors after restarting unit

Reconnect in pronsole: connect /dev/ender3v3se 115200. Power cycling the printer drops the serial connection.

settemp not hotend

* Unknown syntax: hotend 210

The correct pronsole command is settemp 210, not hotend 210.

Bed leveling mesh lost after multiple resets

Invalid mesh / Error:Failed to enable Bed Leveling after repeated reset commands

The printer re-runs auto-level automatically and restores the mesh. Wait for Bed Leveling ON before printing. Can also re-run from LCD: Auto Level.

Print stalls when computer disconnects

Print stops mid-job when laptop dies or serial connection drops

USB/serial printing requires continuous connection. For unattended prints, use MicroSD card method instead.

OrcaSlicer "empty layers" / "conflicting G-code paths at Z=0.00"

Model has geometry below Z=0 — center=true or sphere() positioning pulls vertices below the bed

Verify from terminal: parse the STL for Z min value. If negative, the model is partially below the bed. Fix in OpenSCAD by ensuring all geometry starts at Z=0. Never use center=true on components that need to sit on the bed. Validate with: python3 -c "with open('file.stl','r') as f: zvals=[float(l.strip().split()[-1]) for l in f if 'vertex' in l]; print(f’Z min: {min(zvals):.3f}')".

OrcaSlicer "floating regions" support warning

Thin struts or overhangs detected — slicer suggests enabling supports

Either enable Auto supports in OrcaSlicer, or redesign the model so all parts build up from the bed without unsupported overhangs. Wedge shapes (Star Destroyer) are inherently bed-friendly. Complex shapes (TIE Fighter) may need supports.

If you hit the bwrap error and try mkdir -p /run/user/1000/doc — it will fail with permission denied. That directory is owned by the portal service, not the user. The only fix is the session re-login.