Ubuntu
indicator-datetime package

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

Bug #1215003 reported by Susan Cragin
232
This bug affects 40 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Fix Released
Undecided
Unassigned
indicator-datetime (Ubuntu)
Fix Released
High
Iain Lane

Bug Description

This crash happened on startup.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130731-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 21 12:12:06 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2013-08-12 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811)
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_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe78418a764: mov 0x10(%rdi),%esi
 PC (0x7fe78418a764) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_date_time_to_unix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 indicator_datetime_planner_get_appointments ()
 ?? ()
Title: indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceSource:
 #0 0x00007fe78418a764 in ?? ()
 #1 0x00000000023d8820 in ?? ()
 #2 0x00007fe78418c659 in ?? ()
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
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
Revision history for this message
Haw Loeung (hloeung) wrote :

Maybe this backtrace will help?

Thread 1 (Thread 0x7ffff7fce840 (LWP 3950)):
#0 0x00007ffff6be3764 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff6be5659 in g_date_time_to_unix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x0000000000405c3f in my_get_appointments (planner=0x61f820, begin_datetime=<optimised out>, end_datetime=0x7fffd80015a0) at planner-eds.c:152
#3 0x000000000040541f in indicator_datetime_planner_get_appointments (self=0x61f820, begin=0x0, end=0x7fffd80015a0) at planner.c:188
#4 0x000000000040671b in get_all_appointments_this_month (self=0x61d0e0) at service.c:592
#5 create_calendar_state (self=self@entry=0x61d0e0) at service.c:621
#6 0x0000000000408783 in init_gactions (self=0x61d0e0) at service.c:1459
#7 indicator_datetime_service_init (self=0x61d0e0) at service.c:1889
#8 0x00007ffff6ee4d7b in g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007ffff6ec8475 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff6eca27d in g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff6ecaa2c in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x0000000000408cd2 in indicator_datetime_service_new () at service.c:1946
#13 0x0000000000404f52 in main (argc=<optimised out>, argv=<optimised out>) at main.c:53
(gdb)

Revision history for this message
Haw Loeung (hloeung) wrote :

Again with libglib2.0-0-dbg installed:

Thread 1 (Thread 0x7ffff7fce840 (LWP 4099)):
#0 g_date_time_to_instant (datetime=0x0) at /build/buildd/glib2.0-2.37.6/./glib/gdatetime.c:503
#1 0x00007ffff6be5659 in g_date_time_to_unix (datetime=<optimised out>) at /build/buildd/glib2.0-2.37.6/./glib/gdatetime.c:1899
#2 0x0000000000405c3f in my_get_appointments (planner=0x61f820, begin_datetime=<optimised out>, end_datetime=0x640f20) at planner-eds.c:152
#3 0x000000000040541f in indicator_datetime_planner_get_appointments (self=0x61f820, begin=begin@entry=0x0, end=end@entry=0x640f20) at planner.c:188
#4 0x000000000040671b in get_all_appointments_this_month (self=0x61d0e0) at service.c:592
#5 create_calendar_state (self=self@entry=0x61d0e0) at service.c:621
#6 0x0000000000408783 in init_gactions (self=0x61d0e0) at service.c:1459
#7 indicator_datetime_service_init (self=0x61d0e0) at service.c:1889
#8 0x00007ffff6ee4d7b in g_type_create_instance (type=<optimised out>) at /build/buildd/glib2.0-2.37.6/./gobject/gtype.c:1868
#9 0x00007ffff6ec8475 in g_object_new_internal (class=class@entry=0x61bb20, params=params@entry=0x0, n_params=n_params@entry=0) at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c:1746
#10 0x00007ffff6eca27d in g_object_newv (object_type=object_type@entry=6401904, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c:1890
#11 0x00007ffff6ecaa2c in g_object_new (object_type=6401904, first_property_name=first_property_name@entry=0x0) at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c:1556
#12 0x0000000000408cd2 in indicator_datetime_service_new () at service.c:1946
#13 0x0000000000404f52 in main (argc=<optimised out>, argv=<optimised out>) at main.c:53
(gdb)

Apport retracing service (apport)
tags: added: bugpattern-needed
Haw Loeung (hloeung)
tags: added: apport-collected
Revision history for this message
Sebastien Bacher (seb128) wrote :

That's an issue for those running saucy-proposed's glib version, please don't run saucy-proposed it's made for automatic testing and transitions, not for users...

The bug is fixed with https://code.launchpad.net/~laney/indicator-datetime/valid-day-of-month/+merge/181501 in any case

information type: Private → Public
Changed in indicator-datetime (Ubuntu):
assignee: nobody → Iain Lane (laney)
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-datetime - 12.10.3+13.10.20130731-0ubuntu3

---------------
indicator-datetime (12.10.3+13.10.20130731-0ubuntu3) saucy; urgency=low

  * g_simple_action_group_* were deprecated in glib; use g_action_map_*
    instead.
 -- Iain Lane <email address hidden> Thu, 22 Aug 2013 11:09:15 +0000

Changed in indicator-datetime (Ubuntu):
status: In Progress → Fix Released
Haw Loeung (hloeung)
Changed in indicator-datetime:
status: New → Fix Released
status: Fix Released → Fix Committed
Charles Kerr (charlesk)
Changed in indicator-datetime:
status: Fix Committed → Fix Released
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.