Troubleshooting
Solutions to common problems.
Installation Issues
Linux: AppImage Won't Run
Problem: Double-clicking the AppImage does nothing.
Solution:
# Make it executable
chmod +x korppi_*.AppImage
# Run from terminal to see errors
./korppi_*.AppImagemacOS: "App is damaged"
Problem: macOS says the app is damaged and can't be opened. This is because Apple extorts open source software developers by making them pay 99$ per year to distribute their software, otherwise that message pops up. It is however trivial and completely safe to ignore it.
Solution:
# Remove quarantine attribute
xattr -cr /Applications/Korppi.app
# Or right-click → Open (bypasses Gatekeeper)Windows: SmartScreen Warning
Problem: Windows Defender SmartScreen blocks the installer.
Solution:
- Click "More info"
- Click "Run anyway"
- This is normal for new/unsigned apps
Startup Issues
Blank Window
Problem: Korppi opens but shows a blank white screen.
Solutions:
- Wait a few seconds (initial load can be slow)
- Try
Ctrl+Shift+Rto force reload - Check if running from a network drive (try local)
- Disable hardware acceleration in system settings
Crashes on Launch
Problem: Korppi crashes immediately.
Solutions:
- Check system requirements
- Update graphics drivers
- Try launching from terminal for error messages:
# Linux ./korppi_*.AppImage # macOS /Applications/Korppi.app/Contents/MacOS/Korppi - Check for conflicting antivirus software
Launch Korppi from the terminal to see error messages:
# Open a specific file
korppi /path/to/document.kmdSee the error messages for more information.
Document Issues
Can't Open Document
Problem: Error when opening a .kmd
file.
Solutions:
- Check file permissions
- Verify the file isn't corrupted:
unzip -t document.kmd - Try extracting content manually:
unzip -p document.kmd content.md > recovered.md
Document Won't Save
Problem: Saving fails with an error.
Solutions:
- Check disk space
- Verify write permissions for the folder
- Try "Save As" to a different location
- Check if another program has the file locked
Lost Changes
Problem: Recent edits are missing.
Solutions:
- Check tab indicator—red dot means unsaved
- Look for autosave backup (if enabled)
- Check the timeline for recent patches
- Look in system temp directory for recovery files
Editor Issues
Can't Type in Editor
Problem: Clicking in editor does nothing.
Solutions:
- Click directly on the white page area
- Check if a modal dialog is covering the editor
- Try
Ctrl+Shift+Rto reload - Check if browser zoom is extreme (reset to 100%)
Formatting Not Working
Problem: Bold/italic shortcuts do nothing.
Solutions:
- Make sure text is selected
- Try the toolbar buttons instead
- Check for conflicting browser extensions
- Reload with
Ctrl+Shift+R
Slow Performance
Problem: Editor lags when typing.
Solutions:
- Large documents (50K+ words) can be slow
- Try splitting into multiple documents
- Close other resource-heavy applications
- Check if timeline has many patches
Export Issues
DOCX Export Fails
Problem: Word export produces an error or empty file.
Solutions:
- Check available disk space
- Make sure document isn't empty
- Try exporting a simple test document first
- Report the issue with error details
Markdown Export Loses Formatting
Problem: Exported .md file looks
wrong.
Solutions:
- This is expected—some Korppi features don't translate
- Comments are stripped (expected behavior)
- Check if the issue is in the viewer, not the file
- Open the
.mdin a text editor to verify content
Timeline Issues
No Patches Appear
Problem: Timeline is empty despite editing.
Solutions:
- Patches appear after saving
- Try making a larger edit
- Check if you're viewing a new document
- Reload the document
Can't Restore Version
Problem: Restore button doesn't work.
Solutions:
- Make sure a patch is selected
- Check for error messages
- Try preview first
- Save current doc, reload, try again
Comments Issues
Comments Don't Appear
Problem: Added comment but can't see it.
Solutions:
- Check the Comments panel (right sidebar)
- Click the comments counter in the bottom left to bring up the right sidebar.
- Look for highlight on the text
- Check comment filter (show "All")
- Reload document
Getting More Help
Collect Debug Info
When reporting issues, include:
- Korppi version: (About menu or package.json)
- Operating system: (Linux distro/version, macOS version, Windows version)
- Error messages: (from terminal if available)
- Steps to reproduce: (what exactly you did)
Report an Issue
- Go to GitHub Issues
- Check if issue already exists
- Create new issue with template
- Include debug info above
Developer Console
For JavaScript errors:
Ctrl+Right-Click anywhere → Inspect Element
This opens the browser dev tools where you can see console errors.
Related
- FAQ - General questions
- Installation - Setup instructions