Ubuntu
evolution package

evolution crashed with SIGSEGV in gtk_style_context_get_style_valist()

Bug #1116051 reported by Jens Kehne on 2013-02-05

50

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	evolution (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Evolution froze while downloading contacts from a CardDAV-Server. When I closed the evolution window, apport popped up with this report.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution 3.6.2-0ubuntu0.1
Uname: Linux 3.7.6-zen+ x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 5 09:34:47 2013
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2012-06-05 (244 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: evolution
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/usr/bin/fish
SegvAnalysis:
Segfault happened at: 0x7f06121d71c7 <gtk_style_context_get_valist+215>: mov 0x30(%rax),%rdx
PC (0x7f06121d71c7) ok
source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
Stacktrace:
#0 0x00007f06121d71c7 in gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
Cannot access memory at address 0x7fff94f1a058
StacktraceTop: gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: evolution crashed with SIGSEGV in gtk_style_context_get_valist()
UpgradeStatus: Upgraded to quantal on 2012-10-19 (108 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark

Tags:

Revision history for this message

Jens Kehne (jkehne) wrote on 2013-02-05:

#1

Dependencies.txt Edit (9.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (146.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (915 bytes, text/plain; charset="utf-8")
Registers.txt Edit (804 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (17.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (2.5 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-06:

#2

StacktraceSource:
#0 0x00007f06121d71c7 in gtk_style_context_get_style_valist (context=0x7fff94f1a068, context@entry=<error reading variable: Cannot access memory at address 0x7fff94f1a048>, args=0x7f0612391078, args@entry=<error reading variable: Cannot access memory at address 0x7fff94f1a048>) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkstylecontext.c:2444
[Error: /build/buildd/gtk+3.0-3.6.0/./gtk/gtkstylecontext.c was not found in source tree]
StacktraceTop: gtk_style_context_get_style_valist (context=0x7fff94f1a068, context@entry=<error reading variable: Cannot access memory at address 0x7fff94f1a048>, args=0x7f0612391078, args@entry=<error reading variable: Cannot access memory at address 0x7fff94f1a048>) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkstylecontext.c:2444

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-06: Stacktrace.txt

#3

Stacktrace.txt Edit (590 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-03-06: ThreadStacktrace.txt

#4

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

Changed in evolution (Ubuntu):
importance:	Undecided → Medium
summary:	- evolution crashed with SIGSEGV in gtk_style_context_get_valist() + evolution crashed with SIGSEGV in gtk_style_context_get_style_valist()
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-03-22:

#5

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

Changed in evolution (Ubuntu):
status:	New → Confirmed

Revision history for this message

schollsky (schollsky) wrote on 2013-04-09:

#6

Crash of evolution on shutdown here, too. As a result more than the last half of my personal addressbook entries went invisible after next start. Luckily, they reappeard after another restart.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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