I don't have a maguro device so debugging is going to have to be by proxy :)
A few questions:
1) Does this only occur when the system is read-only?
2) Are logs growning fast in ~/.cache/upstart/ ?
3) What is the screen doing when it is on? Is it enough to run "powerd-cli display on" to see the issue?
4) Is the issue seen on any other hardware?
5) How do you toggle between Mir and SF?
Please could you:
a) Run the Session Init in debug mode by adding '--debug' to 'init --user' in /usr/bin/ubuntu-touch-session.
b) attach ~/.xsession-errors
c) Get an strace of the Session Init.
Sounds like this issue may be related to kernel bug 1234743.
I don't have a maguro device so debugging is going to have to be by proxy :)
A few questions:
1) Does this only occur when the system is read-only?
2) Are logs growning fast in ~/.cache/upstart/ ?
3) What is the screen doing when it is on? Is it enough to run "powerd-cli display on" to see the issue?
4) Is the issue seen on any other hardware?
5) How do you toggle between Mir and SF?
Please could you:
a) Run the Session Init in debug mode by adding '--debug' to 'init --user' in /usr/bin/ ubuntu- touch-session.
b) attach ~/.xsession-errors
c) Get an strace of the Session Init.
Sounds like this issue may be related to kernel bug 1234743.