evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

Bug #1557370 reported by Thomas A. F. Thorne
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Medium
Unassigned

Bug Description

After rebooting my PC I was presented with an error report dialogue which lead me to filing this report. I do not know at what point the error was originally generated.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libevolution 3.10.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
Uname: Linux 3.16.0-67-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Mar 15 08:31:41 2016
ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
InstallationDate: Installed on 2015-03-12 (368 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: /usr/lib/evolution/3.10/evolution-alarm-notify
Signal: 5
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_set_property (object=0x7fe34d92d750, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:481
 object_set_property (nqueue=0x7fe34d910790, value=<optimized out>, pspec=0x7fe34d8a8070, object=0x7fe34d92d750) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1378
 g_object_new_internal (class=class@entry=0x7fe34d87ac00, params=params@entry=0x7ffe998e3f10, n_params=1) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1757
 g_object_new_valist (object_type=object_type@entry=140614235274864, first_property_name=first_property_name@entry=0x7fe34a6e8a4f "schema-id", var_args=var_args@entry=0x7ffe998e4068) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1980
 g_object_new (object_type=140614235274864, first_property_name=first_property_name@entry=0x7fe34a6e8a4f "schema-id") at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1571

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 evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I could not see anything sensitive in the logs so I have opened up this bug to being public.

information type: Private → Public
Revision history for this message
Andre Klapper (a9016009) wrote :

I cannot find the stacktrace in comment 3 in upstream bugzilla.gnome.org.

Note the #10 config_data_get_timezone () at config-data.c:73 in the trace.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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