Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash Reports view: inadequate - more or less absent - instructions #73

Open
LinuxOnTheDesktop opened this issue May 1, 2021 · 4 comments

Comments

@LinuxOnTheDesktop
Copy link

LinuxOnTheDesktop commented May 1, 2021

I was asked to provide a stack trace via MintReport. So I open MintReport and (having clicked 'Crash Reports' - which, I note, lacks a tooltip) I see this:

image

Pondering suggests that were there extant crash reports then they would show in the top box. As for the bottom box: I have no idea. Nor do I see how I could know what to do, if I go merely by the window provides. EDIT: Nor does the 'Help' button actually provide any help - the button is misnamed.

@Jeremy7701
Copy link

It may depend on the setting in /etc/systemd/coredump.conf [systemd is much too complicated for me]
I get something like this:-
Screenshot from 2021-05-02 01-44-49

There are multiple entries of "No symbol table info available" in the stack trace though.

@LinuxOnTheDesktop
Copy link
Author

LinuxOnTheDesktop commented May 4, 2021

Jeremy: thanks - I will investigate this, er, problem with the probem-reporting tool as soon as I have a chance. In the meantime, it would be helpful if you could find out how the tool (MintReport) is actually meant to work. Also, if what I see in MintReport is broken, then really the program itself should report the breakage. [EDIT: removed an extraneous word.] That is: seemingly there is a bug here in MintReport.

@Jeremy7701
Copy link

I think MintReport is probably working fine - but because I'm not running the debug versions of virtually all programs, virtually all dumps don't have "useful" symbol tables.
Currently, I have some dumps (mainly `/usr/libexec/csd-keyboard) for 1st, 2nd, 3rd, 4th of May). ;)

Have you considered whether coredumpctl in conjunction with /var/lib/systemd/coredump/ might be of interest to somebody?
Personally, I doubt it - unless someone knows different...

@LinuxOnTheDesktop
Copy link
Author

Some months after opening this issue, I found my first crash report within Mint Report. So, Mint report is, sometimes, doing something (as @Jeremy7701 said).

The point remains that_the program needs some instructions_. After all, if people cannot understand how Mint Report is meant to operate upon crash reports, then that will subvert the purpose for which the tool was created in the first place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants