Re: [Geary] Geary 0.12 crashing on Fedora 26
- From: Casey Stone <tcstone caseystone com>
- To: Federico Bruni <fede inventati org>
- Cc: Michael Gratton <mike vee net>, geary-list gnome org
- Subject: Re: [Geary] Geary 0.12 crashing on Fedora 26
- Date: Thu, 14 Dec 2017 10:38:57 +0000
Thanks for that info Federico. I found the report. Attempting to submit
it I was warned sending my core dumps might expose sensitive info so I
didn't, then I was warned it would install about 4GB of software (to
analyse the core dump locally maybe???) so I cancelled that.
For now I'll assume the crashing may have been from my outdated theme,
though I could send the backtrace from the problem report to you
Michael if you want it.
On Thu, 14 Dec, 2017 at 6:42 AM, Federico Bruni <fede inventati org>
wrote:
Il giorno mer 13 dic 2017 alle 23:23, Michael Gratton <mike vee net>
ha scritto:
W dniu Thu, 14 Dec 2017 o 7∶50 użytkownik Casey Stone
<tcstone caseystone com> napisał:
Are you (the author or someone) receiving the crash reports that
Fedora tells me are being sent after a crash? Can something be
done to make it more stable?
On this: Crash reports for the distros go to their own crash/bug
tracking service and I think the way it works is that package
maintainers generally triage and report issues upstream. I haven't
heard of any coming from Fedora though. I use Ubuntu myself, so
don't really know where to look, either.
If you or someone who knows Fedora can point me at where these crash
reports get sent, or even better file some bugs for them in Geary's
bug tracker, I'd be happy to look into fixing them.
The application handling the bug reports in Fedora is:
https://github.com/abrt/gnome-abrt
Casey, type "report" in gnome-shell and you'll see it.
By default, crash reports are automatically reported to Red Hat bug
tracker, specifically to the fedora_contrib_private group. So these
reports are not publicly visible by default. But you can add a
comment to the report and ask to make it public.
You can see your configuration in gnome-abrt preferences.
You can also quickly see the stacktrace of the latest crash using
this command:
coredumpctl dump
Core dumps are saved for a few days in this directory:
$ ls -lh /var/lib/systemd/coredump/
totale 119M
-rw-r-----+ 1 root root 70M 12 dic 08.26
core.gnome-shell.1000.ba2f7bf599094fb88a1b4611ec63e312.1735.1513063599000000.lz4
-rw-r----- 1 root root 43M 13 dic 06.41
core.packagekitd.0.08d2d638d7ef4d4bbdddf39930007936.1359.1513143691000000.lz4
-rw-r-----+ 1 root root 6,6M 12 dic 08.26
core.Xwayland.1000.ba2f7bf599094fb88a1b4611ec63e312.1771.1513063603000000.lz4
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]