Felix Lechner <felix.lech...@lease-up.com> skribis: > The status seems a bit bungled, though. I now use a lambda, i.e. no > 'command', with a fresh pull from 'devel'. Thanks!
[...] > Upcoming timer alarms: > Backtrace: > 8 (primitive-load "/run/current-system/profile/bin/herd") > In shepherd/scripts/herd.scm: > 796:9 7 (main . _) > In ice-9/boot-9.scm: > 1747:15 6 (with-exception-handler #<procedure 7f791ed93e40 at > ice-9/boot-9.scm:1831:7 (exn)> _ #:unwind? _ # _) > In shepherd/scripts/herd.scm: > 727:11 5 (_) > In srfi/srfi-1.scm: > 634:9 4 (for-each #<procedure 7f791ed91280 at ice-9/boot-9.scm:797:8 > args> ((service (version 0) (# (#)) # ?))) > In shepherd/scripts/herd.scm: > 323:19 3 (display-timer-events #<<calendar-event> seconds: (0) minutes: > (3 8 13 18 23 28 33 38 43 48 53 58) h?> ?) > In shepherd/service/timer.scm: > 253:21 2 (next-calendar-event #<<calendar-event> seconds: (0) minutes: (3 > 8 13 18 23 28 33 38 43 48 53 58) ho?> ?) > 233:18 1 (week-days->month-days #f 4 _) > In unknown file: > 0 (memv 1 #f) > > ERROR: In procedure memv: > In procedure memv: Wrong type argument in position 2 (expecting list): #f Could you share this service or at least the (calendar-event …) bit? Thanks, Ludo’.