Yeah, it's very unfortunate that apport incorrectly marks bugs as dups and removes the traceback information before a developer gets a chance to look.
It really sounds like a problem when running unity-support-test during the boot sequence, and the fingers generally point to a bug in the OpenGL driver somewhere. Is there any way you could capture a stack trace (crash report, whatever) and attach to this bug instead?
Yeah, it's very unfortunate that apport incorrectly marks bugs as dups and removes the traceback information before a developer gets a chance to look.
It really sounds like a problem when running unity-support-test during the boot sequence, and the fingers generally point to a bug in the OpenGL driver somewhere. Is there any way you could capture a stack trace (crash report, whatever) and attach to this bug instead?