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?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212821

Title:
  Unity fails to load on old hardware on Saucy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1212821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to