Version-Release number of selected component:
runlevel: N 5
Created attachment 1517771 [details]
Created attachment 1517772 [details]
Created attachment 1517773 [details]
Created attachment 1517774 [details]
Created attachment 1517775 [details]
Created attachment 1517776 [details]
Created attachment 1517777 [details]
Created attachment 1517778 [details]
Created attachment 1517779 [details]
Created attachment 1517780 [details]
Created attachment 1517781 [details]
Thanks for a bug report. The reason for the crash, according to the backtrace, is:
"Settings schema 'org.gnome.evolution.calendar' is not installed"
which is quite weird, because evolution-alarm-notify is part of the 'evolution-data-server' package in 3.30.x, but the backtrace claims that the binary is from the evolution package, while ABRT sees this as evolution-data-server package. I suspect there happened something during the update process (like from pre-Fedora 29 to Fedora 29 version), is it possible?
I also checked the sources and nothing references "org.gnome.evolution.calendar" in evolution-data-server, which kind of supports the above paragraph.
If this is related to an update, how did you update the machine, please?
Is the evolution package installed at all, please? (rpm -qa | grep evolution).
I replaced my hard drive.
Backed up the old drive to an external one via rsynch
Put in the new drive
Installed F29 from the Live DVD
Restored everything from the external drive via rsynch (except /boot)
I've just done "dnf reinstall evolution-data-server". Let's see how it goes.
I would try also with `dnf distro-sync`, which might not be exactly the same as reinstall though. The thing is that the rsync could mix different bits together. Like you might have two different evolution-alarm-notify processes now, if the rsync works with the files, not with the path (the path for the process changed as well). Safer would be to use rsync and only then update to a newer Fedora.
To test the change, it's enough to run the process either from
/usr/libexec/evolution/evolution-alarm-notify (it's the wrong location)
/usr/libexec/evolution-data-server/evolution-alarm-notify (it's the correct location).
Either it will claim the missing scheme file immediately, or it'll run.
*** Bug 1704437 has been marked as a duplicate of this bug. ***
The bug #1704437 is very similar, only from evolution-calendar-factory, with no rsync involved. I suspect that GSettings has cached list of schemas and if there are added new schemas while the pplication is running then it doesn't refresh the list, thus when something references that new schema, then GSettings aborts the application, because it doesn't know about this new schema. That's only an idea. If true, then restarting the background process would lead to no crash, the application should run as expected.
*** Bug 1750282 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.
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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.