Version: (using Devel) Installed from: Compiled sources I clicked on Developer information to get a backtrace after an assert, and then clicked report bug to try it out this time. Unfortunately the report bug wizard did not keep the backtrace I needed and replaced it with "this backtrace is not useful" (which it wasn't). Please provide a way to have access to the backtrace.
- Which SVN revision/branch ? The backtrace *is* saved when it is fetched the first time, so the Backtrace Page in the report assistant shouldn't need to regenerate it... (it just reload the cached backtrace) So, this looks like a bug.. - Did the process die after you clicked Report Bug (or when you go to the Backtrace Page) ? - Could you try to reproduce the situation ? (does it happen with other crashes?) Regards
Created attachment 42532 [details] backtracedisappears
Created attachment 42533 [details] backtracedisappears
Created attachment 42534 [details] backtracedisappears
This is a ui bug. Once I click "report bug" I can no longer see it even if I know I want to. No available dialogs show it.
All the three attached images are the same file, is that ok ? Also, in the Report dialog, in the backtrace fetching page it should show you the backtrace (as it will try to regenerate it , because the backtrace you generated the first time is not complete (0 stars)) Also, as another bug, you told that the backtrace is rated as "not useful" while it was useful... if that is the case, please create a new bug report against DrKonqi and attach the full backtrace. Thanks
- May be you aren't getting the Report Assistant wizard at all ? or may be your aren't getting to the Backtrace generation page in the wizard because of some other bug ? (may be because the information you can provide about the crash is not really useful/complete? (step1) )
Created attachment 42537 [details] backtracedisappears2
Created attachment 42541 [details] backtracedisappears2
Created attachment 42543 [details] bt2
Sorry I'm having some image upload issues. The two correct images should be there now.
Oh, that case.. Well.. as the backtrace is considered "not really useful", it is not even saved for the report (to avoid people trying to manually report a mostly incomplete (and not really useful) backtrace)... - Which kind of alternative could be implemented ? * May be including the incomplete backtrace but warning it is not useful ? * May be including an option to get the backtrace anyways ?
I suggest making the "back" button in the second screenshot enabled and take you to a page containing the original backtrace. That way the wizard starts on page 1, but page 0 is for developers who still want to see the backtrace and made the mistake of clicking the button before saving it.
That doesn't seem pretty or discoverable :-\ A possible solution would be something like I proposed some time ago at http://blip.tv/file/2610206/ (however it has major drawbacks.. as the dialog is too much cluttered (too much buttons in the bottom))
I don't know how pretty it needs to be, but the first thing I did was to click back to try to undo what I had just done (clicking report bug). Whatever solution you come up with is fine I'm sure.
There is a "workaround": in the first page, tell the assistant that you can reproduce the issue all the times and that you can provide a lot of information; this way you trick the assistant to think the report can still be useful, leading you to the backtrace fetching page (which will show your backtrace)...
In the new UI you can navigate freely back until a submission has actually been made. That should address the concerns here.