Bug 121934 - Highlighting applied 2 days ago was gone tonight.
Summary: Highlighting applied 2 days ago was gone tonight.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-06 03:20 UTC by Maurice Jaillet
Modified: 2019-07-08 02:49 UTC (History)
2 users (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 Maurice Jaillet 2018-12-06 03:20:40 UTC
Description:
About 20 highlights I applied to a document 2 or 3 nights ago were gone tonight. I am not sure if the document was saved in that time. It was open when I looked at it tonight. It could easily be saved or not saved. this happened using Light Gray 4.

Another problem I have been having with the highlighting is that the intensity of the color will change after the document was saved and re-opened. This has happened on several documents. And it has been all the colors used that were affected. I used light colors to highlight - a very light red and Light Gray 4. When I re-opened the document the very light red had become a very intense very red red. And the gray had become a very very bright intense green. 1 or 2 other colors may have been involved.

I will enter another bug report for this other issue. But, I thought it should be made known since it might be related to the first issue.

If you need any more information I can dig it for you. I have just started using the highlights. They are important to what I am trying to do. I will have to get a document writer that works if this one will not.

I tried resetting the user profile at the first level(there were 2 options). I will see if anything changes. I didn't try to find out what to do to to deal with the OPEN GL. I will take it 1 step at a time.

Steps to Reproduce:
1.tried once to reproduce.
2.saved and re-opened.
3.no problem

Actual Results:
no problem occurred

Expected Results:
???


Reproducible: Couldn't Reproduce


User Profile Reset: Yes



Additional Info:
Version: 6.0.5.2 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 4; OS: Windows 6.1; UI render: default; 
Locale: en-US (en_US); Calc: group
Comment 1 Vera 2018-12-07 21:32:31 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.
(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 further detail.)
Comment 2 V Stuart Foote 2018-12-08 00:01:29 UTC
Also, behavior of native ODF Text .ODT file can differ markedly from OOXML Word .DOCX file. Taking an OOXML file "round trip", i.e. filter export -> filter import can have unexpected results. Best to stay with "native" ODF formats.

Please indicate if this loss of highlighting/background fill is with a .DOCX document?
Comment 3 QA Administrators 2019-06-07 02:53:15 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-07-08 02:49:39 UTC
Dear Maurice Jaillet,

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