I found this one when triaging this bug: https://bugs.freedesktop.org/show_bug.cgi?id=53944
Steps to Reproduce:
Open a new writer document
Format -> Page -> Columns
Select 2 Columns and untick "AutoWidth"
Behavior: Tab stop shows up on the top ruler but columns aren't respected
Expected Behavior: Tab stops should show up and columns should be the result -- ie. you can't type across the tab stop
Version 184.108.40.206.alpha0+ (Build ID: dfd474710f959dcf78038deb990c3618b467ec6)
on Bodhi Linux
Confirmed on WinXP 32b
pull time 2012-12-03 09:03:45
Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Open the attached file:
(2 columns 84.40 mm / 75.62 mm · Spacing 9.98 mm)
Created with LibO 220.127.116.11,
and works fine with LibO 18.104.22.168.
Created attachment 71206 [details]
Sample file: two_columns.odt
*** Bug 53944 has been marked as a duplicate of this bug. ***
Confirmed on windows 7 64bits with LibO-Dev_22.214.171.124.beta1
*** Bug 58188 has been marked as a duplicate of this bug. ***
I should have a bibisect for this shortly and then I'll get in touch with whoever made the patch that borked this :)
Created attachment 71518 [details]
FDO 57953 Bibisect Log
# good: [778045e259d6c6cdd39e55feea1646e95eab8537] source-hash-6aeeca56daa9065f607cc7056e7d86d237c84a99
# bad: [3a336c0c31bf41ebaa40c23ee063bd38a8aa334f] source-hash-5695aea3bbe719881177b35c805920bee608751b
suggests this is introduced in the range 6aeeca56daa9065f607cc7056e7d86d237c84a99..5695aea3bbe719881177b35c805920bee608751b
git log 6aeeca56daa9065f607cc7056e7d86d237c84a99..5695aea3bbe719881177b35c805920bee608751b
show these, and esp. this suspicious (wrt the bug) commit:
Author: Norbert Thiebaud <firstname.lastname@example.org>
Date: Sun Jun 17 13:33:03 2012 -0500
writer:crash(i118878) when adding columns and chang. properties in a frame
when adding columns, GetNumCols() reflect the new number of columns
before the actual columns available are updated.
Due to the way and order in which properties are updated
the code that adjust the columns can be run before the new columns
are avialable.. and was using GetNumCols().
This patch avoid using that api and rely on the column iterator
to determine the acutal number of column available.
CC'ing Norbert to have a look ...
See also: mab4.0 'Bug 53525 - FILEOPEN existing document: 2 columns Table of contents exceeds page width'.
[Please select the duplicate.]
I reverted that fix of Norbert's yesterday and applied a simpler version. Any chance you could re-test ?
WORKSFORME with daily:
Version 126.96.36.199.beta1+ (Build ID: 315b9b4a5c53eed5fd283bc329e05d7d8fbc9eb)
great - that contains the fix - so really this was a duplicate :-)
*** This bug has been marked as a duplicate of bug 53525 ***