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

Bug #1259943 reported by Matthias Gehre
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Appeared after login to freshly booted Ubuntu 13.10.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libevolution 3.8.4-0ubuntu1
Uname: Linux 3.11.0-031100rc7-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
Date: Wed Dec 11 14:47:32 2013
ExecutablePath: /usr/lib/evolution/3.8/evolution-alarm-notify
InstallationDate: Installed on 2013-02-26 (288 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/3.8/evolution-alarm-notify
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: evolution
StacktraceTop:
 g_settings_set_property (object=0x7fa7d5942ab0, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /build/buildd/glib2.0-2.38.1/./gio/gsettings.c:492
 object_set_property (nqueue=0x7fa7d589e200, value=<optimized out>, pspec=0x7fa7d57da740, object=0x7fa7d5942ab0) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1366
 g_object_new_internal (class=class@entry=0x7fa7d57cf2a0, params=params@entry=0x7fffa8d762a0, n_params=1) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1779
 g_object_new_valist (object_type=object_type@entry=140358818165504, first_property_name=first_property_name@entry=0x7fa7d204702f "schema-id", var_args=var_args@entry=0x7fffa8d763f8) at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:2002
 g_object_new (object_type=140358818165504, first_property_name=0x7fa7d204702f "schema-id") at /build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1559
Title: evolution-alarm-notify crashed with signal 5 in g_settings_set_property()
UpgradeStatus: Upgraded to saucy on 2013-11-05 (36 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers

Revision history for this message
Matthias Gehre (m-gehre) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007fa7d1a383d9 in ?? ()
 #1 0x0000000000000020 in ?? ()
 #2 0x00000004d5942ac0 in ?? ()
 #3 0x00007fa7d1a37b70 in ?? ()
 #4 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
Changed in evolution (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I think I have seen something quite similar to this bug. I made a fresh report as Bug #1548226 which includes some valid symbolic stack traces. Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the circumstances in which it happens are very similar?

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.