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

Bug #1061867 reported by Jaromir Obr on 2012-10-04
180
This bug affects 26 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Fix Released
High
Lars Karlitski
indicator-datetime (Ubuntu)
High
Unassigned
Quantal
High
Unassigned

Bug Description

It happened a few minutes after login to Gnome.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Thu Oct 4 22:20:46 2012
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111011)
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
SegvAnalysis:
 Segfault happened at: 0x7f5f417b9eb9 <e_client_open_sync+9>: mov (%rdi),%rax
 PC (0x7f5f417b9eb9) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 e_client_open_sync () from /usr/lib/libedataserver-1.2.so.17
 ?? ()
 g_closure_invoke () 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
Title: indicator-datetime-service crashed with SIGSEGV in e_client_open_sync()
UpgradeStatus: Upgraded to quantal on 2012-09-07 (26 days ago)
UserGroups:

Related branches

Jaromir Obr (jaromir-obr) wrote :

StacktraceTop:
 e_client_open_sync (client=0x0, only_if_exists=only_if_exists@entry=1, cancellable=cancellable@entry=0x0, error=error@entry=0x7fff75b8a748) at e-client.c:1377
 update_appointment_menu_items (unused=<optimized out>) at datetime-service.c:749
 g_closure_invoke (closure=0x25751d0, return_value=0x0, n_param_values=1, param_values=0x7fff75b8aaf0, invocation_hint=0x7fff75b8aa90) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x7f5f18014db0, detail=detail@entry=0, instance=instance@entry=0x7f5f1801bd80, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff75b8aaf0) at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x7f5f1801bd80, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff75b8ad38) at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3300

Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
tags: added: running-unity
security vulnerability: no → yes
security vulnerability: yes → no
visibility: private → public
Changed in indicator-datetime (Ubuntu):
importance: Medium → High
Changed in indicator-datetime (Ubuntu):
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-datetime - 12.10.2-0ubuntu2

---------------
indicator-datetime (12.10.2-0ubuntu2) quantal; urgency=low

  * Backport fix from Lars for a missing NULL check leading to segfault
    (lp: #1061867)
 -- Sebastien Bacher <email address hidden> Fri, 05 Oct 2012 17:24:16 +0200

Changed in indicator-datetime (Ubuntu Quantal):
status: Fix Committed → Fix Released
Charles Kerr (charlesk) on 2012-10-05
Changed in indicator-datetime:
assignee: nobody → Lars Uebernickel (larsu)
milestone: none → 12.10.3
importance: Undecided → High
status: New → Fix Committed
Lars Karlitski (larsu) on 2013-09-10
Changed in indicator-datetime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers