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

Bug #1548226 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

Login to Ubuntu and you are presented with this problem. In my case this seems to have come about after removing the evolution mail client.

Suggested duplicates were:
Bug #1386599
Bug #1264075
Bug #1259943
Bug #273951
Bug #1386599

All of those do look similar to me. However I am raising a new ticket as some of them have no traces and some of them have traces that the retracer failed to deal with.

I do not think the traces matter, I think the problem is that you cannot easily and cleanly uninstall evolution after having used it for a while. All I have installed is the evolution-data-server package.
$ sudo aptitude search evolution | grep "i "
i A evolution-data-server - evolution database backend server
i A evolution-data-server-common - architecture independent files for Evoluti
i A evolution-data-server-online-ac - evolution data server integration with Ubu
p evolution-mapi - Exchange support for the Evolution groupwa

If I attempt to remove that, it want to take some other things with it:
thomasthorne@thorne-ul-dt:~$ sudo aptitude remove evolution-data-server
The following packages will be REMOVED:
  evolution-data-server
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 1,452 kB will be freed.
The following packages have unmet dependencies:
 libfolks-eds25 : Depends: evolution-data-server (>= 3.2.0) but it is not going to be installed.
The following actions will resolve these dependencies:

     Remove the following packages:
1) gnome-contacts
2) libfolks-eds25

     Leave the following dependencies unresolved:
3) indicator-datetime recommends evolution-data-server
4) libfolks25 recommends libfolks-eds25
5) empathy recommends gnome-contacts

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates)]

Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Downgrade the following packages:
1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 3.10.4-0ubuntu1
2) evolution-data-server-common [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 3.10.4-0
3) evolution-data-server-online-accounts [3.10.4-0ubuntu1.5 (now, trusty-updates) ->
4) libcamel-1.2-45 [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 3.10.4-0ubuntu1 (trus

Accept this solution? [Y/n/q/?]

I guess that the 5 other bugs raised for this since 2008 might also have been from people that removed evolution. There was also a Gnome bug marked as related https://bugzilla.gnome.org/show_bug.cgi?id=553631 but it was for a version that was too old to be looked into. If raising this ticket gets some helpful traces generated, perhapse that bug could be updated to show them too.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libevolution 3.10.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
Uname: Linux 3.16.0-60-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 22 07:32:30 2016
ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
InstallationDate: Installed on 2015-03-12 (346 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=0x7fa922e4feb0, 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=0x7fa922cc5c90, value=<optimized out>, pspec=0x7fa922d04070, object=0x7fa922e4feb0) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1378
 g_object_new_internal (class=class@entry=0x7fa922d0f680, params=params@entry=0x7ffd8a9f5190, n_params=1) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1757
 g_object_new_valist (object_type=object_type@entry=140364410085328, first_property_name=first_property_name@entry=0x7fa920347a4f "schema-id", var_args=var_args@entry=0x7ffd8a9f52e8) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1980
 g_object_new (object_type=140364410085328, first_property_name=first_property_name@entry=0x7fa920347a4f "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 have looked through the traces and other logs files supplied, nothing looks sensitive to me. Setting to public as I cannot see a reason to keep this bug marked as private.

information type: Private → Public
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Bug #1506430 contains very little information, so it is hard to say if this is a duplicate of that bug or not. It looks as if things should be fixed in 3.16.5-1ubuntu2; so if anyone has that package (or a later one) installed and sees this issue repeat they should either reopen Bug #1506430 or mark this bug as not being a duplicate of it.

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.