Bug 90972 - Segmentation fault (crash) when attempting to save a .doc file
Summary: Segmentation fault (crash) when attempting to save a .doc file
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.3.7.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-30 16:03 UTC by robstewart57
Modified: 2023-11-21 07:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
GDB trace file (38.50 KB, text/x-log)
2015-04-30 16:03 UTC, robstewart57
Details

Note You need to log in before you can comment on or make changes to this bug.
Description robstewart57 2015-04-30 16:03:14 UTC
Created attachment 115223 [details]
GDB trace file

To reproduce, I:

1. Open a .doc file.

2. Edit by adding a character.

3. LibreOffice Writer crashes.

The first line of errors in the GDB trace is:

Program received signal SIGSEGV, Segmentation fault.
0xb0ac8673 in WW8Export::RestoreMacroCmds() () from /usr/lib/libreoffice/program/../program/libmswordlo.so

Attached is the complete gdbtrace.log file.
Comment 1 raal 2015-04-30 16:17:37 UTC
Hello ,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Thank you
Comment 2 QA Administrators 2015-12-27 20:30:46 UTC
Dear Bug Submitter,

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 INVALID
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
Comment 3 QA Administrators 2016-05-09 20:07:16 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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

This INVALID Message was generated on: 2016-05-09