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

Bug #1098812 reported by frizzle21
358
This bug affects 81 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Fix Released
Undecided
Unassigned
indicator-datetime (Ubuntu)
Fix Released
High
Charles Kerr

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily12.11.23-0ubuntu1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 12 06:06:05 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2012-10-20 (83 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4064ff: mov 0x0(%rbp),%rdi
 PC (0x004064ff) ok
 source "0x0(%rbp)" (0xffffffffffffffff) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown 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 raring on 2012-12-09 (33 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
frizzle21 (frederik-nnaji) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:726
 g_cclosure_marshal_VOID__OBJECTv (closure=0x204bce0, return_value=<optimized out>, instance=0x7f93200035d0, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x2050990) at /build/buildd/glib2.0-2.34.3/./gobject/gmarshal.c:1312
 _g_closure_invoke_va (closure=0x204bce0, return_value=0x0, instance=0x7f93200035d0, args=0x7fff5373ed78, n_params=1, param_types=0x2050990) at /build/buildd/glib2.0-2.34.3/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f93200035d0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff5373ed78) at /build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3211
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.34.3/./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
tags: added: running-unity
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
Charles Kerr (charlesk)
Changed in indicator-datetime (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
information type: Private → Public
Changed in indicator-datetime (Ubuntu):
importance: Medium → High
Revision history for this message
jimjutte (jimjutte) wrote :

This occurred after a partial update on 13.10

Revision history for this message
Charles Kerr (charlesk) wrote :

This is caused by the same problems that caused bug #1197645.

For more information on this, see the change description at https://code.launchpad.net/~charlesk/indicator-datetime/lp-1204532/+merge/184155

Changed in indicator-datetime:
status: New → Fix Released
Changed in indicator-datetime (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.