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 sending of user reports/feedback #4406

Closed
nvaccessAuto opened this issue Aug 21, 2014 · 6 comments
Closed

Automatic sending of user reports/feedback #4406

nvaccessAuto opened this issue Aug 21, 2014 · 6 comments

Comments

@nvaccessAuto
Copy link

Reported by kattygeltmeyer on 2014-08-21 11:55
Please, make it possible to have an automatic feedback/report system within nvda. In supernova 14+ you can activate a kind of user feedback system, which permits the user to send crash reports, logs ... user statistics to Dolphin in an automated way. I suppose this could be helpfull for you too.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-08-21 12:05
We could probably automate crash reports, though actual NVDA crashes are pretty rare. Aside from that, the rest can't really be automated, as we usually need to know details about the issue before we know what the user will need to submit to us. We don't want users just submitting arbitrary logs with no context. Also, there are privacy concerns.

I don't think the gain justifies the work involved here, though this can be reopened in future if this changes.
Changes:
Added labels: wontfix
State: closed

@nvaccessAuto
Copy link
Author

Comment 2 by vgjh2005 on 2014-08-21 14:16
Hi:
When NVDA is crashed, Offer a form to offer information about this bug. Field the content to the EditBox and Press submit. Send the report to NVDA community.
Thanks!

@nvaccessAuto
Copy link
Author

Comment 3 by briang1 on 2014-08-21 14:49

I somehow feel that won't work as it depends what crashes. In fact what you would need is an nvda reboot which detcted the crash and saved stuff as Windows tends to do, and also Firefox. Given that the log is saved and an old log is alwaysstill there all one really would need is to ask the user to retrieve it and post a message somewhere.At present only the ticket system is used for this sort of thing, but really it needs to be somewhere others can see it and see if its confirmed or not, as if the latter it could alwys be the users sogftware which is the issue. I think things work as well as could be expected now, and really as Jamie says, you don't want lots of noise coming in when the eroor or whatever is not nvda's problem.

@nvaccessAuto
Copy link
Author

Comment 4 by vgjh2005 on 2014-08-22 05:49
Hi:
If the error appear three times, Jump a dialog to ask user if you wish to make a report for the same error.
Thanks!

@nvaccessAuto
Copy link
Author

Comment 5 by briang1 on 2014-08-22 09:44
The problem is that when nvda has an error even if its not nvdas fault, it can be a multiple error either the same one repeated due to a timing issue or a cascade as the issue falls through the various subroutines which are running at the time.
I've yet to see an automated error logger that will send to the authors that works. I get very annoyed at the one in Winamp for example which seems to come in and upset the user, even when the program is still working, presumably due to it picking up unexpected data.
Brian

@nvaccessAuto
Copy link
Author

Comment 6 by vgjh2005 on 2014-08-23 05:08
Hi:
This is the taking or rejecting problem. Now, some problems that is not related about NVDA will also be reported. However, this way is easier for reporting BUG and more error will be known.
Thanks!

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

No branches or pull requests

2 participants