Fixing Haiku Applications That Stop Launching After a System Update
Use package states, dependency inspection, safe mode, and debugger evidence instead of replacing random libraries.
Launch the application from Terminal to capture loader or runtime errors. Record its package, architecture, repository, and the update transaction. Do not copy libraries into /system; packagefs makes system content read-only and coherent by package state.
Boot the previous package state from the boot loader. If the application works there, compare changed packages and check for a compatible rebuild in HaikuDepot. Disable user add-ons or settings only after copying them.
For a crash, save the debugger report and symbols/revision information. Restoring a prior state is a rollback, not the final fix; report the smallest dependency transition that reproduces the failure.
Sources: Haiku package-state rollback, Haiku Debugger