On Mon, 2021-11-01 at 22:27 +0100, van snyder wrote:
> The replies didn't reach me via e-mail,...
Hi,
could you verify you are subscribed with the address at:
https://mail.gnome.org/mailman/listinfo/evolution-list
If you are, then check the junk folder (either under On This Computer
or on the server you download the messages from).
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): std::bad_alloc
> Abort
Just to be sure, could you run evolution as below, to see where exactly
it crashed, please?
$ gdb --batch evolution --ex r --ex bt --ex q
It will show the backtrace of the crash and will quit. I'd like to
verify it crashes somewhere below the WebKitGTK code. Verify the output
before sharing it anywhere, to not expose anything private. even
encoded bits can contain private information.
By the way, can you run devhelp or epiphany? Those are the two using
WebKitGTK I know of.
If you cannot downgrade, then you are on a good way to reach the distro
maintainer and ask them to fix this, by rebuilding or just do anything
to unbreak the package.
> "Some of those updated packages broke Evolution."
>
> That's a good argument for a statically-linked code, if only you
> could do it.
No, statically linked code is a bad idea by many means. You do not want
to download gigabytes of packages just because they all statically link
to 1KB library, which has a sever security issue fixed.
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
