indicator-session-service crashed with SIGABRT in g_closure_invoke()

[Libin Thomas]

Binary package hint: indicator-session

This happened when I had just logged into Unity and started an app (eclipse).

I had just logged out and logged in again since something funny had already happened in Unity.
In the previous session(a minute ago), I had logged into Unity and started a few heavy apps simultaneously - eclipse, win xp via virtuallbox , firefox etc. Suddenly I lost all my appearance settings - the fonts and icon theme reverted.
When I logged in again, my settings were restored.
I don't know if that is connected to the current crash but I am mentioning it just in case.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-session 0.2.15-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Thu Apr 7 20:30:00 2011
ExecutablePath: /usr/lib/indicator-session/indicator-session-service
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/indicator-session/indicator-session-service
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_US.UTF-8
 LANGUAGE=en_US:en
 LANG=en_US
Signal: 6
SourcePackage: indicator-session
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: indicator-session-service crashed with SIGABRT in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-01 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #747818, 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.