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

Automatic crash reports #601

Open
vjr opened this issue Oct 21, 2024 · 1 comment
Open

Automatic crash reports #601

vjr opened this issue Oct 21, 2024 · 1 comment
Labels
Needs Design Waiting for input from the UX team

Comments

@vjr
Copy link
Member

vjr commented Oct 21, 2024

Problem

If there is a crash in an elementary app/component I've seen requests to users to collect dumps/traces and upload to github issue reports, which is a manual process and I presume many people find it complicated to do.

Proposal

Configure the OS to automatically capture crash dumps which can then either automatically be uploaded to github issue reports, or if the reporting might risk a flood of tickets, at least make it straightforward for users to view/post to their own github issue reports, say via the feedback app.

Prior Art (Optional)

There was a recent series of blog posts by KDE dev about automatic collection of crash reports, see:

https://planet.kde.org/harald-sitter-2024-08-20-plasma-crash-course-kcrash/

https://planet.kde.org/harald-sitter-2024-08-27-plasma-crash-course-coredumpd/

https://planet.kde.org/harald-sitter-2024-09-04-plasma-crash-course-drkonqi/

Perhaps elementary OS can have similar approach, if not the third one, just collect it in the feedback app to post to github, I think Ubuntu has some tool (is it called apport?) that does something similar.

@vjr vjr added the Needs Design Waiting for input from the UX team label Oct 21, 2024
@teamcons
Copy link

For a long gone distribution, since the same "please run this" "please give info that" showed up constantly on forums, i cobbled up a script which grabbed various latest entries to logs, bundled them in a text file, then sent it to pastebin. The devs shipped it, so people were encouraged before reporting to run it, then give along the link.

Im not sure about the three things you posted, that is above my paygrade, but the end user is already encouraged to come submit their report through Feedback app
I feel it could be accessible to do a enhanced Feedback app (or a bug collection app) which also collects several informations (latest dmesg, wayland-or-x11, which eOS, when last update), so end users also do not come around this place empty handed, but have a text file or something, full of info about their issue.

before any more technical more involved solutions like the above, that could be a good makeshift start to expand on later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Design Waiting for input from the UX team
Projects
None yet
Development

No branches or pull requests

2 participants