Worked for next boot.... failed on next two subsequent cold boots...
I must try to find time to investigate the workings of upstart, from what I have read so far I am guessing either the CUPS start process has not been fully ported and fails if certain 'events' occur/do not occur (maybe along with other services that I have not noticed because I do not use them..) or.. at some point upstart is provided with a NULL runlevel argument and skips processing subsequent events.
A thought.. what if there are many more instances of CUPS not starting but not reported as the users have no printer and have not noticed..
Tried the workaround mentioned in bug 524186.
Worked for next boot.... failed on next two subsequent cold boots...
I must try to find time to investigate the workings of upstart, from what I have read so far I am guessing either the CUPS start process has not been fully ported and fails if certain 'events' occur/do not occur (maybe along with other services that I have not noticed because I do not use them..) or.. at some point upstart is provided with a NULL runlevel argument and skips processing subsequent events.
A thought.. what if there are many more instances of CUPS not starting but not reported as the users have no printer and have not noticed..