Additional evidence: crash leaves stale runtime mounts and blocks future runs
While investigating continued silent failures after reinstall, I confirmed that Timeshift is crashing with a segmentation fault and failing to clean up runtime state. A recent crash report shows: Title: timeshift crashed with SIGSEGV in g_object_unref() After such a crash, no Timeshift process is running: pgrep -a timeshift → (no output) However, the snapshot device remains mounted under /run/timeshift: /dev/sda1 on /run/timeshift/<PID>/backup type ext4 (rw,…) This stale mount persists indefinitely until manually unmounted. While present, subsequent cron-initiated runs either: silently skip execution, or log “another instance of this application is running” No GUI notification is shown, and cron logs do not surface the failure to the user. This indicates that: Timeshift can crash (SIGSEGV in GLib object handling), cleanup/unmount logic is not crash-safe, stale runtime state blocks future scheduled snapshots, failures are not reported to the user. These behaviors together explain the intermittent and confusing snapshot gaps I have observed recently. Manual cleanup (umount /run/timeshift/...) immediately restores correct operation. This appears to be a robustness defect rather than a configuration issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141449 Title: Timeshift scheduled snapshots silently fail due to incorrect cron command, misleading GUI, and lack of error reporting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timeshift/+bug/2141449/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
