Ubuntu
indicator-datetime package

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

Bug #1197645 reported by omarly666
314
This bug affects 96 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Fix Released
Medium
Charles Kerr

Bug Description

errorcode, and restart of indicator, apport showed me

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130703.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
Uname: Linux 3.9.0-4-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
Date: Thu Jul 4 07:30:03 2013
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
SegvAnalysis:
 Segfault happened at: 0xb74110ee <g_object_ref+30>: cmpl $0x50,(%eax)
 PC (0xb74110ee) ok
 source "$0x50" ok
 destination "(%eax)" (0xaaaaaaaa) 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/i386-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libecal-1.2.so.15
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_object_ref()
UpgradeStatus: Upgraded to saucy on 2013-06-10 (23 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Related branches

lp:~charlesk/indicator-datetime/lp-1204532
Ted Gould (community): Approve
PS Jenkins bot (community): Approve (continuous-integration)
Diff: 1014 lines (+477/-176)
4 files modified
src/planner-eds.c (+261/-80)
src/planner.c (+29/-2)
src/planner.h (+33/-7)
src/service.c (+154/-87)
Revision history for this message
omarly666 (omarly666) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_ref (_object=_object@entry=0x90e44b8) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3054
 g_weak_ref_get (weak_ref=weak_ref@entry=0xb461d338) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:4237
 cal_client_emit_backend_property_changed_idle_cb (user_data=user_data@entry=0xb461d338) at e-cal-client.c:445
 g_idle_dispatch (source=source@entry=0x90fd188, callback=0xb76da780 <cal_client_emit_backend_property_changed_idle_cb>, user_data=0xb461d338) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:5235
 g_main_dispatch (context=0x90ccb80) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3058

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-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: indicator-datetime-service crashed with SIGSEGV in g_object_ref()

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

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
Apport retracing service (apport)
tags: added: bugpattern-needed
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.)

information type: Private → Public
Revision history for this message
Charles Kerr (charlesk) wrote :

The possible fix mentioned in the previous comment has landed now in indicator-datetime-13.10.0+13.10.20130911.3-0ubuntu1

Changed in indicator-datetime (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Charles Kerr (charlesk) wrote :

There haven't been any more reports of this since the fix above landed in 13.10.0+13.10.20130911.3-0ubuntu1.

Since it was being reported so frequently before the release, I think it's safe to mark this as fixed.

Changed in indicator-datetime (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
status: In Progress → Fix Released
Charles Kerr (charlesk)
summary: - indicator-datetime-service crashed with SIGSEGV in g_object_ref()
+ indicator-datetime-service crashed with SIGSEGV in
+ cal_client_emit_backend_property_changed_idle_cb()
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.