Red Hat Bugzilla – Bug 1291011
[abrt] evolution: camel_folder_change_info_free(): evolution killed by SIGSEGV
Last modified: 2016-12-20 11:57:48 EST
Description of problem:
i've added the Evolution rss addon from GNOME Software and after adding an rss feed through the newly added rss entry in the Evolution's options screen i launched the newly added Evolution rss app entry from the app picker and Evolution crashed
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (3 frames)
#0 camel_folder_change_info_free at camel-folder.c:4545
#1 folder_emit_changed_cb at camel-folder.c:187
#6 gtk_main at gtkmain.c:1241
Created attachment 1105119 [details]
Created attachment 1105120 [details]
Created attachment 1105121 [details]
Created attachment 1105122 [details]
Created attachment 1105123 [details]
Created attachment 1105124 [details]
Created attachment 1105125 [details]
Created attachment 1105126 [details]
Created attachment 1105127 [details]
Created attachment 1105128 [details]
Created attachment 1105129 [details]
Created attachment 1105130 [details]
Created attachment 1105131 [details]
Thanks for a bug report. This is new to me. I thought it is related to a known issue of the evolution-data-server unreffing message infos multiple times in an IMAPx code, more than it should, which caused memory corruption, but you have installed fixed evolution-data-server, thus it's not it (even it's in IMAPx code, it could strike back anywhere).
I'm moving this to the evolution-rss for further investigation. Its version is evolution-rss-1:0.3.95-4.fc23.x86_64, according to dso_list.
I forgot to add, it would be eventually helpful if you could reproduce the crash under valgrind, if it's reproducible at all, to see whether it'll claim anything useful. The valgrind command looks like:
$ G_SLICE=always-malloc valgrind evolution &>log.txt
Make sure you've installed debuginfo packages for any evolution* package  of the same version as the binary package, thus the valgrind log contains proper information. Also note that the valgrind can log about certain issues and keep the application running, thus even if the evolution run under valgrind will not crash the log can still contain valuable information. Evolution will be very slow under valgrind, due to all the memory checking.
 $ rpm -qa | grep evolution
After reporting the bug i've deinstalled the Evolution RSS package and instead installed the Liferea application for reading RSS feeds.
However after reading your reply i reinstalled the Evolution RSS package out of curiosity and i was able to reproduce the crash and i will tell you exactly how since i failed to mention a step which now i'm certain that it is the one that triggers the crash.
Alright now here is how it goes
1: Launch "Evolution RSS"
3: "News and Blogs" Entry
4: Tab--"Feeds" Add what ever news feed
Note: Step "5" is going to trigger the bug
5: Tab--"Setup" then check mark "Check for new articles at startup" and finally press the bottom close button.
And it seems that this can be done only once per "Evolution RSS" installation.
Thank you for your time.
just wanted to add that i found that the evolution rss addon does make evolution unstable in general and that i am going to remove the rss addon.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.