PandaOSPandaOS
Account and help

Troubleshooting

Find the problem you see, and the fix for it.

Reference Updated 20 Nov 2026

Note: log times and crash times differ

Daily log names use your local time and crash files use UTC. A crash at 23:30 on 20 April in Berlin can sit next to a crash-20260420T21... file. Allow for the offset before deciding two files are unrelated.

What this covers

Common problems, each under a heading that says what you see, with the fix under it. The end of the page lists where PandaOS keeps its log files. When your problem is not here, send a bug report from Help & feedback: PandaOS can read its own logs and write the report with you.

PandaOS quit unexpectedly

Click your account circle at the end of the dock, pick Help & feedback, and choose Report a bug. Add Logs to the report. It attaches the app, update and crash logs from the last runs, so you do not have to find the files yourself. Nothing is uploaded until you submit.

PandaOS keeps crashing with graphics problems

Open Settings, pick General, and find Hardware Acceleration under Startup & System. On Auto, PandaOS turns it off by itself after repeated graphics crashes. Choose Off to turn it off now. The change applies after a restart.

An update says "Download not responding"

The download stopped. Open Settings and pick About. When a Download manually link shows under the update, use it to download the new release yourself and install it.

On Linux, a warning says secure credential storage is unavailable

PandaOS found no working system keyring, the place Linux keeps passwords encrypted. Without one, saved credentials cannot be encrypted and may be stored unencrypted on disk. Configure or unlock your system keyring, then restart PandaOS. The warning shows at the top of Settings, Account.

Where the log files are

All of these files stay on your computer. None is uploaded unless you attach it to a report.

Daily log

One file per day, kept for the last 7 days. Attach the file for the day of the problem.

SystemPath
macOS~/Library/Logs/PandaOS/main-YYYYMMDD.log
Windows%APPDATA%\PandaOS\logs\main-YYYYMMDD.log
Linux~/.config/PandaOS/logs/main-YYYYMMDD.log

Crash files

When part of PandaOS fails, a file named crash-YYYYMMDDTHHMMSS-<kind>.json is written next to the daily log. It holds the error, the app and system versions, a memory snapshot and the last 200 log lines before the failure.

KindWhat happened
uncaughtExceptionAn error nothing caught
unhandledRejectionA failed background task nothing handled
render-process-goneA window's content stopped
child-process-goneA helper process stopped
memory-pressureNot a crash: written while memory was running out, because running out of memory leaves no file of its own

Minidumps (rare)

For the rare crash deeper than the app itself, Electron, the framework PandaOS is built on, writes a binary minidump file. Attach it as it is; only developers can read it.

SystemFolder
macOS~/Library/Application Support/PandaOS/Crashpad/completed/
Windows%APPDATA%\PandaOS\Crashpad\reports\
Linux~/.config/PandaOS/Crashpad/completed/