Hide Forgot
Description of problem: liferea recently started crashing any time I select an article originating from the Slashdot RSS feed. Version-Release number of selected component (if applicable): liferea-1.6.5-1.fc13.x86_64 libsoup-2.30.1-1.fc13.x86_64 How reproducible: Completely reproducible. I am unable to read any Slashdot article in liferea. The article is rendered, then liferea crashes immediately. Steps to Reproduce: 1. Add the Slashdot RSS feed 2. Wait for liferea to check, or force-update 3. Select a Slashdot article Actual results: A render followed by a crash Expected results: I should be able to actually read the Slashdot article and not have liferea crash. Additional info: When executing liferea from the terminal, I see the following messages: [klmitch@tesla ~]$ liferea (liferea:17289): libsoup-CRITICAL **: soup_cookie_domain_matches: assertion `host != NULL' failed (liferea:17289): libsoup-CRITICAL **: soup_cookie_domain_matches: assertion `host != NULL' failed (liferea:17289): libsoup-CRITICAL **: soup_cookie_domain_matches: assertion `host != NULL' failed Liferea did receive signal 11 (Segmentation fault). Note that no core is dumped, despite the fact that I have core dump size unlimited--I use this platform for development. Also, running abrt-gui lists no cores for liferea.
Same here, liferea crashing on Slashdot RSS rendering; same symptoms and settings. Crashes started to occur right after a yum update which installed webkitgtk-1.2.6-1.fc13.x86_64 Downgrading to webkitgtk-1.2.0-1.fc13.x86_64 solves the problem. There is currently a webkitgtk-1.2.6-2.fc13 in testing, which reportedly fixes a regression addressed in bugzilla #670142 https://admin.fedoraproject.org/updates/webkitgtk-1.2.6-2.fc13?_csrf_token=ed5f931102178bc63158aeba771efd825c8bef4b Updating to webkitgtk-1.2.6-2.fc13.x86_64 also resolves the crashing, but still has the libsoup-CRITICAL assertions flooding .xsession-errors, and the rendering of the slashdot comments section fails to complete: only the text is rendered and most of the graphical elements are missing.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.