indicator-session-service crashed with signal 5 in g_type_create_instance()

[Rachid Achellal]

Crashed when I tried to restart desktop

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-session 0.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-server 3.0.0
Uname: Linux 3.0.0-7-server x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Jul 27 19:09:24 2011
ExecutablePath: /usr/lib/indicator-session/indicator-session-service
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
ProcCmdline: /usr/lib/indicator-session/indicator-session-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: indicator-session
StacktraceTop:
 ?? ()
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-session-service crashed with signal 5 in g_type_create_instance()
UpgradeStatus: Upgraded to oneiric on 2011-07-27 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 g_type_create_instance (type=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gobject/gtype.c:1885
 g_object_constructor (type=<value optimized out>, n_construct_properties=0, construct_params=0x0) at /build/buildd/glib2.0-2.29.14/./gobject/gobject.c:1629
 g_object_newv (object_type=35828336, n_parameters=0, parameters=0x0) at /build/buildd/glib2.0-2.29.14/./gobject/gobject.c:1412
 g_object_new (object_type=35828336, first_property_name=0x0) at /build/buildd/glib2.0-2.29.14/./gobject/gobject.c:1322

[Mehmet Ali Anıl (mehmet-ali-anil)]

I confirm that my 11.10 crashes the same way, only, with Unity (not 2d) and i386.

[Sense Egbert Hofstede (sense)]

Thank you for helping with making Ubuntu better by reporting this bug. This issue has been reported several times before and we're using bug #813139 to track it. I am marking this bug report as a duplicate of that. Please continue the conversation there. Thanks!