Hide Forgot
Description of problem: Using Evolution (3.10.2) with evolution-rss plugin (0.3.94) in Fedora 20 (Mate desktop) 1. Open Evolution (with previously imported rss feeds). 2. Open "Edit" -> "Preferences" -> "News and Blogs" ("Feeds" tab). 3. Click on enabled feed and then click "Edit". 4. Click on "Location" selector, window opens allowing to choose different folder. 5. In the window opened above, select another folder, previously created under "News and Blogs" in main Evolution window. 6. Evolution crashes, depending on feed (not every feed does that). So far, I haven't determined why moving certain feeds crashes Evolution and why certain do not. Version-Release number of selected component: evolution-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: evolution crash_function: g_type_check_instance_cast executable: /usr/bin/evolution kernel: 3.11.10-300.fc20.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4008 #1 rss_emfu_copy_folder_selected at rss-evo-common.c:118 #2 folder_cb at rss-config-factory.c:631 #3 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115 #4 _g_closure_invoke_va at gclosure.c:840 #7 gtk_button_clicked at /lib/libgtk-3.so.0 #8 gtk_real_button_released at /lib/libgtk-3.so.0 #9 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115 #10 g_type_class_meta_marshalv at gclosure.c:997 #11 _g_closure_invoke_va at gclosure.c:840 Potential duplicate: bug 891718
Created attachment 834408 [details] File: backtrace
Created attachment 834409 [details] File: cgroup
Created attachment 834410 [details] File: core_backtrace
Created attachment 834411 [details] File: dso_list
Created attachment 834412 [details] File: environ
Created attachment 834413 [details] File: exploitable
Created attachment 834414 [details] File: limits
Created attachment 834415 [details] File: maps
Created attachment 834416 [details] File: open_fds
Created attachment 834417 [details] File: proc_pid_status
Created attachment 834418 [details] File: var_log_messages
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.