Hide Forgot
Description of problem: architecture: x86_64 Attached file: backtrace cmdline: evolution --sm-config-prefix /evolution-NrVnKg/ --sm-client-id 108f8bcee7695d03c129168733751575500000021860026 --screen 0 component: evolution crash_function: g_slice_alloc executable: /usr/bin/evolution Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) Version-Release number of selected component (if applicable): evolution-2.28.3-10.el6 Red Hat Enterprise Linux Workstation release 6.0 (Santiago) How reproducible: random crash Steps to Reproduce: 1. open new message from file menu, blank message stays open 2. return to a mail folder, open an email, and click on the sender's address to create a new email 3. crash Actual results: evolution crashed. Expected results: evolution not crashed. Additional info: customer comment In RHEL 5 I copied email files to a backup, installed RHEL6 and copied the backup files to the .evolution directory. This did not restore evolution because of changes between RHEL5 and RHEL6. After some corrections (calendar), the address book is still not fully functional. The main list of address contains only addresses added after switch to RHEL6, but the categories contain all the correct addresses. In addition, I have fat fingered the email folders so that I have 2 inboxes. The topmost inbox has a small green arrow, which I think indicates that it is an alias. The other (original I think) inbox is now lower case.
Thanks for a bug report. I tried to reproduce it with the same version as you, but no luck, it doesn't crash for me. Are you able to reproduce this consistently, please? If yes, could you try to reproduce it under valgrind, to see whether it'll show us where the memory got corrupted/freed, please? You can run evolution like this: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>vg.txt and then reproduce the issue. The only thing is that evolution will be significantly slower, due to valgrind memory checks. Please attach here the vg.txt file to see whether it'll exhibit any useful information, even if it'll not crash, because valgrind can avoid the crash and print error log into the file only. Thanks in advance.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Created attachment 521145 [details] valgrind
I have attached valgrind of evolution crash. I tried to analyse the crash but I did not get how to dig into it.
Thanks for the update. The valgrind log hows many usages of uninitialized memory, but other than that nothing. I suppose the critical warning is close related to it. > (evolution:19523): evolution-shell-WARNING **: Did not receive a reply. > Possible causes include: the remote application did not send a reply, the > message bus security policy blocked the reply, the reply timeout expired, > or the network connection was broken. To find out which calendar this is coming from, could you disable the MAPI account in Edit->Preferences->Mail Accounts, quit Evolution, stop/kill evolution-data-server-2.28 process and run evolution again, whether it'll crash too, and the best whether it'll claim same critical warning on the console, please? It seems to me that there is some issue when it tries to create the GnomeCalendar component, it seems to fail for some reason. When you run evolution, is it starting in calendar? Because the valgrind log is all about calendar, whereas your steps mentions email only. Also, I do not see a crash notice in the valgrind log, it seems like evolution being closed correctly.
Customer comment .... I disabled my primary (only) email account, quit evolution, used the command prompt> evolution --force-shutdown Shutting down evolution-data-server-2.28 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) And then restarted evolution from the Gnome applications panel (top bar). Evolution started without problem, my account was still disabled (I re-enabled it), and evolution retrieved mail normally. Calendar and contacts both work (without attempting modification). In the sporadic crashes I reported below, there were no error messages, and in particular no attempt to report a bug. He tested evolution as you suggested and it running normally without crash. The crash happen due to some calender problem.
I tried to reproduce the crash with no luck on my machine, but I was able to reproduce the valgrind issues, to which I attached patch into bug #735674 comment #13 (I got it reproduced while I was testing the other bug report).
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.