Button to generate "debug report" for users
See original GitHub issueSometimes when users report problems with Etcher, it’s difficult to get all the info from them we need.
Perhaps there should be an button in the Etcher GUI somewhere (ping @konmouz ) that we could ask the users to click on that would generate a “debug report” they could send to us, which would contain all kinds of useful information, like:
- Etcher version
- OS (and version) that Etcher is being run on
- Name of the image that was selected
- Name of the drive that was selected
- Output of the DevTools console
- Output of the
drivelist
command - etc.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:24 (14 by maintainers)
Top Results From Across the Web
How to enable Debug Logs for any User | Salesforce Bytes
How to enable Debug Logs for any User | Salesforce Bytes - Salesforce Makes Sense - Video #11Salesforce Bytes is another video series...
Read more >Set Up Debug Logging - Salesforce Help
To activate debug logging for users, Apex classes, and Apex triggers, configure trace flags and debug levels in the Developer Console or in...
Read more >How to turn on the Salesforce debug log
1) In Salesforce, go to Setup > Administration Setup > Monitoring > Debug Logs · 2) On the Debug Logs page, in the...
Read more >Collecting Debugs for Tenable Products
This article describes the process on how to generate a debug report in Tenable products. Please sanitize any IP addresses or other ...
Read more >Salesforce Debug Logs: A Comprehensive Guide - Hevo Data
On the Salesforce window, search for 'Debug Logs' in the search box and select Debug Logs. To set the Debug Log, click on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I personally don’t think we should bother with automatic error reporting, since as @lurch , this will be the exception rather than the rule, and we’re pretty much covered in that aspect by TrackJS.
I propose to develop a button that users can click to generate a file containing all sorts of information about their system (generic stuff, no personal information), and they can send it to us by themselves (on a GitHub issue, or attaching to Gitter).
This could be indeed an issue. So for now we can have an option in settings and just a dialog when something goes wrong.