I cannot recreate this issue on either 32-bit or 64-bit fully-updated trusty systems. What would be useful is to know if it also affects the Session Init (upstart running as the user) since that would allow debug to be collected without the kernel panicking.
To find out, please can those affected boot to a *desktop* and run the following as a non-root user:
I cannot recreate this issue on either 32-bit or 64-bit fully-updated trusty systems. What would be useful is to know if it also affects the Session Init (upstart running as the user) since that would allow debug to be collected without the kernel panicking.
To find out, please can those affected boot to a *desktop* and run the following as a non-root user:
$ get_state.sh | json_pp > upstart.state
$ start re-exec
Then, attach the following to this bug if a crash results:
$HOME/. xsession- errors cache/upstart/ upstart. state
$HOME/.
If the Session Init does crash, we might be lucky and get a crash file in /var/crash/.