https://bugs.documentfoundation.org/show_bug.cgi?id=148159
Bug ID: 148159
Summary: Please check if you get error reports which are
assigned to the wrong version of LibreOfficeWriter
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Description:
It just happened to me that LibreOfficeDev version 7.4 crashed. When I opened
the same file with an earlier version, this one told me that LibreOfficeWriter
has just crashed and offered me the opportunity to send a crash report.
It might be the case that the older version of LibreOffice associates its own
version number to the crash report. I can’t check it. But if this really
happens, crash reports might become misleading for developers!
Steps to Reproduce:
1.Open a document with which LO Writer crashes
2.Open the same document again with another version of LibreOffice
3.
Actual Results:
The other version of LibreOffice tells me that it just has crashed. It also
offers me to send a crash report.
If it associates its own version number to the crash report, you'll get one
under the wrong headline!
Expected Results:
In case of a crash report, as a user I would expect to see:
• an indication in which part of the program the error occurred and what
type of bug it is (e.g. insufficient memory, Null pointer, … or whatever else
can be found in the crash dump, only the first few lines to just see what type
of bug it is),
• an indication what information will be sent in the crash report,
• a progress indicator showing the percentage to be transferred and how
many bytes this will be when completed.
• a unique issue number related to the uploaded crash information, which is
shown in one of these bug reporting windows,
• I would expect that LibreOfficeWriter keeps track on these issue numbers
and dates and I would expect LibreOffice to have a function, which – when
invoked – asks te LibreOffice bug tracing system which of these issues are
resolved and telling me, if I should install a new version of LO because of
this progress,
• I would expect a small dialogue where I would be asked a few questions:
◦ What did you do just before the crash happened: in this case: open a
file,
◦ If it has to do with files: questions on their size (in number of
pages, storage, …)
◦ If the bug happened with more than one file if the respective
characteristics (yes, it happened with more than one large file, but it did not
happen with one with 1200 pages instead of ca 670 and it also happened on a 167
pages document: this one showed up for a short moment, then it crashed. A
~-lock<filename.odt># locking file was left over after each such crash..
◦ If it did not happen, if they are loaded into an earlier version –
which one?
◦ If it was possible to deliver an example document of up to ten pages,
which reproducibly shows the bug.
For more details on my expectations see my attachment to another crash report:
https://bugs.documentfoundation.org/attachment.cgi?id=178959
Reproducible: Always
User Profile Reset: No
Additional Info:
This is the version which caused a crash:
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 59a7c40255b836ed75e64686fabb3e9938b755f0
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded
I opened again in Version: 6.4.4.2
Build-ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU-Threads: 4; BS: Linux 5.4; UI-Render: Standard; VCL: gtk3;
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
