Yes, it is 22.04, added this into the summary and description. ** Summary changed:
- Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course + Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course ** Description changed: + (Found in Ubuntu 22.04 LTS, also in 22.10) package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. - Please resolve the problem to make systemd-cron more usable. + Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. ** Summary changed: - Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course + Ubuntu 22.04/22.10, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course ** Summary changed: - Ubuntu 22.04/22.10, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course + Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course ** Description changed: - (Found in Ubuntu 22.04 LTS, also in 22.10) + (Found in Ubuntu 22.04 LTS) package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug description: (Found in Ubuntu 22.04 LTS) package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
