indicator-datetime 0.2.3-0ubuntu3 crashed with SIGSEGV in g_type_check_instance_cast()

[Michael Schmidt]

Binary package hint: indicator-datetime

The error message appeared directly after login without any previous interaction.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
Uname: Linux 2.6.39-0-generic x86_64
Architecture: amd64
Date: Tue Jun 7 23:51:39 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x7f33af306bad <g_type_check_instance_cast+93>: movzbl 0x16(%rcx),%eax
 PC (0x7f33af306bad) ok
 source "0x16(%rcx)" (0x3334325a5f415356) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ido_calendar_menu_item_set_date () from /usr/lib/libido-0.1.so.0
 ?? () from /usr/lib/indicators/5/libdatetime.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to natty on 2011-04-17 (51 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x2849cb0, iface_type=42195904) at /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:3995
 ido_calendar_menu_item_set_date (menuitem=0x27d7440, year=2011, month=5, day=7) at idocalendarmenuitem.c:383
 menu_visible_notfy_cb (menu=0x2671700, pspec=<value optimized out>, user_data=<value optimized out>) at indicator-datetime.c:290
 g_closure_invoke (closure=0x27ca0a0, return_value=0x0, n_param_values=2, param_values=0x2781d90, invocation_hint=0x7fff23227bb0) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=275, instance=0x2671700, emission_return=0x0, instance_and_params=0x2781d90) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3252

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Barneedhar (barneedhar)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #851954, so it 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. Feel free to continue to report any other bugs you may find.

[Charles Kerr (charlesk)]

Reopening this ticket as it doesn't appear to be a duplicate of #851954 -- the traces are completely different.

[Charles Kerr (charlesk)]

In the retrace, the crash appears to be happening from a corrupt memory pointer.

However, the code base has changed quite a bit in the 8 months since this issue was reported. Is this behavior still happening for anyone in 11.10 or 12.04? If so, could an updated crash report be submitted?

[Elieser Ribeiro (rhaerinfo)]

(Unity) I do not know if it is the correct place to post but there is a failure to present the calendar (pt-BR) in the month in March, returning value (null).