Re: [Evolution] Logwatch reports segmentation faults in Evolution

[Tim McConnell <tmcconnell168 gmail com>]

Hi Milan,
So I've followed the steps you sent and now it doesn't crash. It hasn't
shown any segmentation faults in my Logwatch report either. 
I have been doing upgrades as they are released for Debian Testing
(Bookworm) so that may have solved it?
While I was trying to recreate the issue, I did get these minor errors:

(evolution:4003): GLib-GIO-WARNING **: 15:08:43.589: Your application
did not unregister from D-Bus before destruction. Consider using
g_application_run(). (When shutting down in GDB)

And: 

ATTENTION: default value of option mesa_glthread overridden by
environment.
ATTENTION: default value of option mesa_glthread overridden by
environment.
ATTENTION: default value of option mesa_glthread overridden by
environment.
ATTENTION: default value of option mesa_glthread overridden by
environment.
[New Thread 0x7fff637fc640 (LWP 7555)]
Missing chrome or resource URL:
resource://gre/modules/UpdateListener.jsm
Missing chrome or resource URL:
resource://gre/modules/UpdateListener.sys.mjs
[Thread 0x7fff483f1640 (LWP 7484) exited]
Missing chrome or resource URL:
resource://gre/modules/UpdateListener.jsm
Missing chrome or resource URL:
resource://gre/modules/UpdateListener.sys.mjs
(when opening a link in email, I'm not sure why it's looking for
chrome. My default is firefox? ) 
Anyway it appears to be fixed, thanks for responding.

-- 
Tim McConnell <tmcconnell168 gmail com>


On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list wrote:
> On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
> wrote:
> > I'm on Evolution 3.45.3-2 and my logwatch has been reporting
> > segmentation faults for the last few days.
>
>         Hi,
> I do not know what logwatch is, nor how one gets more detailed
> information out of it, but if you face evolution process crashes,
> then
> I suggest to run it from a terminal under gdb and get the backtrace
> when the crash happens. Note the gdb will catch it and will wait for
> an
> input while the GUI will look frozen. A command can be:
>
>    $ gdb evolution --ex r
>
> and once it stops do:
>
>    (gdb) bt
>
> to print the current thread backtrace. An information before this
> command can be useful too, possibly showing some runtime warnings. To
> quit gdb simply execute command in its prompt:
>
>    (gdb) q
>
> Please check the backtrace for any private information, like
> passwords,
> email addresses, server addresses,... I usually search for "pass" at
> least (quotes for clarity only).
>
>         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