SchedPlus troubleshooting

A package will not install or start

Verify the release SHA-256 checksum, then confirm you selected a package for your CPU architecture. Debian Standard, Lite, and CLI packages are mutually exclusive alternative bundles: remove the installed edition before installing another. Standard already supports CLI commands, so it does not need the separate schedplus-cli package. Switching packages retains the shared task database. For an AppImage without FUSE, use --appimage-extract and run squashfs-root/AppRun. Windows portable ZIPs must be fully extracted before launching; do not run an executable from inside the ZIP viewer.

A desktop interface does not start

Install the profile that provides it: pip install -e ".[lite]" for Tkinter support or pip install -e ".[standard]" for PyQt. For Tkinter on Linux, install the operating-system python3-tk package. Use schedplus --tk or schedplus --py to bypass the selector.

A task will not save

Check that the date is a real YYYY-MM-DD date, the time is HH:MM in 24-hour time, and the description has text. For example, 2026-02-30, 9:30, and an empty description are rejected.

The database is locked or read-only

Close other SchedPlus processes and try again. If the error persists, check that your user-data directory is writable and has free disk space. Do not delete tasks.db unless you intend to discard its contents.

SchedPlus reports database recovery

The application found a damaged SQLite file, preserved it as tasks_corrupted_<timestamp>.db in the same data folder, and created a clean database. Keep that backup before investigating or restoring data. The storage log, schedplus.log, is in the same folder.

SchedPlus reports a newer database schema

The installed SchedPlus build is older than the build that last upgraded this database. SchedPlus deliberately leaves the database unchanged. Reinstall the same or a newer application version; do not lower PRAGMA user_version or edit the schema manually. A normal schema upgrade creates a tasks_pre_migration_v<old>_to_v<new>_*.db safety backup in the data folder.

I removed or upgraded SchedPlus and cannot find my tasks

Packages deliberately retain task data. Check the package-appropriate path: %APPDATA%\\ZFordDev\\SchedPlus on Windows, ~/.local/share/ZFordDev/SchedPlus on Debian/AppImage Linux, or $SNAP_USER_COMMON/SchedPlus for strict Snap. If upgrading from 0.7.3 or earlier, start SchedPlus once so it can migrate the old in-application database. Always copy tasks.db while SchedPlus is closed before manually moving or restoring it.

Update commands are disabled

This is expected for source checkouts and Store-managed packages. The built-in updater only supports a compatible managed packaged build with signed release metadata.

For a supported package, use Last update result in the desktop interface or run schedplus update status. Signature, checksum, channel, or package-identity errors deliberately stop the update. They do not stop SchedPlus from opening. Debian and AppImage downloads are not installed automatically; use the verified path reported by SchedPlus with your normal package tools.

For reproducible bug reports, include your operating system, Python version, launch command, exact error, and the relevant schedplus.log lines—without sharing private task content.