[Libreoffice-bugs] [Bug 140869] New: In Version 7.1.1.1 of LO for Windows (x64), Crash reporter shows up with blank instead of link to submit, even though crash dump is created.

Mon Mar 8 03:20:03 UTC 2021

https://bugs.documentfoundation.org/show_bug.cgi?id=140869

            Bug ID: 140869
           Summary: In Version 7.1.1.1 of LO for Windows (x64), Crash
                    reporter shows up with blank instead of link to
                    submit, even though crash dump is created.
           Product: LibreOffice
           Version: 7.1.1.1 rc
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: richard416282 at yahoo.ca

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210308/adf8a220/attachment.htm>