Troubleshooting

Most problems on a rolling-release system come from one of three things: a system that has not been updated in a while, a signature check that cannot succeed because a keyring is out of date, or an update that changed something you were relying on. These pages cover all three, and the last of them explains where to report what is left.

If you are stuck, the Discord channel is the fastest place to ask.

• Updating is not optional – Why a rolling release must be updated entirely, how to update Ditana on the desktop or in a terminal, and what actions to take afterwards.
• “invalid or corrupted package (PGP signature)” – What should be done when pacman refuses a package due to its inability to validate the signature, and how to manually verify Ditana’s signing key yourself.
• An update broke something – Four steps to discover what an update changed and to get a functioning system back.
• Flatpak or Bubblejail stopped working after an update – How to restore Flatpak and Bubblejail on a machine installed from the 0.9.3 medium.
• A Chromium-based program aborts: “The SUID sandbox helper binary was found, but is not configured correctly” – Why Discord and other programs built on Chromium or Electron may abort at start under Ditana’s hardening, and how to fix it.
• Reporting a bug – Which of Ditana’s repositories a problem belongs in, and what a useful report contains.