Bug 83964 - FILEOPEN: FILEOPEN: Highlights bug in doc files
Summary: FILEOPEN: FILEOPEN: Highlights bug in doc files
Status: RESOLVED DUPLICATE of bug 79330
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.1.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: bibisected, regression
Depends on:
Blocks:
 
Reported: 2014-09-17 06:39 UTC by Michael Kůr
Modified: 2021-03-11 09:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Sreenshot where is in circle bug (31.25 KB, image/jpeg)
2014-09-17 06:39 UTC, Michael Kůr 		Details
Here is a picture with expected behavior (26.31 KB, image/jpeg)
2014-09-17 07:58 UTC, Michael Kůr 		Details
Page seven from your book (29.50 KB, application/msword)
2014-09-17 21:01 UTC, Jacques Guilleron 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kůr 2014-09-17 06:39:05 UTC 
Created attachment 106408 [details]
Sreenshot where is in circle bug

Problem description: 

Steps to reproduce:
1. Create document with some highlights.
2. Save the document
3. Reopen document

Current behavior: The highlights appears randomly.

Expected behavior: The highlights appears as it was been saved.

Note: Latest working version is 4.0.2.2.
Operating System: Windows 8
Version: 4.3.1.2 release
Comment 1 Michael Kůr 2014-09-17 07:58:12 UTC 
Created attachment 106413 [details]
Here is a picture with expected behavior
Comment 2 Jacques Guilleron 2014-09-17 14:54:06 UTC 
Hi Michael,

Can you provide a sample where you see this behaviour?

Thank you,

Jacques
Comment 3 Michael Kůr 2014-09-17 16:37:22 UTC 
Yes the document is too big to upload it as attachment, so I uploaded it to Google Drive: https://drive.google.com/file/d/0B9kXRNWWgjR9ZXlUd0Q0N25fck0/edit?usp=sharing
Comment 4 Jacques Guilleron 2014-09-17 21:00:10 UTC 
I extracted page seven from your book. 
I confirm the behaviour with LO 4.3.2.1
Build ID: f9b3ad49d92181b0a1fe7e76f785a2c2cd0847d3
& Windows 7 Home Premium.

LO 3.6.7.2 don't reproduce this behaviour. So this is a regression.
I set status to NEW.

Thank you for the report,

regards,

Jacques
Comment 5 Jacques Guilleron 2014-09-17 21:01:36 UTC 
Created attachment 106464 [details]
Page seven from your book
Comment 6 Xisco Faulí 2014-09-19 12:09:58 UTC 
 56260020c5caba00fbd063db5554b452c06116dc is the first bad commit
commit 56260020c5caba00fbd063db5554b452c06116dc
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Wed Oct 16 14:50:19 2013 +0000

    source-hash-34847f1cf7538c333e9b8700eb4012ae358644a6
    
    commit 34847f1cf7538c333e9b8700eb4012ae358644a6
    Author:     Kohei Yoshida <kohei.yoshida@gmail.com>
    AuthorDate: Tue Nov 6 19:17:19 2012 -0500
    Commit:     Kohei Yoshida <kohei.yoshida@gmail.com>
    CommitDate: Thu Mar 14 15:35:48 2013 -0400
    
        Re-order the header includes. Make sure column.hxx comes first.
    
        Change-Id: I9f93724c4e0b565a9148d0893feda9e82109bff7

:100644 100644 34b251be3d2dc267e2c4b31bf4ade889be54ebd3 a476eec2644ce3d840a3525e60685c10b546a0b1 M	ccache.log
:100644 100644 b8dc7ff128d9a6772510f291499d3e5f8034e4cf 989a6f8490d3dc9b6552faaa5d3338ef11d96ca2 M	commitmsg
:100644 100644 75414764833c884979140a22c1fc3f8888a33e78 c3034c36e1045c28850073be1b5eeeab7948599e M	dev-install.log
:100644 100644 3a778b46f34f3bcf0d3c70c3479270986888f4c9 75d1590884ea160e3916623015bf2d8e8f3f4d63 M	make.log
:040000 040000 15d374b168b90165da4d70957e5ac1da58e05d89 82cb1a6aa93c11182f124401ee3b61d154ac25e3 M	opt

# bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
# good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932
git bisect start 'latest' 'oldest'
# bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574
# good: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15
git bisect good 8f4aeaad2f65d656328a451154142bb82efa4327
# good: [9995fae0d8a24ce31bcb5e9cd0459b69cfbf7a02] source-hash-8600bc24bbc9029e92bea6102bff2921bc10b33e
git bisect good 9995fae0d8a24ce31bcb5e9cd0459b69cfbf7a02
# bad: [8ad82bc1416a07501651e8d96fe268e47d3931d3] source-hash-13821254f88d2c5488fba9fe6393dcf4ae810db4
git bisect bad 8ad82bc1416a07501651e8d96fe268e47d3931d3
# bad: [238338bc4111eb82429ea47384d4012bcd7cdc3e] source-hash-b6ba04639b9922f6717f79ac4be215e09691d7a9
git bisect bad 238338bc4111eb82429ea47384d4012bcd7cdc3e
# good: [89dc8a802d1625e0efd88ba0fb720b22be87f3f0] source-hash-da03bb1ee6a69d2f4fef4c3ca0adc0ba9588bd19
git bisect good 89dc8a802d1625e0efd88ba0fb720b22be87f3f0
# good: [4d8d18a8c871d6803af99b706f780eb6e65c7a5d] source-hash-d4779887636fa9ab5b477f3436bcd3728a3e30ba
git bisect good 4d8d18a8c871d6803af99b706f780eb6e65c7a5d
# bad: [ec6ba885d9d4142060cebdef210d26f0b2ef5045] source-hash-1ce6d6d4133865d9616e12228be2c04cbba1976c
git bisect bad ec6ba885d9d4142060cebdef210d26f0b2ef5045
# bad: [d42e14f46fbe1bfc716dc90d28001a0e32afa3d5] source-hash-82b6c4884d7b2fbb3d45980785cebba7a159fb10
git bisect bad d42e14f46fbe1bfc716dc90d28001a0e32afa3d5
# bad: [56260020c5caba00fbd063db5554b452c06116dc] source-hash-34847f1cf7538c333e9b8700eb4012ae358644a6
git bisect bad 56260020c5caba00fbd063db5554b452c06116dc
# first bad commit: [56260020c5caba00fbd063db5554b452c06116dc] source-hash-34847f1cf7538c333e9b8700eb4012ae358644a6
Comment 7 Xisco Faulí 2014-09-19 12:23:46 UTC 

*** This bug has been marked as a duplicate of bug 79330 ***
Comment 8 Robinson Tryon (qubit) 2015-12-17 11:08:55 UTC 
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]
Comment 9 Justin L 2021-03-11 09:29:20 UTC Comment hidden (no-value)
Comment 10 Justin L 2021-03-11 09:30:34 UTC 
The proposed patch in bug 108518 fixes "Ochrama2.doc" from comment 5.