Comment 3 for bug 306703

No, I can't; the sort of response I got here had me give up on Ubuntu quite some time ago and head back to Debian.

This bug report includes a detailed analysis and the explicit solution to the problem, which is a faulty script.
Having y'all ignore that for, oh, nine months, then ask me to redo the diagnosis is pretty insulting, really.

Perhaps you can glance at the script that is explicitly named, go to the line that is explicitly named, and check to see if the explicitly named bug is still present yourself, eh?