В Wed, 20 May 2015 12:43:34 +0200 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2015-05-20 05:44, Andrei Borzenkov wrote:
В Wed, 20 May 2015 01:18:03 +0200 "Carlos E. R." <> пишет:
This is notebook which is put to sleep at least twice a day.
The problem exists. Cristian just wrote that he solved the issue, but has not mentioned how, or what people need to do to get it. Maybe it is a patch for factory, so does not apply to 13.2, unless it can be backported.
Maybe your machine was running at the precise time.
logrotate.timer has 12 hours accuracy with daily run which means system must be on some time between 00:00 and 12:00. The possible problem for those who *updated* to 13.2 was that systemd.timer did not get activated on update. This is unfortunate situation that was discussed on systemd list but I do not think any resolution is available - there is no way to know whether unit is not active because it simply was not activated or because it was intentionally not or deactivated. So even though defaults are changed to enable service, these defaults are not reapplied on update.