Michael's "/etc/init/" showed 4 upstart conf files updated recently; three on the 14th when this issue began being reported:
$ ls -latr ... -rw-r--r-- 1 tj tj 480 Jan 9 11:34 nvidia-persistenced.conf -rw-r--r-- 1 tj tj 483 Jan 14 04:28 alsa-store.conf -rw-r--r-- 1 tj tj 609 Jan 14 04:28 alsa-state.conf -rw-r--r-- 1 tj tj 494 Jan 14 04:28 alsa-restore.conf
I asked Michael to remove them and run the 'telinit u' tests again. With these files removed the "get_state.sh" test did not provoke a fault.
Adding back the three alsa files caused the fault so he tested the alsa conf files one by one.
alsa-restore.conf == SEGFAULT alsa-state.conf == SEGFAULT alsa-store.conf == SEGFAULT
Michael's "/etc/init/" showed 4 upstart conf files updated recently; three on the 14th when this issue began being reported:
$ ls -latr persistenced. conf
...
-rw-r--r-- 1 tj tj 480 Jan 9 11:34 nvidia-
-rw-r--r-- 1 tj tj 483 Jan 14 04:28 alsa-store.conf
-rw-r--r-- 1 tj tj 609 Jan 14 04:28 alsa-state.conf
-rw-r--r-- 1 tj tj 494 Jan 14 04:28 alsa-restore.conf
I asked Michael to remove them and run the 'telinit u' tests again. With these files removed the "get_state.sh" test did not provoke a fault.
Adding back the three alsa files caused the fault so he tested the alsa conf files one by one.
alsa-restore.conf == SEGFAULT
alsa-state.conf == SEGFAULT
alsa-store.conf == SEGFAULT