Bug 621296

Summary: Crash detected in evolution-data-server-2.28.3-9.el6.x86_64
Product: Red Hat Enterprise Linux 6 Reporter: Jay Turner <jturner>
Component: dbusAssignee: Colin Walters <walters>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: cmeadors, sdodson, srevivo, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-25 11:09:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Backtrace none

Description Jay Turner 2010-08-04 17:41:24 UTC 
Description of problem:
Got the following crash this morning on boot.  

architecture: x86_64
cmdline: /usr/libexec/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=33
component: evolution-data-server
executable: /usr/libexec/evolution-data-server-2.28
kernel: 2.6.32-57.el6.x86_64
package: evolution-data-server-2.28.3-9.el6
rating: 0
reason: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
sosreport.tar.xz: /var/spool/abrt/ccpp-1280928689-11491/sosreport.tar.xz
time: 1280928689
uid: 500


Version-Release number of selected component (if applicable):
2.28.3-9.el6

How reproducible:
There are reports this can be reproduced simply by switching from wired -> wireless networking

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Matthew Barnes 2010-08-04 19:45:33 UTC 
Need a backtrace with debugging symbols please.
Comment 5 Scott Dodson 2011-03-01 15:33:04 UTC 
Created attachment 481658 [details]
Backtrace

I get this crash periodically when I try to open the gnome clock applet. I have no idea if this is the same thing, but given that there's no backtrace in this bug so far and my backtrace at least matches the cmdline and exit code I figure there's no harm in attaching this to this bug.