GNOME Bugzilla – Bug 726169
Text of feeds doesn't present
Last modified: 2021-05-25 12:36:26 UTC
Created attachment 271593 [details] Buggy screen Version of component: evolution-rss-0.3.94-6.fc21.x86_64 Steps to reproduce: 1. Open evolution 2. Open feeds list 3. Open feed Actual results: (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_data_wrapper_decode_to_output_stream_sync: assertion 'G_IS_OUTPUT_STREAM (output_stream)' failed (evolution:15499): GLib-GIO-CRITICAL **: g_output_stream_flush: assertion 'G_IS_OUTPUT_STREAM (stream)' failed (evolution:15499): evolution-module-rss-CRITICAL **: parse_html_sux: assertion 'buf != NULL' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_data_wrapper_decode_to_output_stream_sync: assertion 'G_IS_OUTPUT_STREAM (output_stream)' failed (evolution:15499): GLib-GIO-CRITICAL **: g_output_stream_flush: assertion 'G_IS_OUTPUT_STREAM (stream)' failed (evolution:15499): evolution-module-rss-CRITICAL **: parse_html_sux: assertion 'buf != NULL' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed (evolution:15499): camel-CRITICAL **: camel_stream_write_string: assertion 'CAMEL_IS_STREAM (stream)' failed and see screenshot Expected results: article shows fine
Created attachment 271596 [details] Screenshot of the problem Hello, For my part, after patching evolution-rss sources with the patches proposed in #720459 and then running evolution-rss-0.3.94-1.fc20.x86_64 patched, the only message I can see while loading evolution from a user console is: (evolution:12185): libebackend-WARNING **: module_load: /usr/lib64/evolution/3.10/modules/evolution-module-rss.so: undefined symbol: em_folder_tree_set_selected Failed to load module: /usr/lib64/evolution/3.10/modules/evolution-module-rss.so But the real problem is that no feeds are displayed in evolution. To complete the above description, and for my part with Fedora 20, I can see the two buttons showing an attachment (one to save it and one to show it), but as the attachment part of the message is seen as .dat file, it doesn't show itself correctly in evolution (see screenshot attached). Hope this explanation will help to catch this issue. Cordially, -- NVieville
Already fixed in: https://git.gnome.org/browse/evolution-rss/commit/?id=7600f67649f3f25cc4bae9e132517c9ab63b54b5
Sorry for that, but after applying the patch cited above and rebuilding the Fedora 20 package, no amelioration for me :-( Evolution stills show feeds as attachment with .dat extensions, but doesn't display them as it should using one of the HTML renderer chosen in the evolution-rss plugin settings. Cordially, -- NVieville
Yeah. Problem not in this errors. I'm wrong in first comment. Bug still present.
Hello, Sorry for that bump, but any news about this problem? Still got HTML pages not rendered in evolution interface from rss folder (called on my Fedora 20 "News and Blogs"). Hope it will be possible to catch this issue. Cordially, -- NVieville
I have the same problem in current Debian Jessie. Any news for this?
Hello, Sorry for that bump, but any news about this problem? Problem remains as it was in my previous message. Cordially, -- NVieville
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution-rss/-/issues/ Thank you for your understanding and your help.