I've successfully verified this fix by removing slocate from a desktop install and observing ""none: prio 0" when running the cron job from package version 4.2.31-1ubuntu2. After updating to the proposed package, 4.2.31-1ubuntu2.1, the job was then observed to run with "best-effort: prio 7".
I've successfully verified this fix by removing slocate from a desktop install and observing ""none: prio 0" when running the cron job from package version 4.2.31-1ubuntu2. After updating to the proposed package, 4.2.31-1ubuntu2.1, the job was then observed to run with "best-effort: prio 7".