Troubleshooting
Logs and crash reports
Help > Show logs in Explorer (on Linux, Show logs in your File Manager) opens the log folder. Puck writes one log a day there, and a crash-<time>.txt report if it ever stops unexpectedly. Puck sends nothing anywhere; attach these files yourself when you report a problem.
| System | Settings and logs |
|---|---|
| Windows | %APPDATA%\Puck, logs in %APPDATA%\Puck\logs |
| Linux | ~/.config/oberon (or $XDG_CONFIG_HOME/oberon), logs in its logs folder |
Git is missing or too old
Puck needs Git 2.38 or later. On Windows it brings its own; on Linux it uses the system’s. When the Git it finds is missing or older, a dialog blocks the window and says what to install (Install Puck).
Signing in on Linux
Puck keeps your sign-ins in the system’s keyring through the Secret Service (GNOME Keyring, KWallet). Without one, the sign-in lasts until Puck quits, and Options > Accounts says so.
HTTPS passwords and the Git Credential Manager
For hosts other than GitHub, Puck asks for the user name and password when Git needs them and can save them. Options > Advanced > Use Git Credential Manager hands those hosts to the Git Credential Manager instead.
SSH
Puck uses your SSH keys and config as Git does. On Windows, Options > Advanced > Use system OpenSSH uses the OpenSSH that comes with Windows, with its agent. When a key needs a passphrase or a host is new, Puck asks in a dialog.
Proxies
Git and Puck follow the system’s proxy settings, including PAC scripts, unless your Git config sets its own http.proxy.
Certificates
A server whose certificate the system does not trust shows a dialog with the certificate. Trust it there only if you know why it is not trusted.
A repository went missing
If a repository’s folder is moved or deleted, Puck shows it as missing with Locate, Clone again, and Remove.