Bug 142089 - LIbreoffice crashes at opening a document
Summary: LIbreoffice crashes at opening a document
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-05 05:15 UTC by Jerzy Orlowski
Modified: 2021-12-03 04:47 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
backtrace (14.14 KB, text/x-log)
2021-05-05 05:15 UTC, Jerzy Orlowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jerzy Orlowski 2021-05-05 05:15:00 UTC
Description:
Libre office crashes on opening a document

Steps to Reproduce:
1.Open a document

Actual Results:
Ducent recovery window

Expected Results:
OPened document


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
I cannot send the document, because it contains data of my client that I cannot share
Comment 1 Jerzy Orlowski 2021-05-05 05:15:49 UTC
Created attachment 171638 [details]
backtrace
Comment 2 Jerzy Orlowski 2021-05-05 05:17:22 UTC
The document was edited by my client in word. I tried to delete all stuff that I cannot share, but after I save the docuemnt in libreoffice, the bug dissapears.
Comment 3 Xisco Faulí 2021-05-05 08:58:54 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 4 Telesto 2021-05-05 13:49:07 UTC
(In reply to Xisco Faulí from comment #3)
> Thank you for reporting the bug. Please attach a sample document, as this
> makes it easier for us to verify the bug. 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the requested document is provided.
> (Please note that the attachment will be public, remove any sensitive
> information before attaching it. 
> See
> https://wiki.documentfoundation.org/QA/
> FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help
> on how to do so.)

@Xisco
Note the additional info: I cannot send the document, because it contains data of my client that I cannot share

So it's or sanitizing attempt or secondly private sharing?
Comment 5 Telesto 2021-05-05 13:50:19 UTC
@Jerzy,
Please try a recent version (7.1) to check if the bug is still present (else the whole sanitizing/sending privately topic being pretty pointless
Comment 6 Julien Nabet 2021-05-05 18:23:42 UTC
Also, you can try this https://wiki.documentfoundation.org/QA/FirstSteps
Comment 7 QA Administrators 2021-11-02 04:11:12 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2021-12-03 04:47:43 UTC
Dear Jerzy Orlowski,

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