Comment 23 for bug 1623853
Revision history for this message
| Jean-Baptiste Lallement (jibel) wrote | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
My theory is:
- A change in apparmor triggers a recompilation of the profiles on upgrade
- repowerd starts early in the boot process and before u-s-c and unity8 (in the log above it starts at 7:37 and u-s-c at 7:40)
- After the upgrade, the system boots, repowerd starts, the compilation of the profiles starts too (at 7:36)
- The compilation of the profiles takes more than 1 minute (it stops at 7:37:09 according to the logs, 1 minute after it started)
- The device suspends when it reaches the suspend timeout.
- Because u-s-c is not started, there is no way to wake the device up with the power button.
- Plugging a power supply resumes the device and it proceeds with the boot.
For anyone with this problem, the easiest workaround it to connect the device to a power source, otherwise long press the power button, it should be harmless but it'll interrupt apparmor. In any case, the OTA is correctly applied.