Description of problem:
Seemed to occur when reporting spam with evolution-rspam.
Version-Release number of selected component:
Thread no. 1 (10 frames)
#2 g_settings_schema_get_value at gsettingsschema.c:640
#3 g_settings_schema_key_init at gsettingsschema.c:751
#4 g_settings_get_value at gsettings.c:1079
#5 g_settings_get_boolean at gsettings.c:1785
#6 org_gnome_sa_rspam at rspam.c:912
#11 _gtk_action_emit_activate at gtkaction.c:801
#21 gtk_widget_activate at gtkwidget.c:6332
#22 gtk_menu_shell_activate_item at gtkmenushell.c:1429
#23 gtk_menu_shell_button_release at gtkmenushell.c:830
#24 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
Created attachment 662954 [details]
Created attachment 662955 [details]
Created attachment 662956 [details]
Created attachment 662957 [details]
Created attachment 662958 [details]
Created attachment 662959 [details]
Created attachment 662960 [details]
Created attachment 662961 [details]
Created attachment 662962 [details]
Created attachment 662963 [details]
Created attachment 662964 [details]
Thanks for a bug report. Your comment is correct. Evolution crashes in evolution-rspam code. It claims:
> Settings schema 'org.gnome.evolution.plugin.rss' does not contain
> a key named 'move-junk'
I'm moving this to evolution-rspam.
Crash on startup.
OS Release: Fedora release 18 (Spherical Cow)
could you check bug #887246 , have something similar
There is used both
which seem to have the same GSettings *setting; defined as a global non-static variable, thus I guess what happened here:
> > Settings schema 'org.gnome.evolution.plugin.rss' does not contain
> > a key named 'move-junk'
is that the 'settings' variable from evolution-rss plugin was picked instead of the one in evolution-rspam. Defining them 'static' may help to prevent of this in the future.
I moved this upstream , to evolution-rss' bugzilla. Please see  for any further updates. I'll provide an interim workaround for Fedora too.
evolution-rss-0.3.92-2.fc18,evolution-rspam-0.6.0-3.fc18 has been submitted as an update for Fedora 18.
evolution-rss-0.3.93-3.fc19,evolution-rspam-0.6.0-5.fc19 has been submitted as an update for Fedora 19.
evolution-rss-0.3.93-3.fc19, evolution-rspam-0.6.0-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
evolution-rss-0.3.92-2.fc18, evolution-rspam-0.6.0-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.