evolution crashed with SIGSEGV

Bug #872944 reported by Ryan Jonathon Rahebi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

lol idk uh.....ur the expert lol i just work here :p

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Wed Oct 12 10:55:15 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f9d656363f0: add %cl,-0x7d(%rax)
 PC (0x7f9d656363f0) ok
 source "%cl" ok
 destination "-0x7d(%rax)" (0xffffffffffffff83) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libcairo.so.2
 ?? ()
Title: evolution crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-10-12 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ryan Jonathon Rahebi (rrahebi) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_arg_class_cb (key=<optimized out>, value=<optimized out>, user_data=<optimized out>, error=<optimized out>) at /build/buildd/gtk+2.0-2.24.4/gdk/gdk.c:139
 _cairo_user_data_array_set_data (array=0x246eb20, key=0x0, user_data=0x0, destroy=<optimized out>) at /build/buildd/cairo-1.10.2/src/cairo-array.c:487
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
security vulnerability: yes → no
security vulnerability: yes → no
visibility: private → public
visibility: private → public
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

11.04 is not longer supported
change status to invalid

Changed in evolution (Ubuntu):
status: New → Invalid
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.