Comment 101 for bug 554172

Don Myers: Keep in mind this is an open source project and we need to all work together to fix this. I understand your frustration though, I have gone back to 9.10 because of this issue and it's working great for me. I think it's a good idea to let new releases mature somewhat before adopting them any ways. But it is a little disconcerting that this is happening on a LTS.

Developers: What can we do to get this bug addressed? I notice it is still in "Incomplete" status. What information do you need to move this back to "Confirmed" and get this assigned? I will gladly help in any way whatsoever.

Digression: Perhaps you should have the less technical users volunteer to help with QA. I realize it's a tedious process that wastes valuable developer's time. Basic things like testing printing is something intermediate users can do. We could define a list of basic functions to check to be sure they are all working ok with new releases. This can be for all functions, not just printing, getting multiple results from many users on the same function to corroborate.

I've tried removing proprietary NVIDIA drivers to see if would make a difference: No, it does not.

I think this may be a general upstart problem. I have noticed that boot sequence is highly inconsistent and seemingly unpredictable on consecutive boots, even when nothing major has changed on system. For example, the text that scrolls by on the screen is frequently different during subsequent boots. I get the Ubuntu splash screen with the dots showing progress, sometimes not. Sometimes I get the Nvidia proprietary Logo screen, sometimes not. I am booting with --debug kernel option and the last line of text in boot sequence is frequently different. I agree with Steve Langasek above that this is more than likely a general upstart problem, and not just a cups issue. See comment #69.

My suggestion: If everyone affected by this could on terminal do:

1. If you have a boot where printers do not appear in System->Administration->Printers, do a 'sudo start rc-sysinit' in your terminal. then do a 'ps aux' and see if more services start. Virtual terminals (ttys), irqbalance, acpid, cron, atd, winbindd all do not start for me when cupsd doesn't start (see my comment #92 on this bug).

2. please post what you find here.

If the majority of users here have several services not starting, in addition to cupsd, perhaps we could re-file this as an upstart bug?