Bug 108510 - Imported .doc file renders characters near endnotes uneditable
Summary: Imported .doc file renders characters near endnotes uneditable
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.8.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-13 17:49 UTC by Bradley Smith
Modified: 2018-07-03 14:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bradley Smith 2017-06-13 17:49:42 UTC
Description:
When I open a .doc file with endnotes (for a citations list at the end), those characters are not editable, giving me the message: Readonly content cannot be changed. Modifications will not be accepted.
In addition, the two neighboring characters are also listed as read-only; I cannot add delete a character that comes after the endnote nor can I add or delete a character before one.

Steps to Reproduce:
1. Open MS Word .doc file with endnotes.
2. Attempt to modify, delete, or insert any character near one of these endnotes.

Actual Results:  
I cannot change nearby characters or delete the endnote.

Expected Results:
I should be able to at least change nearby characters even if the endnote is readonly.


Reproducible: Always

User Profile Reset: No

Additional Info:
I am unsure if this has to do with the fact that the document also already has “Record changes” data in it from MS Word. I do not have other documents that are not in the process of being proofread to test this.


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Comment 1 Xisco Faulí 2017-06-13 21:47:54 UTC
Thank you for reporting the bug.
it seems you're using a really old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 Bradley Smith 2017-06-14 03:29:37 UTC
I apologize for the old version. This is just what is being push updated through Ubuntu (14.04) software updates. I don't think anything from version 5 was pushed through, nor is it found on the Ubuntu Software store, which may be another issue to be solved unless I'm just doing it wrong. I'm relatively new to linux-based systems.

I'll manually install it and let you know shortly.
Comment 3 Bradley Smith 2017-06-14 17:43:58 UTC
Hello, yes I have tried this and it does still occur with Version 5.

Following build information:
Version: 5.3.3.2
Build ID: 1:5.3.3~rc2-0ubuntu0.14.04.1~lo0
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 4 Xisco Faulí 2017-11-13 18:01:34 UTC
Hello Bradley,
Please attach a sample document, as this makes it easier for us to verify the bug.
Comment 5 QA Administrators 2018-05-30 16:40:09 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2018-07-03 14:19:08 UTC
Dear Bug Submitter,

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-20180703