gnome-control-center assert failure: gnome-control-center: intel_resolve_map.c:46: intel_resolve_map_set: Assertion `(*tail)->need == need' failed.

[Lars Karlitski]

Right after two-factor auth to google finished.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu12
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
AssertionMessage: gnome-control-center: intel_resolve_map.c:46: intel_resolve_map_set: Assertion `(*tail)->need == need' failed.
Date: Mon Aug 27 11:25:14 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: gnome-control-center credentials
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7fcc98d806c6 "(*tail)->need == need", file=0x7fcc98d806b2 "intel_resolve_map.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7fcc98d806c6 "(*tail)->need == need", file=0x7fcc98d806b2 "intel_resolve_map.c", line=46, function=0x7fcc98d806e0 "intel_resolve_map_set") at assert.c:103
 intel_resolve_map_set () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/libdricore8.1.0.so.1
Title: gnome-control-center assert failure: gnome-control-center: intel_resolve_map.c:46: intel_resolve_map_set: Assertion `(*tail)->need == need' failed.
UpgradeStatus: Upgraded to quantal on 2012-06-09 (78 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.90-0ubuntu1
 gnome-control-center-signon 0.0.13-0ubuntu1
 indicator-datetime 12.10.0-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1041891, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.