I also had this bug on a thinkpad x220 i7 sandy bridge tablet with integated intel graphics after doing an upgrade from 10.10 to 12.04 beta today Mar 26.
I ran "DISPLAY=:0.0 unity --reset" from vt2 and after a bunch of messages unity 3d started up correctly and continued to work after a relog.
Though in addition to warning messages there was a segfault when I ran --reset.
I also had this bug on a thinkpad x220 i7 sandy bridge tablet with integated intel graphics after doing an upgrade from 10.10 to 12.04 beta today Mar 26.
I ran "DISPLAY=:0.0 unity --reset" from vt2 and after a bunch of messages unity 3d started up correctly and continued to work after a relog.
Though in addition to warning messages there was a segfault when I ran --reset.
Compiz: 1:09.7.2-0ubuntu1
Unity: 5.8.0-0ubuntu2
(some successful messages)
...
Setting update "run_key"
(compiz:8770) GLib-CRITICAL **: g_source remove: assertion `tag > 0 ' failed
(compiz:8770) GLib-CRITICAL **: g_source remove: assertion `tag > 0 ' failed
(compiz:8770) GLib-CRITICAL **: g_source remove: assertion `tag > 0 ' failed
Segmentation Fault
$