GNOME Bugzilla – Bug 626117
crash in imapx_command_sync_changes_done
Last modified: 2010-10-01 12:44:02 UTC
Using gnome-2-30:
+ Trace 223119
Thread 1 (Thread 30999)
Bugzilla thinks this is a duplicate of bug 620023, FWIW.
Thanks for a bug report. It seems to me that the source code lines are somehow shifted, because my latest checkout of gnome-2-30 branch of evolution-data-server doesn't have line 4069 inside imapx_command_sync_changes_done. Is it possible you've there some patch applied, which shifts lines? Nonetheless, there is not planned any update for 2.30 as of now, and the branch master contains quite many fixes in the whole imapx code, thus I would suggest to move to it.
(In reply to comment #2) > Thanks for a bug report. It seems to me that the source code lines are somehow > shifted, because my latest checkout of gnome-2-30 branch of > evolution-data-server doesn't have line 4069 inside > imapx_command_sync_changes_done. Hrm. Strange. Mine is the same, and it's the source that the crash should have come from. Although, the report is now a month old, so my source might have been updated since then. I currently have: 4065: ic->pri = job->pri; 4066: ic->job = job; 4067: ic->complete = imapx_command_subscription_done; 4068: imapx_command_queue(is, ic); 4069: 4070: g_free (encoded_fname); 4071:} > Is it possible you've there some patch > applied, which shifts lines? I don't think I have any imapx patches at the moment. > Nonetheless, there is not planned any update for 2.30 as of now, and the branch > master contains quite many fixes in the whole imapx code, thus I would suggest > to move to it. Is master stable enough yet? Is it nearing branching for gnome-2-32?
Heh, bad line numbers. :) There is a new branch gnome-2-32 created just recently, which is under hard code freeze till the upcoming 2.32.0 release. If you build yourself, then you probably can safely switch to it. The only trouble is a requirement for recent glib, but gtk can be 2.20.x with no issue.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 618845 ***