RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 595502 - [abrt] evolution-data-server-2.28.3-4.el6: __pthread_mutex_lock: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.28.3-4.el6: __pthread_mutex_lock: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 592004
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-data-server
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard: abrt_hash:a716c27ae16a1bb26b9e6402bbf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-24 20:12 UTC by Marc Milgram
Modified: 2010-06-14 09:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-14 09:40:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.65 KB, text/plain)
2010-05-24 20:12 UTC, Marc Milgram
no flags Details

Description Marc Milgram 2010-05-24 20:12:28 UTC
abrt version: 1.1.2
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck --oaf-ior-fd=28
component: evolution-data-server
crash_function: __pthread_mutex_lock
executable: /usr/libexec/evolution-data-server-2.28
global_uuid: a716c27ae16a1bb26b9e6402bbf9ebcdb6f33189
kernel: 2.6.32-28.el6.x86_64
package: evolution-data-server-2.28.3-4.el6
rating: 4
reason: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)

comment
-----
Evolution data server crashes on my system several times per day.
I installed my system with 6.0 Beta (nightly), but am using /home
from RHEL 5.5.

How to reproduce
-----
1. Run Evolution
2.  View calendar (?)
3. View email (?)
4. Wait several hours

Comment 1 Marc Milgram 2010-05-24 20:12:30 UTC
Created attachment 416216 [details]
File: backtrace

Comment 3 RHEL Program Management 2010-06-07 16:04:11 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Matthew Barnes 2010-06-12 20:41:24 UTC
Conditional NAK -- Steps to reproduce the crash are circumstantial.  Need
repeatable steps for QA to follow to prove whether the cause of the crash is
fixed.

Comment 5 Milan Crha 2010-06-14 09:40:19 UTC

*** This bug has been marked as a duplicate of bug 592004 ***


Note You need to log in before you can comment on or make changes to this bug.