On Wed, 2019-02-20 at 11:23 +0100, Helmut Bardeli wrote:
> Thread 1 "evolution" received signal SIGSEGV, Segmentation fault.
> dconf_engine_manage_queue (engine=0x555555805d80) at dconf-
> engine.c:1078
> 1078 engine->sources[0]->object_path,
> (gdb) bt full
> #0 0x00007fffda226c5d in dconf_engine_manage_queue
> (engine=0x555555805d80) at dconf-engine.c:1078
> oc = 0x55555611cc60
> parameters = 0x7fffcc030100
> __func__ = "dconf_engine_manage_queue"
> #1 0x00007fffda227a51 in dconf_engine_change_fast
> (engine=0x555555805d80, changeset=changeset@entry=0x7fffcc02eb00
> ,
> origin_tag=origin_tag@entry=0x0, error=error@entry=0x0)
> at dconf-engine.c:1187
> node = 0x0
> #2 0x00007fffda2263ac in dconf_settings_backend_write
> (backend=0x55555579e450, key=0x55555611cc00
> "/org/gnome/evolution/mail/show-headers", value=0x0, origin_tag=0x0)
Hi,
if I've got it right then you do not see any runtime error before the
crash, there is no message on the console between you run evolution and
when it crashes. If so, then my previous message describes a different
issue. I'm sorry for the confusion.
The above-quoted part of the backtrace shows that DConf is trying to
save/write changes to the /org/gnome/evolution/mail/show-headers. I
found a similar issue filled against gnome-control-center:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1727020
which makes me wonder whether there's any issue with DConf itself.
There can be found more bugs when searching for
"dconf_settings_backend_write" (quotes for clarity only). I do not
know, I'd probably try to upgrade/downgrade DConf packages, but I've no
idea whether it would be helpful at all.
Bye,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
