Description of problem: After upgrading from fc18 to fc20, started evolution in mate, and it crashed without even showing any GUI. Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: WebCore::DOMWindow::finishedLoading executable: /usr/bin/evolution kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 WebCore::DOMWindow::finishedLoading at Source/WebCore/page/DOMWindow.cpp:1773 #1 WebCore::DocumentLoader::mainReceivedError at Source/WebCore/loader/DocumentLoader.cpp:241 #2 WebCore::DocumentLoader::cancelMainResourceLoad at Source/WebCore/loader/DocumentLoader.cpp:1437 #3 WebCore::DocumentLoader::stopLoading at Source/WebCore/loader/DocumentLoader.cpp:297 #4 WebCore::FrameLoader::stopAllLoaders at Source/WebCore/loader/FrameLoader.cpp:1579 #5 WebCore::FrameLoader::continueLoadAfterNavigationPolicy at Source/WebCore/loader/FrameLoader.cpp:2855 #6 WebCore::FrameLoader::callContinueLoadAfterNavigationPolicy at Source/WebCore/loader/FrameLoader.cpp:2713 #7 WebCore::PolicyCallback::call at Source/WebCore/loader/PolicyCallback.cpp:103 #8 WebCore::PolicyChecker::continueAfterNavigationPolicy at Source/WebCore/loader/PolicyChecker.cpp:180 #9 WebKit::FrameLoaderClient::dispatchDecidePolicyForNavigationAction at Source/WebKit/gtk/WebCoreSupport/FrameLoaderClientGtk.cpp:486
Created attachment 892269 [details] File: backtrace
Created attachment 892270 [details] File: cgroup
Created attachment 892271 [details] File: core_backtrace
Created attachment 892272 [details] File: dso_list
Created attachment 892273 [details] File: environ
Created attachment 892274 [details] File: exploitable
Created attachment 892275 [details] File: limits
Created attachment 892276 [details] File: maps
Created attachment 892277 [details] File: open_fds
Created attachment 892278 [details] File: proc_pid_status
Created attachment 892279 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that this crashes in a WebKitGTK3 code, but I cannot tell why for sure. Does this crash every time you run evolution? What if you run evolution from a terminal like this: $ evolution -c mail or like this: $ evolution -c mail --disable-preview ? It seems that the crash happens in the Calendar view, and is somehow connected to the preview of the message, thus running in the mail view, and eventually disabling the preview, may show us whether my aim is correct. To run evolution in the Calendar view just invoke: $ evolution -c calendar Could you also try to downgrade webkitgtk3, please? I use webkitgtk3-2.2.5-1.fc20.x86_64, which doesn't have any issue. It is also possible that the crash is related to certain message, the webkit crashes when it is selected and shown in the message preview. It would be good to verify that as well. If you manage to run evolution with --disable-preview, then the selected message should be the one which was loaded into the preview the last time.
Dear Milan, I have tried all but the downgrade option of your comment #12, all with the same results, seg faults for all! Next, I tried them in Gnome instead of Mate, with the same results, but, the ps command reports that: 833 ? SLl 0:00 /usr/libexec/evolution-source-registry 925 ? Sl 0:01 /usr/libexec/evolution-calendar-factory 957 ? Sl 0:00 /usr/libexec/evolution/3.10/evolution-alarm-notify 1218 ? Sl 0:00 /usr/libexec/evolution-addressbook-factory 23270 pts/0 S+ 0:00 grep --color=auto evolution but again, seg faults even with the disable-preview! Now, I shall try the downgrade option. Thanks for your comeback and info, YBnawtbug
Milan, Back again to report that I did't downgrade as I found that I would have to go to version 2.2.2-2, so instead, I upgraded via updates-testing to webkitgtk3 (and related packages) version 2.2.7-1 as it was a bugfix update. This did not help any, as it is still seg faulting, and trying to have abrt send out another report. Next, I think I shall try the remove home folder prefs and cache folders after a little research, so as to have it evolution startup on a clean plate, as my thinking is that it might be crashing on bad user data, but not telling me about it. Thanks again, YBnawtbug
Created attachment 893047 [details] CAMEL_DEBUG=all evolution Debug output file, since error shows up after looking through db, seems evolution is having trouble since trash and spam folders are not there.
Sorry, should be trash and junk folders not there. I think this db corruption may stem from yahoo and its lack of proper dealing with linux software, due to the heartbleed scare, and system hacks to yahoo, or changes in how it deals with mail since it introduced new mail ui not so long ago -- just a bit of speculation on my part here. Thanks, YBnawtbug
Some additional info: I just now created a new user and found that evolution does work! I also found that it seems that yahoo no longer does imap (as this way didn't work), but, when the account was setup for 'pop', it worked and downloaded a copy of the over 1200 e-mail there (which took a while). So now, I am left to figure a work around this so that my main users evolution also works, probably by cuting out the bad db files, and then, when the interface returns, fixing my yahoo to the proper 'pop' address (yes, I could not use the yahoo account e-mail for a couple of months or so now before I upgraded last week, not knowing as to why, and so had to use a web browser interface, and not on firefox, because yahoo distrusts it, but finally got qupzilla to work for the e-mail. Now, after the upgrade, firefox works for the e-mail, but not for the home page of yahoo, maybe due to cross scripting, or due to my foss java not being trusted by yahoo? I know not, but these are separate issues I think). Any help in the matter would be greatly appreciated in the work around of this situation, so thanks in advance, YBnawtbug
OK, there are too many things mentioned here. I'll surely miss some of them, but anyway: - I use Yahoo! account on my computer, I connect to it through IMAP, and it works. It has some early quits by the server, but that's nothing crucial, because it does that only if the account is IDLE for "long enough". Using POP3 for Yahoo! is also fine. I had never issue to login to web interface of Yahoo! mail using Firefox. I suspect they do not like something about your internet provider or just about some setting. Who knows. I'd rather not blindly guess. - If a new user account works as expected, then it can surely be something with either internal evolution data, or some browser plugin doing nasty things during initialization (evolution disables all plugins on start, but the plugins are initialized regardless, which is not ideal, but it's the way it works). Please see bug #1083306 comment #13 for places where browser plugins can be stored, I'd focus on the user's folders, than on those system wide. Try to cleanup those folders and see what will happen. - With respect of local cache, you can safely drop ~/.cache/evolution/mail/ directory, it will be recreated and repopulated on demand. The only counter-side is that the folder's summary will be redownloaded, which can take its time, depending on the folder/account sizes. - The camel debug log is cut, unfortunately, somewhere in time of initialization, slightly before the crash. Tomas, as this is crashing in webkit, maybe you'll have some idea where to look or what could cause the problem.
To all whom this may concern, I did another command in an effort to see what webkitgtk3 might be doing to my evolution, and in the process created another bug! Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1095461 for more info. Basically, I ran an exec of webkitgtk3's GtkLauncher. I hope this helps. Thanks, YBnawtbug
Hooray or Hurray! I figured it out! OK, in the course of testing, I disabled the mozplugger plugin, and found that I did need it so as to play midi files, so, I got to thinking, that maybe the webkitgtk3 problem had to do with the way my local plugin folder was set up, as I had to link the /usr/lib64/mozilla/plugins/ directory to my .mozilla/plugins forlder so that my manually upgraded firefox (as many sites would not serve my 'old' firefox of fc18 as I could not upgrade due to space constraints, that I solved using my new 2T drive purchased with fed tax refund money) as well as locally upgraded firefox could acess all the plugins. So, on a hunch, I moved the local plugins directory to old, made a new empty .mozilla/plugins, then started evolution, and, it worked! Next, I turned my attn to the fact that my inbox did not work, at least from yahoo, and I found that the other folders on my yahoo account did work, but I realized that imap and my large amount of e-mail in my inbox were probably to blame, so, I made a new account on evolution, disabling the old, and made sure it was 'pop', and it worked, taking about 5mins to download (whereas in imap version, nothing happened no mater what I tried, just folders like bulk would show what was there, and downloading would occur when opened, etc.). So, it seems to me that webkitgtk3 had trouble with the mirrored effect of the plugins dirs, if I were to make a guess-timation. That is about all, Thanks again one and all, and thanks for the needed info Milan! Ybnawtbug
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.