The latest 14w30b snapshot crashed, and the Launcher prompted to send a crash report to Mojang. I clicked the button to publish the report and the dialog disappears.
What I expected to happen was...:
The dialog box was dismissed without actually confirming if the bug report had been properly published.
What actually happened was...:
Some indication should be given as to the status of the bug report.
Steps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. ...
3. ...
Linked issues
is duplicated by 2
relates to 1
Comments 6
From MCL-3383:
Cannot confirm, the Launcher Log says
[17:48:05 INFO]: Reported crash to Mojang (ID 0)
But some kind of feed back in form of a text would be appreciated...
Confirmed for forced crashes for
1.6.43 (Windows)
However it seems that other crashes cause the launcher to open the bug tracker instead
Is this still a concern in the current Minecraft Launcher version 2.0.805 / 2.0.806? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened it as soon as the requested information has been delivered.
I agree that even very minimal user feedback would be helpful. (affects 1.5.1)