You have a specific problem. Here's how to diagnose and resolve it.
An application crashes on Haiku and a debug report window appears. Rather than dismissing it, here's how to actually read what it's telling you and use it to fix — or usefully report — the crash.
Your character walks by itself with the stick untouched, or a full push barely registers. This is distinct from a controller not being detected at all — it's a calibration problem, and it's fixable in software.
Pages look broken, layouts collapse, or certain sites refuse to render properly in Haiku's native WebPositive browser. Here's how to isolate whether it's a page compatibility issue or a local configuration problem.
A frame-perfect run suddenly hitches every time a new visual effect appears on screen. It's not a savestate or performance problem — it's your GPU driver compiling a shader for the first time, mid-frame.
A container gets killed repeatedly with reason OOMKilled, even though the application 'shouldn't' need that much memory. Here's how to find its actual peak usage and set limits that reflect reality instead of guesses.
FreeDOS boots with the wrong date or time every session, or DATE/TIME commands don't stick. Here's how to distinguish a dying CMOS battery from a software configuration issue.
A service refuses to start at all, and systemctl reports start-limit-hit — this is systemd's own crash-loop protection, and it requires clearing the rate limit as a distinct step after fixing the real cause.
Force Quit doesn't work, the app's icon keeps bouncing, or it's stuck at 'Not Responding' indefinitely. Here's the actual escalation path from gentlest to most forceful.
The progress bar hasn't moved in hours and Windows Update reports it's still downloading. Distinct from an update stuck installing — here's how to reset the download-side components specifically.
kubectl get nodes shows a node stuck in NotReady state, and pods are being evicted from it. Here's how to check kubelet, container runtime, and network plugin health in the right order.