Re: [Evolution] Logwatch reports segmentation faults in Evolution

[Milan Crha <mcrha redhat com>]

On Sat, 2022-10-01 at 14:39 -0500, Tim McConnell via evolution-list
wrote:
> But for those that don't know it: 

        Hi,
I see, thanks. My memory is rusty, which doesn't help in many ways. I'm
sorry about that.

> one when I clicked on a link from an email (job posting)

A process started from an application, which is run from a terminal,
shares the terminal pipes (stdout/stderr/...). I think, and only think,
that those JavaScript related messages are from the browser, or from
its helper, which passed the clicked URL to the running instance. Which
exact part reports it I do not know, maybe certain plugin the browser
has installed, who knows. They might be harmless for the evolution
itself.

> the second one when I used Ctl+Q (quit evolution) which I always get
> when I exit an Evolution session from a command prompt.

That's a very boring message, whose fix requires fundamental changes I
didn't brave myself to try to address yet. A bit more info here:
https://gitlab.gnome.org/GNOME/glib/-/issues/1857
It's also harmless, it's basically telling that there's a memory leak.
It does not hurt, because the app is closing anyway.
        Bye,
        Milan