indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()

[Marc Deslauriers]

Binary package hint: indicator-datetime

After fresh reboot

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.1.96-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Mar 5 15:13:20 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4048fa: mov 0x0(%rbp,%rcx,1),%edx
 PC (0x004048fa) ok
 source "0x0(%rbp,%rcx,1)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to natty on 2011-02-01 (32 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
XsessionErrors:
 (nm-applet:2796): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:2778): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (<unknown>:2761): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
 (<unknown>:2761): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.

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