Ubuntu
indicator-datetime package

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

Bug #1207060 reported by Christopher
302
This bug affects 66 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Confirmed
High
Unassigned
indicator-datetime (Ubuntu)
Confirmed
Medium
mubm

Bug Description

Probably similar to bug #1098812 but the app crashed for no apparent reason.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130731-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Wed Jul 31 14:51:31 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2013-07-05 (26 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130703)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff6af4bd951 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7ff6af4bd951) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libecal-1.2.so.15
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_object_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Christopher (soft-kristal) wrote :
Revision history for this message
Christopher (soft-kristal) wrote :

I wasn't doing anything that should have affected it, but for what it's worth, I had just started Simple Scan.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_ref (_object=_object@entry=0x247f790) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3054
 g_weak_ref_get (weak_ref=weak_ref@entry=0x24bdaf0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:4237
 cal_client_emit_backend_property_changed_idle_cb (user_data=0x24bdaf0) at e-cal-client.c:445
 g_main_dispatch (context=0x2473510) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3058
 g_main_context_dispatch (context=context@entry=0x2473510) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3634

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Christopher (soft-kristal) wrote :

On my stable 13.04 partition, the date and time is often 4 hours off my location.

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
Dimitri John Ledkov (xnox)
information type: Private → Public
Revision history for this message
mubm (mubm) wrote :

Just try open calendar, but when click on the icon "calendar" become anything, and about 2-3 days Ubuntu is crashed with shutdown PC.

Changed in indicator-datetime (Ubuntu):
assignee: nobody → mubm (mubm)
Revision history for this message
Vinay (vinay-wagh) wrote :

Bug confirmed on Saucy (x86_64). The bug seems to be related to evolution-calendar.

One can restart the date-time applet using the folliwing command:
$> /usr/lib/x86_64-linux-gnu/indicator-datetime-service &

VInay

Revision history for this message
Simplehuman (simplehuman) wrote :

This crash happened on my Saucy x64 today. With no reason. I was just reading a book.

Also, I don't use calendar

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

The changes landing in https://code.launchpad.net/~charlesk/indicator-datetime/lp-1204532/+merge/184155 may also affect this ticket.

The Stacktrace in this ticket is vague; however, it looks like a timing issue or dangling pointer in our EDS code. lp-1204532 eliminates the EDS object churn in indicator-datetime's planner-eds code, which may fix or ameliorate this ticket's crash. (Note, this is a wishy-washy assessment. I'd feel more confident on this point if I could reproduce the crash or if the stacktrace were more conclusive.)

Changed in indicator-datetime:
status: New → Confirmed
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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