Ubuntu GNOME

evolution-calendar-factory crashed with SIGSEGV

Bug #1370108 reported by Cristian Aravena Romero on 2014-09-16

24

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu GNOME	New	Undecided	Unassigned

Bug Description

Crash.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.12.6-0ubuntu2~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging]
Uname: Linux 3.17.0-031700rc5-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 16 12:03:30 2014
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2014-09-03 (13 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
SegvAnalysis:
Segfault happened at: 0x7f389d9cef6b: mov 0x90(%rbx),%rdi
PC (0x7f389d9cef6b) ok
source "0x90(%rbx)" (0x00000090) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
?? () 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
?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcaldav.so
Title: evolution-calendar-factory crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2014-09-16:

#1

CrashDB.txt Edit (263 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (9.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (702 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (308 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (75.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (845 bytes, text/plain; charset="utf-8")
Registers.txt Edit (677 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (36.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2014-09-16:

#2

StacktraceTop:
socket_connect_finish (sock=<optimized out>, conn=0x0) at soup-socket.c:675
soup_socket_connect_sync_internal (sock=<optimized out>, cancellable=cancellable@entry=0x7f38a2cf1370, error=error@entry=0x7f3874f76ba8) at soup-socket.c:884
soup_connection_connect_sync (conn=0x7f385c004e30, cancellable=0x7f38a2cf1370, error=error@entry=0x7f3874f76ba8) at soup-connection.c:615
get_connection (should_cleanup=0x0, item=0x7f383c0042b0) at soup-session.c:1878
soup_session_process_queue_item (session=session@entry=0x7f38a2907460, item=item@entry=0x7f383c0042b0, should_cleanup=should_cleanup@entry=0x0, loop=loop@entry=1) at soup-session.c:1899

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2014-09-16: Stacktrace.txt

#3

Stacktrace.txt Edit (4.0 KiB, text/plain)

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2014-09-16: StacktraceSource.txt

#4

StacktraceSource.txt Edit (4.8 KiB, text/plain)

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2014-09-16: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (27.9 KiB, text/plain)

tags:

removed: need-amd64-retrace

Cristian Aravena Romero (caravena) on 2014-09-16

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1370750

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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