mweinbergh opened omacom/omarchy#16677 after the October 25 clock rollback, reporting millions of timer warnings, accumulated shell logs filling the runtime filesystem and failures launching applications through UWSM. 
AzrielSins added a London report with warning timestamps and subsequent logger and application-daemon failures, while explicitly noting that filesystem occupancy could no longer be established after reboot.
Dominik-O22 supplied a Berlin report and traced the suspected loop to Quickshell's handling of ambiguous local times in SystemClock. The issue remains open. These reports support investigation of the clock and logging paths; they do not establish a merged fix.
