On Thu, 2018-03-22 at 09:52 +0100, Matej Marusak wrote:
> Now you knew that there is something wrong with kernel and you have a
> good starting point for you later investigation.
Hi,
yes, I agree, informing is good, but this one is not useless only for
developers, it's useless also for the user. It's a starting point, but
also the final point. I do not know how to debug kernel crashes and I'd
bet the "Details" button was disabled (it's a long time, I can be
wrong), not talking that getting information from the ABRT GUI (like
the most important is the backtrace of the crash for me) is a problem,
as it's not available there at all or it cannot be copied from the GUI
(not everything in the GUI of ABRT can be copied out).
My options, as I see them:
- ABRT tells me kernel crashed during boot, but doesn't let me file
the bug
As a regular user:
- file a bug in probably Red Hat bugzilla and hope kernel folks
monitor it, thus they can help/guide me and so on
- read about the crash the next boot, until...
As a developer:
- oops, kernel crashed. I've no idea how to debug kernel crashes
during boot, thus let's file a bug and continue as a regular
user above.
So I end up with a bug and with a hope. What's the main difference
between the bug filled by ABRT and the one filled by me? As long as the
anonymous bug reports are disabled (it's the FAF for, right, bugs
cannot be filled anonymously), then the bug I fill manually is even
less useful than the one which ABRT would fill. Why? ABRT may include
basic information about the issue, like what crashed, when/where it
crashed, what versions of packages had been involved and all that
information which the developer would ask for anyway, but which I'd not
always be able to give him/her easily (see above, cannot copy
everything from the ABRT GUI). Thus ABRT-filled bug would be more
accurate and contain much more information than what the user would do.
Frankly, my initial bug text would probably look like:
ABRT tells me about a crash of kernel after boot, but ABRT claims
the report would be useless for kernel developers, thus it doesn't
let me to report it. Could you guide me what to do now to
investigate the crash, please? It's there after each restart
of the machine.
I even do not know what heuristic is done to make ABRT think that the
human kernel developer would consider the report useless.
> (Or still, if you are experienced enough you can take closer look
> into the problem details)
This is kernel/boot related. Most users are not experienced enough, I'm
pretty sure of it.
Bye,
Milan
_______________________________________________
desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
