evolution-addressbook-factory-subprocess crashed with SIGSEGV in g_io_stream_get_input_stream()

Bug #1746884 reported by Andreas Brauchli
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Addressbook is EWS-based

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 1 22:10:18 2018
ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
InstallationDate: Installed on 2018-01-24 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180123)
ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx23890x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/23890/3
SegvAnalysis:
 Segfault happened at: 0x7f0aecac1650 <g_io_stream_get_input_stream>: mov (%rdi),%rax
 PC (0x7f0aecac1650) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_io_stream_get_input_stream () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in g_io_stream_get_input_stream()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Andreas Brauchli (blk) wrote :
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 : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution-data-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

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.