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

Bug #1087410 reported by Sam Segers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Get a lot of errors with datetime.
I use evolution for adding my google agenda to the datetime-service.

Have these on two different setups (pc and laptop)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Thu Dec 6 20:32:36 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2012-02-02 (307 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=nl_BE:nl
 LANG=nl_BE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x406897: mov 0x8(%rax),%rcx
 PC (0x00406897) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () 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_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-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-18 (48 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Sam Segers (sam-sgrs) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:736
 g_cclosure_marshal_VOID__OBJECTv (closure=0x1e6bd20, return_value=<optimized out>, instance=0x7f78140035d0, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x1e6fa20) at /build/buildd/glib2.0-2.34.1/./gobject/gmarshal.c:1312
 _g_closure_invoke_va (closure=0x1e6bd20, return_value=0x0, instance=0x7f78140035d0, args=0x7fff813b6418, n_params=1, param_types=0x1e6fa20) at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f78140035d0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff813b6418) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3356

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
summary: indicator-datetime-service crashed with SIGSEGV in
- g_cclosure_marshal_VOID__OBJECTv()
+ update_appointment_menu_items()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.