unity-greeter crashed with SIGSEGV in g_main_context_dispatch()

[D. Wegener]

I received a crash dialog after starting system in text mode, logging in, and running startx to bring up desktop. Problem may be related to non standard startup.

I'm running in text mode because when I try booting in graphics mode, the display manager(lightdm) goes into a restart loop. The login screen is displayed, I hear the Ubuntu drums, and the display manager immediately restarts. I don't get a chance to enter my password, select a different user, or change any options.

Is it possible that the cause of this unity-greeter crash could also be causing the display manager restart loop?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Thu Mar 29 19:35:02 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-greeter
Title: unity-greeter crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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 #946674, 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.

[D. Wegener (dpwegener)]

This issue has been marked as a duplicate of a private bug. That prevents me from looking at the bug to confirm it is a duplicate or to see any comments/status of the bug to determine when it might be fixed or work arounds.

I'm not sure what it means for a bug to be private, but could someone look at making the bug public so I can see it?