v0.68.1

Patch Changes

• The bug-report toast can be closed.

  Sending a report puts a toast in the corner that reports progress and then the outcome. It carried no close button, unlike the app's ordinary toasts, so the three outcomes that offered actions — the reference to copy, the email draft, the failed send you can retry — could only be waited out, and two of those never time out at all. Each of the five now carries a close button in the corner, in the same place the app's ordinary toasts put theirs. The separate Dismiss button on the in-progress and already-sending toasts is gone; the close button replaces it.

• No longer opens "the previous session crashed" at startup for a graphics glitch the app recovered from on its own.

  A recoverable GPU-process death is swallowed on purpose: the process relaunches in about a second, so an isolated one leaves the user nothing to describe. The dump it wrote outlived the session anyway, and the next launch's crash scan had no way to tell it from the dump of a crash nobody was ever told about, so the app spent one session hiding a glitch and the next one asking about it, often naming a version the user had already updated away from.

  The app now remembers the glitches it swallowed, and stays quiet at the next launch only about a leftover it can match to one of them. Anything it cannot place that precisely still prompts.

  Crash dumps remain attachable to a report the user opens themselves; what changed is only which deaths the app raises on its own.

• Fixed an error thrown inside every CodeMirror-backed editor when selecting with the mouse. Double-clicking to select a word and triple-clicking to select a line both threw, and so did the handler that starts a drag from a widget. Selecting still looked like it worked, because the browser's own selection took over once the editor's handler failed. That covers source mode, plain-text documents, the Mermaid editor, the text viewer, the raw MDX fallback, and the smaller code inputs in the property panel and preview dialogs. A dependency pin held @codemirror/state at a version older than the editor required, so the API those selection paths call was missing at runtime.

• The sync indicator recovers after a sleep, a Wi-Fi change, or a VPN flap.

  When a laptop sleeps or the network switches underneath you, the socket to the local server can die without the operating system ever reporting it closed. Open Knowledge notices the silence and reconnects on its own, and every edit made after that really was reaching the server. What did not recover was the claim about it: the status stayed short of "synced" for the rest of the session, and the "your edits aren't reaching the server" warning stayed on screen with no way to dismiss it. The only way out was to close and reopen the window.

  Both now clear as soon as the reconnect finishes. The warning is replaced by "Reconnected", which fades on its own, and the indicator returns to synced.

  Two quieter consequences of the same stuck state are fixed with it. Returning to a background tab flushes pending edits again rather than skipping the document, and reopening a document keeps the connection that was already working instead of tearing it down and building a new one.

  One behaviour to expect: a document that is still opening when the connection resets now shows "Connection dropped" with a Retry button, the same as any other dropped connection, instead of waiting in silence.

Downloads

Platform	Architecture	Download
macOS	Apple Silicon	OpenKnowledge-arm64.dmg
Windows	x64	OpenKnowledge-Setup-x64.exe
Windows	arm64	OpenKnowledge-Setup-arm64.exe
Debian / Ubuntu	x64	OpenKnowledge-amd64.deb
Debian / Ubuntu	arm64	OpenKnowledge-arm64.deb
Fedora / RHEL	x64	OpenKnowledge-x86_64.rpm
Fedora / RHEL	arm64	OpenKnowledge-aarch64.rpm