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 696881 - Crash on mail migration
Summary: Crash on mail migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.2
Hardware: i686
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 700212
TreeView+ depends on / blocked
 
Reported: 2011-04-15 07:03 UTC by Siddharth
Modified: 2018-11-14 13:02 UTC (History)
5 users (show)

Fixed In Version: evolution-2.28.3-24.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 700212 (view as bug list)
Environment:
Last Closed: 2011-05-19 14:09:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Backtrace, Dissassembly (89.59 KB, text/plain)
2011-04-15 07:08 UTC, Siddharth 		no flags Details
abrt.log (189.23 KB, text/plain)
2011-04-27 15:45 UTC, Jiri Koten 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 597082 0 None None None Never
Red Hat Product Errata RHBA-2011:0714 0 normal SHIPPED_LIVE evolution bug fix update 2011-05-18 18:09:51 UTC

Description Siddharth 2011-04-15 07:03:14 UTC 
Description of problem:
abrt version: 1.1.13
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.32-71.el6.i686
rating: 0
reason: Process /usr/bin/evolution was killed by signal 8 (SIGFPE)
time: 1302795629
uid: 215


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Workstation release 6.0 (Santiago)
evolution-2.28.3-10.el6
architecture: i686

How reproducible:
random crash

Steps to Reproduce:
1.Backup client evolution settings on RHEL5.6 Workstation
2.Open evolution on newly installed RHEL6, and perform a restore operation for evolution-backup.tar.gz created in step #1
3.Evolution crashes
  
Actual results:
evolution crashed.

Expected results:
evolution should not crashed.

Additional info:
Comment 1 Siddharth 2011-04-15 07:08:37 UTC 
Created attachment 492290 [details]
Backtrace, Dissassembly
Comment 4 Milan Crha 2011-04-18 06:42:00 UTC 
Thanks for a bug report. This seems to be an upstream bug [1], which was fixed by a commit [2], thus a patch exists for it.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=597082
[2] http://git.gnome.org/browse/evolution/commit?id=b76e7f143
Comment 7 Milan Crha 2011-04-19 16:11:55 UTC 
Here [1] is a test package. I'm not sure if it's not in too much hurry, (I know I asked for a devel ack just recently, but I didn't plan to change my mind). It would be good to have the package tested, as the crash depends on actual data being migrated (even after the backup restore), and there is too little time to achieve that, I'm afraid.

[1] https://brewweb.devel.redhat.com/taskinfo?taskID=3268541
Comment 12 Matthew Barnes 2011-04-20 19:25:59 UTC 
Testing this should just be a matter of setting up some kind of IMAP account on RHEL 5, letting Evolution download summary info for your mail folders so it has data to migrate, and then upgrading to RHEL 6 and running Evolution.  If you have a Zimbra IMAP account with a fair amount of content, that should work.

The crash is due to thread-safety issues in the migration dialog's progress bar, so the mail content itself shouldn't matter.  Just so there's enough stuff there to migrate that you can watch the progress bar make progress.
Comment 14 Jiri Koten 2011-04-27 15:33:31 UTC 
Crash happens in evolution-2.28.3-23.el6 when "Migrating folders" window appears.

In old package evolution-2.28.3-22.el6 after crash happened during migration, evolution started successfully and settings were migrated. 

With new package crash happens all the time, evolution won't start after crash during migration.
Comment 15 Jiri Koten 2011-04-27 15:45:30 UTC 
Created attachment 495278 [details]
abrt.log

abrt.log with backtrace.
Comment 16 Matthew Barnes 2011-04-27 18:32:11 UTC 
I see what's going on.  The idle callback update_states_in_main_thread() is running the main loop before returning, but the idle source is still registered with the main loop, so the callback is being called recursively and freeing the same memory over and over until it crashes.
Comment 21 errata-xmlrpc 2011-05-19 14:09:02 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0714.html
Note You need to log in before you can comment on or make changes to this bug.