[Users] [Bug 4385] Fedora reporting kernel crashes related to Claws Mail

[edwardp at gmx.com]

On Fri, 25 Sep 2020 06:01:24 +0600
Dustin Miller <dustbiz at gmail.com> wrote:

> On Thu, 24 Sep 2020 08:41:12 +0000
> noreply at thewildbeast.co.uk wrote:
>
> > https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4385
> >
> > --- Comment #27 from Jeremy Nicoll <jn.wb.bzc.0306 at letterboxes.org>
> > --- Comment on attachment 2102
> >   -->
> > https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=2102
> > Entire gdb output - personal information removed
> >
> > Just for information - the file you uploaded it contains a tiny
> > amount of info from gdb - just 4 lines at the top saying it is
> > starting claws, and just 4 lines at the bottom saying it's got
> > control again because claws crashed.
> >
> DM: Thanks for this, Jeremy. I haven't ever used gdb so this is
> helpful to know.
>
> DM: Edward, Jeremy's comment here is a good corrective to my previous
> posts on this. So I'm guessing Paul's earlier comment was probably
> because you had copied part of the gdb-specific output rather than the
> claws-specific output, but I'm not sure on that.
>
> DM: Interesting that you found the similar issue from a year ago.
> Seems like the first thing that needs to be figured out is whether
> the bug is with Claws or with one of its supporting libraries. Not
> sure how to go about doing that, but hopefully you and/or the
> developers will be able to come up with a good workaround or solution
> for you. Cheers, ---Dustin
> >
> > ALL the rest of the output is from claws, and is the "debug trace"
> > that claws produces when run with the "--debug" flag (in this case
> > because gdb was told to start claws by "run --debug").  These lines
> > show what claws was doing and why it was doing it... with as much or
> > as little info as the claws programmers thought they'd need when
> > trying to follow the workings of claws.  Ideally it shows what claws
> > was about to try to do just before the crash, but earlier on it will
> > also show stuff from claws' setup which might help to explain what
> > happened.
> >
> > gdb itself really only comes into play once claws has crashed, when
> > gdb is then able to look at the contents of memory, create the stack
> > trace etc, showing what the immediate aftermath of the crash looks
> > like and hopefully just info, combined with the --debug info - for
> > someone to work out why it happened.

I just wish Fedora's retrace server were back online, so I can submit
all the crash reports.

Just during the past two weeks, there are now 15 Claws Mail crashes
queued in Fedora's ABRT crash reporter (including below and the one in
my bug report), plus an additional 18 kernel crashes (kernel-core) - all
referencing Claws and all indicating libgobject_2.0.

I have submitted a bug report at Red Hat/Fedora on the package
containing this library while also referencing my Claws bug
report, but have not heard anything on it yet.

FWIW, I tried changing the theme in the XFCE desktop, Claws crashed
again, referencing the same library. MATE, LXQt and now XFCE. Although
I also have KDE Plasma installed, I'm not even going to try it, because
once logged in, it changes the icon theme for other desktops.

Something is causing these crashes, either Claws or the library. I
just hope some or all of the information will help...