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

[Ryan Amick]

erro popped up after restart after todays upgrade

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Mon Oct 29 14:04:14 2012
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2012-05-16 (166 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x804d966: mov (%esi),%eax
 PC (0x0804d966) ok
 source "(%esi)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
UpgradeStatus: Upgraded to quantal on 2012-10-06 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:734
 update_appointments () at datetime-service.c:1397
 g_cclosure_marshal_VOID__OBJECTv (closure=closure@entry=0x95c94d0, return_value=return_value@entry=0x0, instance=instance@entry=0x95ca8b8, args=args@entry=0xbfaf7e8c "\020\316\223\264", marshal_data=marshal_data@entry=0x0, n_params=n_params@entry=1, param_types=param_types@entry=0x95c88e8) at /build/buildd/glib2.0-2.34.0/./gobject/gmarshal.c:1312
 _g_closure_invoke_va (closure=0x95c94d0, return_value=return_value@entry=0x0, instance=instance@entry=0x95ca8b8, args=args@entry=0xbfaf7e8c "\020\316\223\264", n_params=1, param_types=0x95c88e8) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=instance@entry=0x95ca8b8, signal_id=signal_id@entry=10, detail=detail@entry=0, var_args=var_args@entry=0xbfaf7e8c "\020\316\223\264") at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3211

[Launchpad Janitor (janitor)]

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

[Charles Kerr (charlesk)]

in indicator-datetime 12.10.2-0ubuntu3, line 734 of datetime-service.c is the "source = E_SOURCE" line of this passage:

> // Generate instances for all sources
> for (s=appointment_sources; s!=NULL; s=s->next) {
>
> ESource *source = E_SOURCE (s->data);
> ECalClient *ecal = e_cal_client_new(source, E_CAL_CLIENT_SOURCE_TYPE_EVENTS, &gerror);

Which makes me think that the appointment_sources array is being corrupted somehow.

Is this crash repeatable for anyone, or was it a one-off? I'd like to try and trigger it here in a testing environment.

[Dmitry Shachnev (mitya57)]

It happened three or four times for me on startup, but it doesn't happen always. I also don't know a way to trigger the crash.

[Rob D (robod)]

It seems to be happening everytime I logon for the first time after a reboot (I normally suspend). I've upgraded from 12.04. The description is exactly the same as above.

[iMac (imac-netstatz)]

Totally repeatable for me, on boot almost every time. I think it has something to do with evolution-ews.

--- stack trace ---
#0 0x0000000000406897 in update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:736
        source = 0x7f2740094d80
        ecal = 0x0
        current_zone = <optimized out>
        curtime = 0
        t1 = 0
        t2 = 1362782388
        l = <optimized out>
        s = 0x7f2740001aa0
        gerror = 0x7f275c276740
        i = <optimized out>
        width = 96
        height = 1
        sources = 0x0
        today = <optimized out>
        mday = 2
        mon = 32585216
        year = 0
        start_month_saved = 0
        start_tm = <optimized out>
        this_year = 1900
        days = {-106352976, 32767, 0, 32551, 96, 0, 4, 1, 4, 0, -106354872, 32767}
        highlightdays = <optimized out>
        sorted_comp_instances = <optimized out>
        time_format_str = <optimized out>
        apt_output = <optimized out>
        markeddays = {x = {139806555590864, 0, 139807058247234, 139807029321018, 140737382001008, 0, 139806555580712, 139805480452096, 140737382000456, 140737382000384, 140737382001032, 140737382000408, 3, 139806555590864, 4, 139805480452099}}
        marks = <optimized out>
#1 0x0000000000000008 in ?? ()
No symbol table info available.
#2 0x00007f2748044f90 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
--- source code stack trace ---
#0 0x0000000000406897 in update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:736
  731:
  732: ESource *source = E_SOURCE (s->data);
  733: ECalClient *ecal = e_cal_client_new(source, E_CAL_CLIENT_SOURCE_TYPE_EVENTS, &gerror);
  734:
  735: if (!ecal) {
  736: g_debug ("Cannot create ecal client: %s", gerror->message);
  737: g_clear_error (&gerror);
  738: continue;
  739: }
  740:
  741: icaltimezone* current_zone = icaltimezone_get_builtin_timezone(current_timezone);
#1 0x0000000000000008 in ?? ()
#2 0x00007f2748044f90 in ?? ()
#3 0x0000000000000000 in ?? ()

[Oibaf (oibaf)]

Is this still an issue?

[Ryan Amick (finisdiem)]

I'm not having this issue anymore.

Sent from my iPhone

> On Oct 26, 2013, at 1:05 PM, Oibaf <email address hidden> wrote:
>
> Is this still an issue?
>
> ** Changed in: indicator-datetime (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: indicator-datetime
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1072887
>
> Title:
> indicator-datetime-service crashed with SIGSEGV in
> update_appointment_menu_items()
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/indicator-datetime/+bug/1072887/+subscriptions

[Oibaf (oibaf)]

 From Ryan Amick <email address hidden>:
> I'm not having this issue anymore.
Thanks, closing.