** Summary changed: - Clock set to past confuses AppArmour cache validation + Clock set to past confuses AppArmor cache validation
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch- customization-hooks in Ubuntu. https://bugs.launchpad.net/bugs/1385382 Title: Clock set to past confuses AppArmor cache validation Status in AppArmor Linux application security framework: Won't Fix Status in “ubuntu-touch-customization-hooks” package in Ubuntu: Triaged Bug description: During initial boot sometimes clock could be set to past, which will confuse logic validating precompiled AppArmour cache, causing cache recreation. If time is not set correct(valid) value, even consequent boots will fail to validate cache, forcing cache recreation. This bug affects Initial out of the box experience, since device clock is set in the factory to default value, for example 0:0am 1st of January 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385382/+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
