Bug 54890

Summary: Applying frame style changes width value
Product: LibreOffice Reporter: Henrik Gebauer <code>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium CC: code, jorendc
Version: 3.5.4 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: video that shows the bug

Description Henrik Gebauer 2012-09-13 20:09:44 UTC
Created attachment 67120 [details]
video that shows the bug

I want to define a new frame style with a certain width (actually I want to create a table frame which is always 100% wide).

Clicking "Apply" in the style editor set the width to another (very small) value.
Clicking "OK" or changing other values works.

See the video in the attachment.
Comment 1 Jorendc 2012-12-29 18:24:51 UTC
Thanks for reporting!

Tested with Ubuntu 12.10:

I CAN reproduce it with LO 3.6.4.3

CAN'T reproduce this with Ubuntu 12.10 and LO 4.1.0.0.alpha0+ (Build ID: 6306926e038fd7ad49c0089ebce8be0f0f8da3c) <- BUILD ENABLE_SYMBOLS=true

When trying to bibisect, to find out where the bug was fixed, I CAN reproduce it with the latest version (git checkout latest) (4.1.0.0.alpha0+ (Build ID: 8450a99c744e9005f19173e4df35d65640bcf5c))...

So, OR it is fixed between latest version I can bibisect, and the version I build today (approximate 3 houres ago) ... OR I can't reproduce with my own build, because of ENABLE_SYMBOLS=true.

I'll set this bug to NEW, and let a developer/another QA-tester have a look at it.
Comment 2 Jorendc 2012-12-29 18:39:14 UTC
Just spoken with a core developer (Joel Madero).

The latest build of a bibisect is some weeks old. My compiled version is a couple hours old.

Result: the bug is fixed between last bibisect version and my compiled version.

I set bug status to RESOLVED WORKSFORME; If not fixed in release of LO 4.1, please REOPEN this bug.

Thanks for reporting, and happy holidays!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.