evolution-addressbook-factory-subprocess crashed with signal 5 in g_thread_new()

Bug #1885864 reported by Muelli on 2020-07-01
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Undecided
Unassigned

Bug Description

This is probably one of the many bugs that my Evolution produces, e.g. 1872240

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 1 07:30:02 2020
ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
InstallationDate: Installed on 2017-10-13 (991 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx15908x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/15908/2
Signal: 5
SourcePackage: evolution-data-server
StacktraceTop:
 g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evolution-addressbook-factory-subprocess crashed with signal 5 in g_thread_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1872240, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers