Description: When running the (was then) Latest version of the Non-development version of LO 7.1, and a bug tripped up the operation, a screen popped up imploring me to report the bug, and what was happening when it stumbled and fell (I know its a walking or running metaphor, but well, this is English too. In my case it was the bug of the "Cntl-K" when inputting URLs into fields in LO Calc. But the bigger problem, was that the LO handler for bug reporting failed in both the DEV, and the Release versions. Instead there was a single blank line where the submit link used to be, and where a copy/paste could be done by opening a browser window, then clicking enter or go on any browser. But now, the dumber question, how do I force a bug trip, to validate or Invalidate the failure of 7.1.1.1 (non dev) to give a bug submission request. Alas, using "search", in Bugzilla for LO gave me a few hits, none of them matched the problem I experienced with LO 7.1.1.1 even though I had been using LO DEV version 7.2.0 to test if the bug was fixed or not in the beta versions. So, the question needs to be asked, when LO crashes with a blank whitespace, what is needed from a vanilla user, to submit the crash details. The "Documentation" for windows users is very scant, and reads like Uninstall Windows, but use Unix emulator for windows users (CYGWIN), and get a unix like machine to start speaking dev-speak. Granted this may be a harsh read for those who are not Windows familiar, there was very little in the documentation. PS. Bugzilla needs to be updated to push the Bug Version from 7.0.3 to the latest choices 7.1 and 7.2, Likewise Option for Windows(all). Steps to Reproduce: 1. Download LO 7.1 from download link (goes to local mirror) 2. Stumble onto a bug. (crash, bluescreen, error-code) 3. Option presented to submit report with [OK] button, or to restart LO in reduced function mode, with no extensions loaded.......but field is blank, yet no guidance is given in LO documentation page except...... being familiar with bugzilla , find thread asking for bugs to be reported for DEV cases, yet closed with WONTFIX or similar downvote. Actual Results: Need to look up crsh reports in C:\Users\[user-name]\AppData\Roaming\LibreOffice\4\crash. There are 8 'dmp' files there, but never did the program or the developers point USERS into this direction. Just "WONTFIX" or in my case "Duplicate of Bug xxxx", where bug was described as similar, yet invoked the same code. You cannot get a keyboard code (CNTRL-K) from a mouse click. Expected Results: Expected patience with the new user experience. Instead got "please provide more details...", but without knowing where to look for "details", had to search on my own. The simple stuff is not explained to the end user, nor do the documents point to specific and easy steps to take. Reproducible: Always User Profile Reset: No Additional Info: The software *should* point one to the specific page at the "how to submit a bug" document, that is clear, concise, and easy to use. Former MS-win click and press types, are not likely to become software developers or 'coders' overnight, nor should they be expected to. The process *should* be 3 steps: A click on the "error dialogue box" to either submit a bug, and include the relative internal process steps, or not click on submit, but be able to submit a redacted version with full knowledge that the bug will get looked at eventually, with the dummy data embedded in the report. The user would be promped for an e-mail address, where a reply can be sent (or not if they wish to retain their anonymity), and finally, A reference number or link spat back from the server(s) with the internal IP address of the submission embedded into the referral code, that can be analyzed to determine if further action needs to be performed, based on various criteria, Language, OS, or regional variation.
Created attachment 170324 [details] LO Crashed Screen grab by date[redacted file name] image of screen grab
Actual screen was "LibreOffice Document Recovery", (see attachment of JPG file,27KB) Text of window is : "Due to an error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically." and "The following files will be recovered:" [filename_redacted].ods [see redacted image , 36kb]
Original text of error message with blank url in field. "Please check the report and if no bug report is connected to the crash report yet, open a new bug report at bugs.documentfoundation.org. Add detailed instructions on how to reproduce the crash and the shown crash ID into the crash report field. Thank you for your help in improving LibreOffice."
the similar text was reported as popping up in DEV version of master build. https://bugs.documentfoundation.org/show_bug.cgi?id=126488 But this was a running Non-dev build (or so I thought). Unknown now if this is only showing up in DEV master builds, or in Release or RC builds. will attempt to recreate error, but still would like to know how to Manually submit 1 of the 'dmp' files, and if they can say which version caused the hiccup, then restart of LO. Does LO Dev need extra files, since it was LO 7.1.1.1 that I was running, when it fell on its face. Possible LO corruption since I had moved my "documents" folder from C:\users\[user-name]\documents, to USB Attached secondary HDD, some days earlier to K:\users\[username]\documents. and updated the field in LO to point to drive K instead of C for file storage.
Created attachment 170326 [details] Crash Report with blank link for submission.[png duplicate from 2019] actual location: https://bugs.documentfoundation.org/attachment.cgi?id=152887
Maybe the server was not reachable when you reported the crash. Could you please try again ?
Dear Richard_416282, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Richard_416282, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp