You have a specific problem. Here's how to diagnose and resolve it.
Haiku's desktop/file-manager shell has stopped responding or crashed. Because Tracker is just another BLooper-based application, restarting it doesn't require rebooting the whole system.
Characters look too wide, too thin, or the image doesn't fill the screen correctly. This almost always traces to a pixel-aspect-ratio setting, not the emulator core rendering incorrectly.
A save state that worked before an update now fails to load, or loads into a corrupted state. This is expected behavior given how save states actually work — here's what to do about it.
The core loads but the game never appears — just a black screen, or an immediate crash back to the menu. Here's how to isolate whether it's the ROM, the core, or your video configuration.
A helm upgrade fails partway, or a release gets stuck in 'pending-upgrade' state, blocking every subsequent operation on it. Here's how to actually recover instead of getting stuck retrying the same failing command.
A pod can't start because Kubernetes can't pull its container image — the fix depends entirely on which of a handful of specific causes is actually responsible, from a typo to a private registry auth problem.
A pod stuck Pending means the scheduler couldn't place it anywhere — here's how to read the actual reason from pod events instead of guessing at resource, taint, or affinity problems.
A DOS game or application reports no sound, or the wrong sound, almost always tracing back to a mismatch between the BLASTER environment variable and the card's actual jumper or Plug-and-Play settings.
This message covers several genuinely different underlying causes — a typo, a missing PATH entry, a missing file extension, or a corrupted COMMAND.COM. Here's how to tell them apart.
A DOS program can't print, or output is garbled — usually a port configuration, IRQ, or cable-mode mismatch, all diagnosable without any special tools.