Download it now!
Bug 78396 - FILEOPEN: Position of lines with anchor set at "Cell" are all moved to cell A1.
Summary: FILEOPEN: Position of lines with anchor set at "Cell" are all moved to cell A1.
Status: RESOLVED DUPLICATE of bug 67712
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, regression
Depends on:
Reported: 2014-05-07 15:13 UTC by bureautiquelibre
Modified: 2015-12-15 11:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

ODS file created in 4.0.4 with lines anchored at "cell" (1.36 MB, application/oleobject)
2014-05-07 15:31 UTC, bureautiquelibre

Note You need to log in before you can comment on or make changes to this bug.
Description bureautiquelibre 2014-05-07 15:13:46 UTC

After an update from v4.0.4 to,

Some users report than line position aren't kept in ods files created with 4.0.4 and opened in

All lines anchored to a cell in v4.0.4 are all displayed as if they were anchored to cell A1 when opening the file in v4.1.5.3

I reproduced the same problem in v4.1.6 and v4.2.3

See the attached file + expected result.

A workaround is to change the anchors to "Page", but requires to go back to v4.0.4 first and adapt loads of documents :-(

Best Regards,
Eric Ficheux
Comment 1 bureautiquelibre 2014-05-07 15:31:39 UTC
Created attachment 98632 [details]
ODS file created in 4.0.4 with lines anchored at "cell"

The file contains some macros, no need to activate them to see the problem.
v4.1.5.3+ shows all lines on the top left corner.
Comment 2 Cor Nouws 2014-05-07 18:14:53 UTC

Thanks for the report!
I can confirm the bug. 
Is OK in
(Din't check which is the first version with the problem...)
Comment 3 bureautiquelibre 2014-05-12 07:23:48 UTC

Some more information about the issue: it also occurs with files created in v4.1.5.3 and 4.2.3, with lines anchored to a cell.

Best Regards,
Eric Ficheux
Comment 4 Xisco Faulí 2014-05-29 15:38:31 UTC
a7e54955e9f49e8b59dfd8c4533785a680b1796c is the first bad commit
commit a7e54955e9f49e8b59dfd8c4533785a680b1796c
Author: Bjoern Michaelsen <>
Date:   Wed Oct 16 11:07:50 2013 +0000

    commit 5da10275a7475efdbfd9de14ea58cf8f4c6c1582
    Author:     Stephan Bergmann <>
    AuthorDate: Fri Mar 1 17:09:45 2013 +0100
    Commit:     Stephan Bergmann <>
    CommitDate: Fri Mar 1 17:18:29 2013 +0100
        Related rhbz#915743: Abort UCB call from SvtMatchContext_Impl::Stop
    otherwise the SvtMatchContext_Impl thread can continue to run for
        arbitrarily long, and the other thread calling Stop() and join() will block.
        However, especially the WebDAV UCP does not properly support aborting commands,
        see 260afe56fd6b2f34de8290f3cdb7d1df5b88f8a8 " neon commands cannot be aborted",
        so this is not yet enough to actually fix rhbz#915743 "thread deadlock/slow
        join in insert->hyperlink in impress."
        Change-Id: I0da899f824763e1b3d19bb5b38d906feb690b623

:100644 100644 fd22aadcebcf1ca20b6c2fcdb9e135deeb9b5885 8a0f14e1bb71d7ecdf8086c62e9769bb7f2d09b8 M	autogen.log
:100644 100644 5af869ab53b50329a270e7d4e2587f802bf68afb 8519bf956c5e06a85818d380070eedc0ef846790 M	ccache.log
:100644 100644 63cd7351c9d6feb098661a5783d51bb172d8a306 33abac29aad7182260562465482b493d94b78a83 M	commitmsg
:100644 100644 e9ea867065a69fa4f0fbbb5c2abb40baeeabd307 21fc5294b2cb922862b78327b6b8a3cd953f38b5 M	dev-install.log
:100644 100644 4c087a5ff52a8cef08f31417ac650666b1d9d0af c1cc87465560a589137349c81641a62968242386 M	make.log
:040000 040000 ece742cbaf9101d015210ea8da6c00ad7a4457c7 9ff9cbceea1fe6b0ad1b17fe9068b2c8e32a6cbb 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
# bad: [89dc8a802d1625e0efd88ba0fb720b22be87f3f0] source-hash-da03bb1ee6a69d2f4fef4c3ca0adc0ba9588bd19
git bisect bad 89dc8a802d1625e0efd88ba0fb720b22be87f3f0
# bad: [fe956dc63cc7ed1831f0e7e9e7253ea4d8c99549] source-hash-b15f095293c6127ecaef2f0fa3a1683e72392835
git bisect bad fe956dc63cc7ed1831f0e7e9e7253ea4d8c99549
# good: [cd762eb968ba8783f726b67d9d70b0a76f4eb55d] source-hash-c9562064740baed3a9978723c5fe77b44a13a7aa
git bisect good cd762eb968ba8783f726b67d9d70b0a76f4eb55d
# bad: [a7e54955e9f49e8b59dfd8c4533785a680b1796c] source-hash-5da10275a7475efdbfd9de14ea58cf8f4c6c1582
git bisect bad a7e54955e9f49e8b59dfd8c4533785a680b1796c
# good: [5e90d936616ff95724eaa3e3a0a7c7a9747e9b44] source-hash-ba446dd58a4ad324d242afcd5b28d3b4dff5a881
git bisect good 5e90d936616ff95724eaa3e3a0a7c7a9747e9b44
# first bad commit: [a7e54955e9f49e8b59dfd8c4533785a680b1796c] source-hash-5da10275a7475efdbfd9de14ea58cf8f4c6c1582
Comment 5 Cor Nouws 2014-05-29 21:45:55 UTC
Isn't the same?
Comment 6 bureautiquelibre 2014-09-30 14:32:47 UTC

Looks to be the same bug,

Best Regards,
Eric Ficheux
Comment 7 Cor Nouws 2014-09-30 20:06:26 UTC
thanks Eric. Marking as duplicate then

*** This bug has been marked as a duplicate of bug 67712 ***
Comment 8 Robinson Tryon (qubit) 2015-12-15 11:03:10 UTC
Migrating Whiteboard tags to Keywords: (bibisected)